Managing Intercompany Solution in different servers

Managing Intercompany Solution in different servers

Before setting up the Intercompany 2.0 solution across different servers, the following key factors must be assessed:

  • Quantity of servers available in the environment (i.e., 2 servers: Americas and EMEA+APJ)
  • Desired Landscape by the customer (i.e., Consolidation)
  • Localizations are needed in the implementation
  • Maintaining the environment (complexity)


  • Microsoft SQL Server
  • SAP Business One 10.0 PL X *
  • SAP Business One DI Proxy Service
  • SAP Business One EventSender Service
  • Intercompany Add-on (all databases using ICO)
  • SAP Business One Integration Service
  • Intercompany Scenario

 

  • Microsoft SQL Server
  • SAP Business One 10.0 PL X *
  • SAP Business One DI Proxy Service
  • SAP Business One EventSender Service
  • Intercompany Add-on (all databases using ICO)
Note: Same PL for ALL databases in the environment

 

From the SAP Business One package, install the Integration Solution Components




Define a path where you want the integration to be installed



  • Ensure this server presents all components from the Integration package installed
  • Include an administrator password to be used by the B1iadmin user

  • Select the correct database type (SQL, HANA, etc)
  • Include the correct password to connect to the server
  • Include the B1i password
      

      

  • Activate the desired packages (i.e., Mobile)
  • Verify the summary and install the Integration package
      
      

  • Start the installation process
  • Make sure to complete the installation properly
      

      

From the SAP Business One package, install the Integration Solution Components
     
 
      

Define a path where you want the integration to be installed
      

      

  • Make sure to UNCHECK “Integration Framework Service.”
  • SAP Business One EventSender is mandatory
  • SAP Business One DI Proxy is optional
      

      
      

  • Since the “Integration Framework Service” will not be installed, the wizard jumps to the “Summary” screen
  • Press Install
      

      
      

 

  • All the components must be maintained in the same version and patch level
  • After the complete installation, EventSender from server 2 needs to point to the Integration Service from server 1
  • Connections must be working properly for all databases in the SLD (Integration – server 1)
  • Entries in SLD from server 2 must be created manually in server 1
  • The environment will present 2 SBO-Commons (which is OK)
  • Only the databases necessary for the Intercompany solution need to be created in the integration server
  • Important to create a strategy to back up all databases at the same time
  • Mixing Intercompany and Multi-branch functionalities is NOT supported in the same environment
      




  • SAP Business One Integration Service installed

  • SAP Business One Integration Service NOT installed
      

  • Start → All Programs → Integration Solution for B1 → SAP Business One EventSender → Setup
  • Select the correct DB Type (SQL or HANA)
  • Include local server name (from Server 2)
  • SQL password for the sa user
      

      
      

  • Step 3/5 requires the B1i Server Host and the B1iadmin password
  • The information should be retrieved from server 1 (Americas)
      

      
      

  • Retrieving the B1i Server Host to be used in the server 2 EventSender
  • Start → All Programs → Integration Solution for B1 → Integration Framework
  • Include the B1i User (B1iadmin) and password of the server 1
      

      

  • Maintenance → Cfg Runtime
  • Look for the Integration Framework Server
  • Copy the entire path.
      

  • Copy the “Integration Framework Server” extracted from server 1 into the “B1i Server Host” field in server 2
  • Include the B1iadmin password from server 1 (Americas)
  • Press “Test Connection” to ensure a successful message appears

 

  • Select the required databases necessary for the environment
  • The databases selected will send events (transactions) to the Integration located in server 1 (Americas)
  • Step 5/5 shows B1 Server from server 2 (EMEA + APJ) and B1i server from server 1 (Americas)
  • Process returns a “Setup Successfully” message

 

  • The database entries in SLD will NOT be created automatically
  • User needs to manually create the SLD entries to successfully connect the databases to the Integration server
  • 3 DBs will be created (CAGroupCons, Branch2CA, and Branch3CA)
      


      

  • Select one of the existing companies available in the Integration server
  • Press “Copy”
  • System returns a message to be confirmed by the user
      

      

Relevant information in this step:
      

      

The following fields must be configured for each database on Server 2:

  1. Name: Branch2CA – created manually (normally the DB name is available in server 2)
  2. B1Server: DEWDFWTEC4038:30000 (from Server 2)
  3. licenseServer: DEWDFWTEC4038:30000 (from Server 2)
  4. Company: Branch2CA – created manually (normally the DB name is available in server 2)
  5. SQL password: password from SQL available in server 2
  6. B1i password: password from the B1i user in SAP Business One (server 2)
  7. diProxyHost: DEWDFWTEC4038 (either from server 1 or server 2)
  8. url from JDBC: jdbc:sqlserver://DEWDFWTEC4038:1433;integratedSecurity=false;databaseName=Branch2CA;selectMethod=cursor
      

      

  • Make sure the connections work for ALL databases (especially the DBs located in server 2)
  • For troubleshooting, refer to SAP note 2029714

* Apply the same process to ALL databases required on the Integration server.

  • Follow the normal Intercompany Integration Solution Installation
  • Intercompany Scenario is ONLY installed in Server 1 (Americas)
  • Intercompany Add-on needs to be installed in all companies.