Add/Modify an ERP Server page

This section describes the Add/Modify an ERP Server page of the Connector for Web Services.

The Connector for Web Services provides web services that expose BDE business interfaces implemented on LN application servers. On the Add/Modify an ERP Server page, you can configure the connections between the connector and one of these LN application servers (ERP Servers). You use the Add an ERP Server page to add a new ERP Server configuration. You use the Modify an ERP Server page to edit an existing one.

To configure a connection with an ERP Server, specify this information:

ERP Server *
The unique name of the LN application server that holds the BDEs or BOIs for which web services are provided.

In the WSDL files that define these services, this name corresponds with the last part of the URL specified as the location attribute of the <soap:address > element.

See Deploying a web service.

Host name *
The TCP/IP name of the computer that hosts the LN application server.
Activation type
The activation type used to start a bshell on the LN application server. You can choose one of these types:
  • rexec

    Activation type rexec starts a bshell using the rexec protocol, which sends the username and password over the network without encryption.

    The rexec type is the default activation type.

  • baanlogin

    Activation type baanlogin starts a bshell using the BaanLogin protocol, which is more secure than rexec protocol because the username and password are first encrypted before sent over the network.

  • baanlogin_ssl

    Activation type baanlogin_ssl starts a bshell using the BaanLogin protocol using a "secure sockets" connection. This activation type can only be used in environments where ION-API performs the user authentication. Typically, this is the case in a multi-tenant cloud environment, but ION-API can also be installed in an on-premises environment.

    ION-API must be configured in such a way that user information, tenant information, and OAuth 1.0a tokens are passed to the Connector for Web Services through HTTP headers.

  • none

    If you select value none, remote activation is disabled. Therefore, you must manually start a bshell and an ottstpjcadaemon on the LN application server.

    You will only use this option for server debugging.

Port
The number of the TCP/IP port to the ERP application server.
  • If Activation type is rexec, the port number is read-only and fixed to 512.
  • If Activation type is baanlogin or baanlogin_ssl, the default port number is 7150. You can, however, select any other valid port number.
  • If Activation type is none, this port number must correspond with the port number used by the ottstpjcadaemon.
User *
The user name used for authentication on the ERP application server. This account is used when deploying BDEs. It is also used as the account for anonymous requests.
Password *
The password used for authentication on the ERP application server.
BSE*
The path of the Baan Environment (BSE) of the bshell.
Bshell*
The logical name of the bshell, as specified in the ${BSE}/lib/ipc_info configuration file.
Environment
Optional field containing the environment settings for the bshell process.

For example:

  • To set the environment variable TRACEJCA, specify this value: -set TRACEJCA=1.
  • To activate extra tracing options for the bshell, specify this value:

    -dbgmulact -keeplog -logfile log.out -dbgjvmi -tracelevel 1

To set here the environment variable TRACEJCA to 1 has the same effect as checking the Trace option.

Company
The company number used by the LN application. If this field remains empty or has value -1, the default user company applies.
Max connections
The maximum number of physical connections for this connection point.

If the value is 0, the number of physical connections is not limited and connection pooling is disabled. If the Activation type is none, this field is read-only and fixed to value 0.

Max references
The maximum number of references to one physical connection.

This restriction on the number of references only applies when the maximum number of physical connections (as specified by Max connections) is not yet reached. When the maximum number of physical connections is reached, the connector selects the connection with the lowest number of references.

If the Activation type is none, this field is read-only and fixed to value 1.

Max threads
The maximum number of requests that can be placed in a thread queue while waiting for a physical connection to become available. As soon as a connection becomes available, the oldest request is removed from the queue and assigned to the connection. A value of -1 means that there is no limit to the amount of requests that can be placed in the thread queue. The default value is 0, which means that no queueing is used.

This field is typically used in combination with Max references set to 0. This prevents that multiple requests are handled concurrently in the same bshell.

If the Activation type is none, this field is read-only and fixed to value 0.

Keep alive time (seconds)

The number of seconds the connection with the ERP application server remains in the idle pool after it is closed.

If you specify here a value larger than 0, you enable connection pooling and set the timer for the idle pool. The default value is 0, which means that no connection pooling is used.

Trace
If this check box is selected, a trace file is generated on the server in which the activities of the ottstpjcadaemon and ottstpbdeman processes are traced. This file is called trace.jca<bshell.pid> and is located in the ${BSE}/log directory.
Allow anonymous requests
If this check box is selected, "anonymous" SOAP requests are processed. Anonymous requests are requests in which no username/password has been specified in the SOAP header or in the "Basic Authentication" HTTP header. In this case the username/password as specified above is used for authentication.

If this check box is cleared, all SOAP requests must contain the username and password in the SOAP header. From version 10.5.1.0042 you can also pass the username and password in a "Basic Authentication" HTTP header. Anonymous requests are blocked.

If the Activation type is none or baanlogin_ssl, this field is read-only and its value is not used. In case of baanlogin_ssl activation, the user account as passed by ION-API is always used.

Use UPN instead of User ID
This check box is only available if the Activation type is baanlogin_ssl.

If this check box is selected, the "User Principal Name" of the user is used instead of the "User ID". This option is intended for multi-domain installations.

All fields marked with an asterisk (*) are mandatory, which means that you must specify a valid value. The following fields are also required, but you do not have to fill in these fields, because they use default values.

  • Activation type
  • Connection port
  • Keep alive time
  • Max connections
  • Max references
  • Max threads

You use the following fields to enable connection pooling, which means that multiple SOAP requests can be processed through one shared physical connection:

  • Max connections
  • Max references
  • Max threads
  • Keep alive time

For more information, see the connection pooling page of the connector's online Help.

To save a new configuration, click Add. To save a modified existing configuration, click Modify. Any configuration changes do not take effect until you click one of these buttons. After successfully saving a configuration, the connector returns to the ERP Servers page.

Click Cancel to return to the ERP Servers page without saving the added or modified configuration.