When P6 or p6service.jar
runs on a server other than a P6 Integration API Remote Mode server and the "Job Service Shared Folder Location" configuration in the Primavera P6 Administrator is set to null, attempting an XML import from a P6 Professional deployment that uses Cloud Connect will result in the XML import process to fail. The import process fails because the temporary XML file for the project import that is created under the P6 Integration API home directory but not the P6 or p6services.jar
server which runs the import code.
Setting the Job Service Shared Folder Location configuration to a shared directory that can be utilized by all P6 modules allows the temporary XML file to be stored in a common location that can be accessed by P6 Integration API Remote Mode server as well as the modules which have potential to run services, such as XML import.
For more information about when you need to create a shared folder for P6 Integration API and P6, see the following article on My Oracle Support:
Primavera P6 XML Import Error "Cannot Schedule job. Please contact administrator to correct the problem" or "The job request you submitted did not complete successfully" And The Log File Displays "$path\importer_RMI_####.xml (No such file or directory)" (Doc ID 1987004.1)
To ensure that you can successfully implement an XML import when P6 Integration API Remote Mode and P6 or p6service.jar
resides on different servers:
p6services.jar
Note: If you are using Windows, the drive letter that you use for the mapping must be the same across all servers.
/P6EPPM/Temp)
.
Legal Notices
Copyright © 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Monday, October 24, 2016