You need to make sure that the Lead Developer user configured in your source server where the product has been created is pointing on the correct Presto generated access group. This will drive connection to the source server and product list retrieval. If the access group is not correct product list won't show correct list.
Yes the source server is where the product is to be migrated from.
It's an environment that you've created as part of your application in Deployment Manager. Now you must ensure that the lead developer on that source server has the proper access group to see your products.If you are able to create a deployment request this means that you installation is correct so no remarks on the step.
I created a new access group and a new application that is built on the Presto Application and my Project's application which is also the one in context of the product. I have given access to this access group to the lead developer that I am using while configuring the environments in the Release. I am still unable to find the products. I was only getting the default products in the list, but not the product that I created. Few points to be noted regarding the infrastructure:
1. Since our Pega version is on 7.2.2, we used the server for 7.2.2 and not the server for 7.2 in general.
2. Since we are unable to add application of the Presto accessgroup due to password lock, we created a new application and an accessgoup with the built on application as the PegaPRESTO 7.20 and the project's default application to which I subscribed from the RM client/Devlopment server.
3. When trying to enter the lead ID which is having the accessgroup created in step 2, in the Environment section in the release request, the name is not fetched. After clicking on the gear icon for an environment, i entered the same dev lead operator id with the environment details. When I tried to check the connection status from Manage Env option, I get a HTTP 403 error for all the environments.
Please help me. Is it possible to have a screenshare with you regarding this issue. Or at least a phone call will also help. Please respond. <Removed> I really need your help.
***Moderator Edit-Vidyaranjan: Removed Personal Information***
Hi Shoeb, Your Lead Developer opertor ID must use the Presto access group which is normally pointing on your Wrapper application prefixed by PegaPRESTO_<YourAppplication>. This wrapper application should have been generated via the PRESTO Portal application. Try also to restart both client and server to make sure context is clean after all your changes. If still not working i'll see if we can have a screenshare. Kind Regards, Djibril
I was able to populate the product list finally after following your latest instruction. Thanks a lot for your continued help. It was really helpfull. Now I will need a little help in the jenkins configuration. Hope thats not asking for too much :)
Gald to hear that you are now able to populate the product list. Do you mind marking the reply with the instructions as the Correct Answer and creating a new post for your use case on Jenkins configuration? Individual discussions threads that focus on individual issues/use cases will help other community members who have the same requirement and can help bring on increased focus on your post.