Creating an M3 Configuration

If the MWS server can detect an M3 environment running in the same Grid as MWS is installed in, a default M3 Configuration is created.

You can also create a new configuration that defines the M3 application back-end system that the web service uses.

  1. In the M3 Web Services Server management page, click the Configurations link. The Manage Configurations page is displayed.
  2. Click the + next to M3 Configuration. The Create M3 Configuration page appears.
    1. Provide information for the following fields and click Save.
      Name

      Provide a name for the configuration.

      Description

      Provide a description for the configuration

      M3 Router Address

      Provide the name of the M3 Application Server, hostname or IP address.

      M3 BCI Port

      Provide port number of the M3 BCI Port. This port is used during execution of web services based on M3 Display Programs. This port is defined in the Grid router named M3Router in a standard M3 Business Engine installation.

      M3 Server Timeout (BCI)

      Provide the timeout in milliseconds for M3 Server connections. Value zero (0) means that the default timeout (60 s) setting will be used.

      Note: This value should not be changed unless there are timeout problems.
      M3 Server API Port

      Provide the M3 Server API Port. This port is used to retrieve design-time meta data for web services based on M3 API Programs as well as during execution of web services based on M3 API Programs. This port is defined in the Grid router named M3Router in a standard M3 Business Engine installation.

      M3 Server API Timeout

      Provide the timeout in milliseconds for M3 Server connections. Value zero (0) means that the default timeout (60 s) setting will be used.

      M3 API Force Proxy

      This parameter should be set to True to force proxy connections to M3 Api.

      Normally, a reconnect is carried out when a new port (and in certain cases, a new IP address) is assigned by the server and the client connects to that port instead. This is often done to provide for load balancing.

      In certain cases where communication occurs through a firewall, this can be a problem. By using proxy, the reconnect does not occur.

      Note: Running in PROXY mode imposes a larger burden on the server. It should not be used unless it is necessary, for example when used via firewalls with certain, restricting configurations. For more detailed information on this scenario, see the M3 API Client Interface - Programmer’s Guide & Reference.