Configure Connection point

Use this wizard to define the properties of a Connection Point.

Related topics

- Introduction
- To configure connection points
- To define the log configuration

Configure Connection point

Use this page to specify the general properties of a connection point.

Fields
Fields | Description
Connection point
Name | The name of the connection point.
Description | The description of the connection point.
Connection sharing
Share connection | If this check box is selected, the connection point is linked to another connection point. If both connection points connect to the same ERP LN environment, sharing connection points is useful. Therefore, to improve the performance, only 1 bshell is used to connect to the back-end.
Shared Connectionpoint | The connection point to which the current connection point is linked. The current connection point will use all connection properties of this connection point, except the company number.
Company | The Infor ERP company number used in the ERP application.
Activation
Activation Type | The activation type used to establish a connection between your local machine and the back-end. Most activation types start a bshell on the ERP LN application server; you can choose from one of the following:
Activation Type | Description
Rexec | Starts a bshell using the rexec protocol, which sends the username and password over the network without encryption.
BaanLogin | Starts a bshell using the BaanLogin protocol, which is more secure than rexec protocol because the username and password are encrypted before they are sent over the network.
BW | Starts a bshell using the settings specified in a BW Configuration file (.bwc file).
None | If you select value `none`, remote activation is disabled, which means that you must manually start a bshell and an ottstpjcadaemon on the ERP LN application server. You will only use this option for back-end debugging.
Socket-In | Establishes a connection from the back-end to a port number on your local machine. This activation type is used to send debugging messages from the back-end to the Application Studio on your local machine.

Properties for activation type BW

Use this page to define properties for connection points with activation type `BW`.

Fields
Fields | Description
BW Activation
Configuration file | The .bwc file that contains the connection settings.
Class name | Read-only field taken from the selected .bwc file.
Company | The Infor ERP company number used in the ERP application.

Commands
Commands | Description
Browse | Starts the Select a Configuration File dialog, where you can select a .bwc file.

Properties for activation types BaanLogin, Rexec, and None

Use this page to define properties for connection points with activation type `Rexec`, `BaanLogin`, or `None`.

Note

If Activation type is `None`, you can specify only a Hostname and a Connection port.

Fields
Fields | Description
ERP LN Connection
Hostname | The TCP/IP hostname or IP address of the ERP back-end.
Connection port | The used TCP/IP port number on the ERP application server. If Activation type is `Rexec`, the port number is read-only and fixed to 512. If Activation type is `BaanLogin`, the default port number is 7150. However, you can select any other valid port number. If Activation type is `None`, this port number must correspond with the port number used by the ottstpjcadaemon.
ERP LN Application Server
User | The user name used for authentication on the ERP application server.
Password | The password used for authentication on the ERP application server.
Bse | The directory on the application server where the Infor ERP Software Environment resides.
Company | The Infor ERP company number used in the ERP application.
Bshell | The logical name of the bshell, as specified in configuration file ${BSE}/lib/ipc_info.
Environment | Optional field that contains the environment settings for the bshell process. For example: To set the environment variable BOL_PUBLISHER_TRACE, enter `-set BOL_PUBLISHER_TRACE=<path>/publisher_trace.txt`. To set the environment variable TRACEJCA to 1, enter `-set TRACEJCA=1`. This has the same effect as selecting the Trace Backend option.
Trace Backend | If this check box is selected, a trace file is generated on the server. In this file the activities of the ottstpjcadaemon and ottstpbdeman processes are traced. The file is called `trace.jca<bshell.pid>`, and is located in the ${BSE}/log directory.

Properties for activation type Socket-In

Use this page to define properties for connection points with activation type Socket-In.

Fields
Fields | Description
Event consumer
Local port | The used port number on your local machine.

| Send Us Your Feedback About this Help Page