implementation:manufacturing:service_broker
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
implementation:manufacturing:service_broker [2018/04/20 07:22] csuhaa remove download section |
implementation:manufacturing:service_broker [2019/07/02 15:46] (current) vise |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| =====3.2. Produmex Service Broker===== | =====3.2. Produmex Service Broker===== | ||
| - | <WRAP round important>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.</WRAP> | + | <WRAP round important>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.</WRAP> |
| 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 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. | ||
| Line 22: | Line 22: | ||
| 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. | 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. | ||
| + | |||
| + | <WRAP center round info 100%> | ||
| + | Local System users usually do not have the right to use printers, therefore, it is recommended to configure a Windows user. | ||
| + | </WRAP> | ||
| 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. | 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. | ||
| Line 77: | Line 81: | ||
| {{ :implementation:manufacturing:installation:dependency02.png |dependency}} | {{ :implementation:manufacturing:installation:dependency02.png |dependency}} | ||
| - | //Please note: 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.// | + | //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.// |
| </WRAP> | </WRAP> | ||
implementation/manufacturing/service_broker.txt ยท Last modified: 2019/07/02 15:46 by vise
