Question4Replies459Views BhushanD2728 Member since 2017 4 posts Citicorp USA Inc Posted: 2 years agoUpdated: 2 years ago Closed Solved Exporting multiple product file (.zip file) using prpcserviceutil utility.Hi,we want to export multiple product file(.zip file) using prpcserviceutil utility.Can you please help with configuration. we are able to export single product but we need to export multiple product in single go.Thanks,Bhushan***Updated by moderator: Lochan to branch reply and create new post*** Data Integration System Administration ReplyI also have this Question (0) FacebookTwitterLinkedinEmail Copy Link Copied! Subscribe Add to My Favorites This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Accepted Solution Posted: 2 years agoMahesh Midthuru replied to BhushanD2728@Bhushan, you can go through my blog over here to understand the configurations to set. Facebook Twitter Linkedin Email Copy Link Copied! Posted: 2 years agoBhushanD2728 replied to BhushanD2728Hi Mahesh, we are tyring to export multiple product from the command line utility and not using Jenkins here. we re trying to run below command. sh prpcserviceutils.sh export --connPropFile file name where file contains. below details. Here node1 is unkown to us. any idea how to get this details. node1.pega.rest.server.url=http://<host name>:<port number>/<context>/PRRestService/<tenant url hash> node1.pega.rest.username= node1.pega.rest.password= node1.export.archiveName= # PRODUCT NAME AND VERSION TO EXPORT node1.export.productName= node1.export.productVersion= #APPLICATION NAME AND VERSION TO EXPORT node1.export.applicationVersion= node1.export.applicationName= # Flag to execute the export operation in async/sync modes. When executed in async mode, the request will be queued. The status of request can be retrieved by setting the jobID. node1.export.async=true Thanks, Bhushan Facebook Twitter Linkedin Email Copy Link Copied! Posted: 2 years agoMahesh Midthuru replied to BhushanD2728@Bhushan, as per the serviceConnection.properties file documentation provides the below information: #To use prpcServiceUtils for multiple instances specify the connection details for each system in the format <systemname>.pega.rest.url... #Anything prefixed to pega.rest.server.url is identified as a system and all properties prefixed with that system name are treated as specific to that system So in your case node1 should be replaced with your system name. You can login into your designer studio to check your system name in System > General or from the database table pr_sys_statusnodes. Hope this might help you to proceed further. Regards Mahesh Facebook Twitter Linkedin Email Copy Link Copied! Posted: 2 years agoBhushanD2728 replied to BhushanD2728Hi Mahesh, Yes. this is very helpful to proceed further. Thanks, Bhushan Facebook Twitter Linkedin Email Copy Link Copied!