Message Broker configuration file can be found in the main application directory. The file name is E4CwinService.exe.config. The file has an XML format and contains sections related to web services, some .NET environment settings, etc. From the point of view of the Message Broker configuration, there are two important sections, described below.
| Anchor | ||||
|---|---|---|---|---|
|
Application settings are grouped in the <appSettings> section, close to the top of the file. The following settings are to be maintained there:
SpringCfgPath – path in the file system, where configuration of spring.net can be found. This shold point to Objects.xml file in subdirectory config of your application directory
SapWebServiceUrl – URL, at which SAP web service is registered to be called
SapWebServiceUserName – user name (technical user), used by Message Broker to access SAP web service and send inbound messages to SAP
SapWebServicePassword – password of technical user used by Message Broker to authorize itself to the SAP web service
passwordSecure – encrypted password generated in the Cloud Manager with cloud access token used as the encryption key
MessageBrokerWebServiceUrl – URL, at which web service of Message Broker should be accessible to SAP, please note, that this URL has to be reserved first, as described in URL namespace reservation section
MessageBrokerWebServiceUserName – user name SAP should use to authenticate to the web service
MessageBrokerWebServicePassword – password SAP should use to authenticate to the web service
passwordSecure - encrypted password generated in the Cloud Manager with cloud access token used as the encryption key
AccessToken – cloud access token, used to authenticate Message Broker to Cloud. Access token is generated as described in Cloud access token section
CloudAccount – account used to authenticate to Cloud, generated as described in Account regstration section
CloudCompanyName – company name in Cloud, as described in E4C Architecture Overview document.
MasterCloudUrl – leave empty for productive Cloud. To access non-productive Cloud instance, the Cloud address should be entered here
| Anchor | ||||
|---|---|---|---|---|
|
Besides the application settings described above, E4CwinService.exe.config file is responsible for logging configuration. Message Broker uses common logging library (http://netcommon.sourceforge.net/) in conjunction with NLog (http://nlog-project.org/). In short: common logging is a factory that hides from the application the actual logging implementation. It is capable to do a simple logging to a console, or so. For more advanced logging setup, it needs a backing library (NLog, log.net, or similar). In case of E4C Message Broker, NLog has been chosen. It is capable to log to file (including file rolling), system event log, console, etc. It is a matter of configuration to replace NLog for any library of a preference. The logging configuration (output file/directory, information being logged, log severity threshold, etc.) is configurable in the file too. In Message Broker configuration file, the logging configuration can be found near the bottom of the file. A sample configuration is presented below. Here NLog is configured to a file. The file is put to c:\tmp\e4c.log directory and is rolled (a new log file is created) every day. Logs produced by Spring.NET package are stored if their level is Info or above. Other logs are created with Trace level, which makes every log sent to a file and console. You may want to edit the log settings and switch off the console logging, change directory, where the log files are created, change logging level, to save some disk space, etc.
...