Defining connectivity settings
This section describes the procedure to define connectivity settings for the LN Studio.
Infor LN Studio
uses
Connection Points
to connect to the
LN
server that contains the
LN
applications and the
development repository, and to the server on which the software projects are
stored.
This table shows the static connection points you must configure to
define the connectivity settings:
Connection point
Description
ProjectServer
This connection
point is used to connect to the
Project Server.
The
Project Server
contains projects and activities that are used in the
Infor LN Studio.
The
Project Server
connection point is used, for example:
When a
project
manager creates a new project, or a new activity in the
Software Project Explorer view.
When a
software
engineer starts the
Open an Activity wizard from the
Activity Explorer view.
Debug
When a software
engineer debugs a session from the
LN Studio,
the debugger on the
LN
server uses this connection point to send messages to the
LN Studio
on the client PC.
RuntimeRepositoryConnection
This connection point is used
for exchanging business metadata with the application server. This connection
is not required if the interface project is using "related software projects".
TestServerConnection
This connection point is used
when testing Business Interface implementations. This connection is not
required if the interface project is using "related software projects".
Configuring static connection points
To configure the connection points:
Display the standard
connection points
On the Eclipse
Windows menu,
select Preferences.
The Preferences dialog appears.
In the tree that is
displayed in the left pane of the dialog, select Infor LN JCA Connectivity. The Infor LN JCA Connectivity dialog is displayed.
The dialog shows the standard Debug and Project Server connection points, which were defined by LN Studio by default.
The Infor LN JCA
Connectivity dialog is part of the connectivity plug-in. For
details, see the dialog's online help and to the online help of the Infor
Connectivity plug-in.
Configure the connection
points
To configure a connection point, select the connection point and
click
Edit. The
Configure Connection point wizard starts.
Specify the properties for the connection points and close the wizard.
This table shows points of attention per static connection point:
Connection
point
Points of
attention
ProjectServer
Select the
appropriate activation type:
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 after setting up a "Cloud Environment". To connect to a
single-tenant cloud installation of LN, specify the
HTTP-Basic activation type.See "Specifying additional settings for cloud
development".
The company number for this connection point must be
000.
The application and project data accessed through these
connection points can reside in the same
LN
environment. If so, you can share these connection points. As a result, only
one bshell is used to connect to the server, instead of two, which improves the
performance.
Debug
Select
the Socket-In activation type.
Select a free local port number, such as
10100.
RuntimeRepositoryConnection
Select the
BaanLogin (recommended),
Rexec, or
BW activation type, and specify the
corresponding settings.
The company number for this connection point must be
000.
TestServerConnection
Select the
BaanLogin (recommended),
Rexec, or
BW activation type, and specify the
corresponding settings.
The
Configure Connection point wizard is part of
the connectivity plug-in. For details, see the wizard's online help and the
online help of the Infor Connectivity plug-in.
You can use the Preferences dialog box to
set various other user preferences for the LN Studio workbench. See "Application preferences",
"Integration preferences", and "Connectivity preferences" in the
Infor LN Studio
Administration Guide.
To run or debug sessions after creating or modifying the Debug connection point,
you must restart LN Studio.
In a multi-tenant environment you cannot debug with LN Studio. You can use the Debug Workbench, see the
Debug and Profile 4GL (ttadv1123m000) session.
In a multi-tenant environment you cannot run or debug BFlows with LN Studio. You can run BFlows in the
LN UI to see the result.