Before Message Broker can initiate communication with FSM Cloud it must be authenticated.
Cloud company registration
Currently company management is not available in the FSM admin. Therefore, a small utility program - E4C Cloud Manager has been created, that helps in company management. Please note that cloud manager is independent on the message broker version. The program can be downloaded here:
The concept of companies has been described in the FSM Architecture Overview (System Architecture). In a nutshell, each Cloud account needs at least one company to be configured. All messages are exchanged in context of the company. In order to manage companies, start E4C Cloud Management.exe and login with Cloud account and the corresponding password. Then on Companies tab you can create and remove companies.
Important note: be careful when deleting companies. When company is deleted, all data related to it is removed from the Cloud. This operation cannot be undone.
Cloud access token
Cloud access token is necessary to be able to exchange messages with the Cloud. It is used by Message Broker together with the FSM cloud account to authenticate to the FSM, so that the FSM password doesn't have to be stored in the Message Broker configuration. Access token can be generated with use of E4C Cloud Management.exe utility. After logging-in, and switch to the Access Token tab, an existing token can be copied from a configuration file and tested as well as a new token can be generated.
Important note: there can be only one active authentication token per account. This means, that when a new token is generated, the old one stops working. This may break communication, which already has been set-up.
There should be only one connector (Message Broker instance) per Cloud account. It is highly recommended not to share the access token among several Message Brokers, as it may lead to unexpected behaviours.
Password
With Cloud Manager three passwords can be encrypted:
SAP user
Message Broker user
Proxy
In the tab "Password" enter the access token and the password to encrypt. Then press the "Encrypt Password" button.
The generated string ("Encrypted Password") needs to be entered in the property "passwordSecure" in an applicable section of the message broker configuration file (E4CwinService.exe.config).
