This is an old revision of the document!
3.2. Produmex Service Broker
Make sure you do not run both the 32-bit version and the 64-bit version Service Broker on one environment as they conflict with each other. Only one service broker instance should be installed on a server at any time.
The Service Broker establishes the connection between the company database/schema and the application on the mobile device. It queries the data from the database/schema and sends it to the mobile application, and it creates the SBO documents based on the requests from the mobile devices. The SBO documents are created with SAP DI API 32bit version.
The Service Broker can run as a service or from a command window. It creates threads for the different requests which are independent from each other so if one thread has a problem it can be closed and the others are not influenced by it.
If the Service Broker does not run, the communication between the clients and the company database/schema is not possible.
The service broker creates its log files at C:\ProgramData\BX\BX Service Broker\Logs. The ProgramData folder is hidden, you have to either enable 'Show hidden folders and files' in Windows Settings or you have to enter it directly to the address bar in Windows Explorer:
Install the service broker on the server which has access to the company database/schema. The installation file is an .exe file with a name like this one: BxServiceBroker.Setup.exe.
EULA
After launching the .exe file, the End User Licence Agreement will open up. Produmex Service Broker can only be installed if the License Agreement is accepted.
Service settings
When you start the installation, the Produmex Service Broker installer will request information based on the system and will set up the service based on the information you enter.
The installer will first ask the user who will be assigned to the service broker service in windows. This must be a user who has rights to write the event log and the program data directory where the logs are created. The service broker service will also make a connection to the company database/schema, the user must have rights for that as well.
Local System users usually do not have the right to use printers, therefore, it is recommended to configure a Windows user.
The default port for the communication between the service broker and the clients is 50231. The installer will open the firewall for this port automatically, but if you change the port, you will have to change the firewall settings manually.
You can also set up the start mode of the service. The recommended start mode is Auto.
Admin page
On the next screen specify a password for the Service Broker Administration web page.
Database connection
Then you have to provide connection data to the database server.
Select the database type from the dropdown menu.
- MSSQL
Add the name or the IP address of the database server. If you have a named instance, you have to enter the name of the server and the named instance as well (for example SERVER\NAMEDINSTANCE).
Enter the database port on which the application can connect to the server. The default port is 1433.
Add the name and the password of the database user. The default user is sa.
- HANA
Add the name or the IP address of the database server. The database server name has to be added with the exact same format as it was added during the installation of the SAP Business One client.
Enter the database port on which the application can connect to the server. The default port is 30015.
Add the name and the password of the schema user. The default user is SYSTEM. It is recommended to install the Service Broker with the SYSTEM user.
When working on SAP B1 Cloud, add the domain user name and password as well.
Default SAP Company
After that you have to set up the company database/schema. You can only set up one company here, if you have more than one database/schema, you can add the others in the Produmex Service Manager after installation. For more information please see: Produmex Service Manager-Add new database.
Enter an SAP user here which has at least an indirect access license as of SBO 9.2. PL08.
Summary
At the end of the installation you will see a summary screen about you settings. Click ’Finish’ to end the installation.
Configure dependency from the SBO Server Tools service on an MSSQL system
If the server where Produmex Service Broker runs needs to be restarted frequently, we advise to configure dependency from the SBO Server Tools service.
When Produmex Service Broker starts, it tries to connect to the SAP environment. If the connection fails, Produmex Service Broker will not start.
If the Produmex Service Broker is dependent from the SBO Server Tools service, it will only start after the SBO Server Tools service is started, therefore it will be able to connect to the SAP environment.
To configure the dependency, open the Command Prompt window and enter the following:
C:\>sc config BXServiceBroker depend=B1ServerTools
On the Dependencies tab of the Produmex Service Broker properties you can see that the dependency is successfully added:
Make sure you do not set the dependency on HANA enviroments. Since the Produmex Service Broker is a Windows service, SAP HANA and Produmex Service Broker are running on separate servers. In order to avoid this issue, make sure that the HANA server is already running when you restart the server of the Service Broker.