Companies on many servers

Run companies on one machine or on servers in different places.

Find a partner Back to Administration and health check

What it does

Multi-instance support with proxy groups and event sender settings for companies on different servers and in different countries.

When you need it: Subsidiaries on their own servers in Asia and Europe.

How it works

Choose one machine to run the integration framework, with its integration service and the Intercompany scenario. Every other SAP Business One server gets only the EventSender, which is required, and optionally the DI Proxy; leave the "Integration Framework Service" unticked there.
Keep SAP Business One and all its components on one version and patch level across every server.
On each other server, set up the EventSender so that it sends to the integration server: copy the server name from the integration server's Maintenance › Cfg Runtime page, enter the B1iadmin password, run "Test Connection" and select the databases that should send events.
On the integration server, create the SLD entries for those remote databases by hand, for example by copying an existing entry and changing the name, server, licence server, company, passwords, DI proxy host and JDBC address. Test every connection.
Install the add-on in all companies and carry on with the normal landscape set-up.

Set it up

For speed, start more than one DI proxy instance per company database and join them into a group; the guide also advises a separate DI proxy for each consolidation level. In the EventSender settings, the "Include List B1 Object(s)" field takes the object list printed in the administrator's guide, plus -3@ and the name of each custom table you replicate, and the "Exclude List B1 User" field takes the name of the B1i user. Restart the EventSender service for the change to apply.

Good to know

A layout with two servers shows two SBO-Common databases; that is expected.
Plan one backup that covers all databases at the same moment.
Once the landscape is in place, switch off the sap.B1System package (Integration Framework › Scenarios › Control) so that system IDs cannot change while running, which can block queues. A company added later then needs a system entry made by hand and a new deployment.
The sizing guide covers up to 30 company databases on one server and puts the throughput on one SAP Business One instance at, on average, between 5000 and 7000 intercompany transactions in 12 hours.