Configure integration server

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

Before you begin

You must create an integration server before you can deploy integration solutions and related resources. See, Creating an integration server.

About this task

Add the connector provider properties that are specific to App Connect for Manufacturing into the server.conf yaml file.

Procedure

  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.
    UNIX platformLinux platform
    
    ConnectorProviders:
     ACMfg:
        connectorClassName: 'com.ibm.industrypack.industryclient.connector.ICConnectorFactory'
        jarsURL: '/opt/IBM/ACMfg-2.0.0.8/runtime/amd64_linux_2'
        property1: 'trustCertificate=true;isHA=false'
    Windows platform
    
    ConnectorProviders:
     ACMfg:
        connectorClassName: 'com.ibm.industrypack.industryclient.connector.ICConnectorFactory'
        jarsURL: 'C:/Program Files/IBM/ACMfg/2.0.0.8/runtime/amd64_nt_4'
        property1: 'trustCertificate=true;isHA=false'
        
    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:

    UNIX platformLinux platform
     jarsURL='/opt/IBM/ACMfg-2.0.0.8/runtime/amd64_linux_2'
    Windows platform
     jarsURL='C:/Program Files/IBM/ACMfg/2.0.0.8/runtime/amd64_nt_4'
  4. Start the Integration server by using the following command.
    IntegrationServer --work-dir <workdirectory>
    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.
    Note: For a vault-enabled Integration server, start the Integration server by using the following command.
    IntegrationServer --work-dir <workdirectory> --vault-key <vaultkeyname>

What to do next

Stop and start the integration server for the change to take effect.