Use Transaction SE80 to maintain FSM Cloud Connector Web Service configuration. Choose the Package /PACG/ECM, then select the node "Enterprise Services" → "Service Definition" and finally choose the service /PACG/ECM_WS:
...
Once you press the button presented on the screenshot above, the transaction SOAMANAGER will be launched. Login with your SAP user when the browser is launched and click “Create service”.
...
Here we will guide you through the configuration of the SAP web service. After completing all the steps you should have a working communication channel from message broker to SAP system.
Start with running transaction SOAMANAGER.
Go to Service Administration tab (default tab of SOA Manager so most likely you are there already)
And then to Web Service Configuration
Next - use the available search box to find ‘*pacg*’ objects and select /PACG/ECM_WS
Followingly in the ‘Configuration’ tab define new service (a biding is also created) - press ‘Create Service’ button
Define service name, binding name and add description. Names and description should be meaningful as usual - there are no further requirements in this area.
Press ‘Next’ and continue to ‘Provider Security'.
In ‘Transport Level Security’ section you must select either ‘None’ if using HTTP connection or 'SSL' in case of HTTPS. You can learn more on the topic here: Setting up secure (HTTPS) connection from FSM Message Broker to SAP system.
Then in the ‘Authentication Settings’ section, ‘Transport Channel Authentication’ subsection tick ‘User ID/Password’ - this allows message broker to login with user and password when connecting to this web service.
Press ‘Next’ and continue to ‘SOAP Protocol'.
Here it is not really necessary to change nor add anything, you can simply press ‘Finish’ but the ‘Access URL’ is actually a path to the web service. It is needed to complete configuration of a message broker - Url property in the ‘SapDefinitions’ section. When you click ‘Finish’ and then come back here (edit or view) you will find ‘Calculated Access URL’ displayed. You can then copy it and paste to your message broker configuration but you could also use ‘Alternative Access URL’. Here you can basically enter anything you want and this can be used as a path to the service. In the same time the calculated Access URL is still valid.
Next step would be setting the correct URL in your message broker config file. So how to tell what is the correct URL? It must follow the pattern URL follows this simple pattern: [protocol]://[host]:[port][path].
The protocol is either HTTP or HTTPS, the right one depends on what was defined in the web service definition (above).
‘Host' is just an address of your SAP system, if you don’t know it, you can check it in the SMICM (ICM Monitor) transaction:
Start SMICM in your SAP system
From the menu select ‘Goto’ → ‘Services’
Then select interesting line either corresponding to HTTP service or HTTPS, depending which of them you intend to use (within SAP these settings are system-wide) and display details - thus you should get the host name and the port number that the service uses (it does not have to be the default one like 80 or 443).
Once you have all the components you can out your URL together and enter it in the message broker config file
Activating web service. In theory new service/binding in SAP is activated on creation. This is displayed in the bindings' list:
However it can happen that even SOA Manager says that service is active - it is not. If you needed to activate such a service you should do it in transaction SICF.
Start SICF transaction
In the initial screen simply execute the transaction
Then find your service - the services' tree corresponds to the service calculated path e.g. Calculated Access URL is ‘/sap/bc/srt/rfc/pacg/ecm_ws/200/fsm2sap/fsm2sap’ and then activate it. All nodes from top to bottom must be black - that means they are active
