SOAMANAGER Setup

Prerequisite: Review SSL certificates are the same between SAP and 3rd party tools. Locally/self-signed certificates are not accepted. Verisign is one certificate provider.
Note; SOAMANAGER web browser dashboard structure changes with every version of Solution Manager.

• a. Go to Application and Scenario Communication (Service Administration)
• b. Single service admin (Web Service Configuration)
• c. Enter /bti/* and search for Service
• d. Press Apply selection
• e. Go to Configurations tab
• f. Create
• g. Enter a service name and binding (TETASK)
• h. Save
• i. Go to Overview tab to get WSDL for selected binding

2. Give WSDL to calling system
3. Create a user ID and password. Allocate roles /BTI/TE:CTS_ADMIN and /BTI/TE:CTS_USER

Outbound
1. Create endpoint using SOAMANAGER

• a. Go to Application and Scenario Communication (Service Administration)
• b. Single service admin (Web Service Configuration)
• c. Enter /bti/* and search for Consumer proxy (Both Names)
• d. Press Apply selection
• e. Go to Configurations tab
• f. Create Port
• g. Put in WSDL url, user id and password
• h. ALWAYS SELECT the DEFAULT checkbox
• i. Save
  

2. If a different version of Remedy, you may need to re-generate the proxy
3. If the outbound call is not working and you are debugging the send method, if the ‘set authorisation’ method fails on retrieving the ‘protocol’ it probably means that SAP cannot determine the logical port to use and therefore defaults to trying to output the call using XI. This will be because the ‘default’ checkbox was not selected when the port was created above. Re-create the port making sure it is selected. If this is not possible for some reason, then the port must be specified in the constructor method of the class.