Defining dynamic connection points
Dynamic connection points
LN Studio uses the following dynamic Connection Points:
Dynamic connection point | Description | Configuration |
---|---|---|
Administrator | Enables you to
perform administrative tasks on the
LN
server.
The connection point is used, for example:
|
Configure this connection point for each LN server, on which you want to perform administrative tasks or development tasks. |
Development Address | Is used to
connect to the development repository on the
LN
server.
This connection point is used, for example, when a software engineer:
|
Configure these connection points for each software project, in which you develop software. |
Runtime Address | Sends information to the LN server when you run or debug a session from the LN Studio. |
You are prompted to configure these connection points, the first time you open an activity linked to the software project. See the following section.
Configuring dynamic connection points
To configure the dynamic connection points mentioned, complete the following steps:
- Select the project
Complete these steps:
- Open the Application perspective: On the menu, select , and subsequently click . Select from the list and click .
- In the Activity Explorer view, click . The Open an Activity dialog box is displayed.
- Select the software project from the list. A question window is displayed: you are prompted to configure the corresponding Administrator connection point.
Note: This question is displayed only the first time you open an activity for the project. - Configure the
Administrator connection point
Complete these steps:
- In the question window, click Configure Connection point wizard starts. . The
- Specify the
properties for the connection point.
Points of attention:
- To connect to
an on-premises installation of LN, select the BW, Rexec, or
BaanLogin activation type, and
specify the corresponding settings.
To connect to a multi-tenant cloud installation of LN, specify the HTTP-OAuth2 activation type.
To connect to a single-tenant cloud installation of LN, specify the HTTP-Basic activation type.
- Select company number 000.
- The application and project data can reside in the same LN environment. If so, you can share the Administrator and ProjectServer connection points. As a result, only one bshell is used to connect to the server, instead of two. This improves the performance.
See the wizard's online help.
- To connect to
an on-premises installation of LN, select the BW, Rexec, or
BaanLogin activation type, and
specify the corresponding settings.
- To save the connection point and to close the wizard, click . A question window is displayed: you are prompted to configure the Development Address and Runtime Address connection points.
- Configure the Development
Address and Runtime Address connection points
Complete these steps:
- In the question
window, click
Configure Connection point wizard starts and
automatically generates these connection points:
- <project name>_dev (Development Address)
- <project name>_rt (Runtime Address)
. The
- Specify the
properties for these connection points.
Points of attention:
-
Development
Address
- To
connect to an on-premises installation of LN, select the BW activation type and specify the corresponding
settings.
To connect to a multi-tenant cloud installation of LN, specify the HTTP-OAuth2 activation type.
To connect to a single-tenant cloud installation of LN, specify the HTTP-Basic activation type.
- The company number for this connection point must be 000.
- To
connect to an on-premises installation of LN, select the BW activation type and specify the corresponding
settings.
-
Runtime
Address
- To
connect to an on-premises installation of LN, select the BW activation type and specify the corresponding
settings.
To connect to a multi-tenant cloud installation of LN, specify the HTTP-OAuth2 activation type.
To connect to a single-tenant cloud installation of LN, specify the HTTP-Basic activation type.
- A runtime address is always linked to a particular company number, such as company 100, on the LN server.
- To
connect to an on-premises installation of LN, select the BW activation type and specify the corresponding
settings.
If the development repository and the application data accessed through these connection points reside in the same LN environment, you can share these connection points. As a result, only one bshell is used to connect to the server, instead of two. This improves the performance.
See the wizard's online help.
-
Development
Address
- To save the connection point and to close the wizard, click .
You can now open an activity for the project.
- In the question
window, click
Configure Connection point wizard starts and
automatically generates these connection points:
Modifying existing connection points
To modify the configuration properties of existing connection points:
- Select Preferences dialog box is displayed. . The
- In the tree in the left pane of the dialog box, select Infor LN JCA Connectivity dialog box is displayed. The dialog box shows the connection points. See the dialog box's online help. . The
- To configure a connection point, select the connection point and click Configure Connection point wizard starts. Modify the properties for the connection point and close the wizard. . The