The solution is a manual process and requires the user be well versed in creating SOAP calls.
The CA APM wsdl that you download from within the APM GUI does not work in the SOAP UI because CA PAM does not support everything that the ITAM API needs to update an asset. For Example, CA PAM does not support SOAP Headers where the ITAM API stores authentication tokens.
The basics for the reason why this does not work is because the CA APM WSDL uses the SOAP 1.2 fault message format. CA IT PAM does not recognize this message format.
Note: The web services SOAP messages contain the parameters and data that are needed to perform specified operations (such as logging in or searching).
The CA APM WSDL uses the header section of the SOAP message to store authentication information. The header section is required for CA PAM to communicate with CA APM through the web services. CA PAM does not recognize the header section of a message.
The CA APM WSDL contains CA APM objects and sub-objects. CA PAM does not recognize the sub-objects.
You can resolve these problems by creating each SOAP message that you need and importing it into CA PAM as a preformatted SOAP message file. You need to create a separate SOAP message for each operation (on each object) that you want to perform.
Complete the following steps to create and implement preformatted SOAP messages:
- Navigate to Administration, Web Services in the product and download the WSDL (.wsdl) file to your local computer.
- Open the WSDL file in your preferred SOAP message tool.
- Create a SOAP message .xml file for each method and operation that you want to perform in web services.
Note: You must create a SOAP message file for the Login method.
- Save the SOAP message files on a server that CA PAM can access.
The following example shows a path and file name for a SOAP message file that is named SearchContact.xml:
- Open CA PAM and create a process for each method and operation that you want in your CA APM web services.
- Import each saved SOAP message .xml file into the corresponding process.
- Modify the data and settings for the SOAP files to create your own web services descriptions.
- Start the new processes.
Note: After the Login method has run and you receive the authenticationticket ID, save the ID in a temporary variable or data set in each process.