Configuring integration server

You can use App Connect Enterprise integration server configuration file to define properties that are related to external services on which the integration server relies.

1. Navigate to the folder where the server.conf yaml file is.

   The server.conf yaml file is available in the <work directory>/server.conf.yaml.

2. Right-click the server.conf yaml file, and select to Edit in text mode.
3. Add the following line under "ConnectorProvider" to add App Connect for Manufacturing connector provider properties.
   Windows

   
   ConnectorProviders:
    ACMfg:
       connectorClassName: 'com.ibm.industrypack.industryclient.connector.ICConnectorFactory'
       jarsURL: 'C:/Program Files/IBM/ACMfg/13.0.0.0/runtime/amd64_nt_4'
       property1: 'trustCertificate=true;isHA=false'     
       property2: 'returnDiagnosticHeaderParameter=0x00000002'
       

   LinuxUnix

   
   ConnectorProviders:
    ACMfg:
       connectorClassName: 'com.ibm.industrypack.industryclient.connector.ICConnectorFactory'
       jarsURL: '/opt/IBM/ACMfg-13.0.0.0/runtime/amd64_linux_2'
       property1: 'trustCertificate=true;isHA=false'
       property2: 'returnDiagnosticHeaderParameter=0x00000002' 
   

   Where,

   • jarsURL is the installation directory of App Connect for Manufacturing.
     Note: If the default installation directory for App Connect for Manufacturing is changed, make sure to update the jarsURL path.

     For example, the default location is:

     Windows

      jarsURL='C:/Program Files/IBM/ACMfg/13.0.0.0/runtime/amd64_nt_4'

     Linux Unix

      jarsURL='/opt/IBM/ACMfg-13.0.0.0/runtime/amd64_linux_2'

   • You can opt to set the returnDiagnosticHeaderParameter property if you need to request the diagnostic information.
4. Start the integration server by using the following command.

   IntegrationServer --work-dir <workdirectory>

   For a vault-enabled integration server, start the integration server by using the following command.

   IntegrationServer --work-dir <workdirectory> --vault-key <vaultkeyname>

   Note: If your message flow has username and password, you need to configure vault in the integration server. For more information, see Configuring vault-enabled integration server.