Development >  Utilities >  Miscellaneous >  Pool of the java bridge  

Display all Hide all

Since version 108, the “Safe X3 Java Bridge Server” component has the ability to contact an X3 processing server in order to call 4GL sub-programs directly. In this way, the developers of "extends" bundles are able to connect to the available connection pools by means of the SDK Client.

This function is used to define the pools published for the solution. It is used to define the connection pools of the “Safe X3 Java Bridge Server” component in relation to a folder.

SEEINFO The connection pools are not necessarily linked to SDATA.For optimization reasons, it is recommended to set the login integration user used by the SalesLogix application as the connection pool.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Fields

The following fields are present on this tab :

Configuration

  • Pool alias (field POOLALIAS)

Identifier of the Java Bridge pool.
  • field INTITPOOL

 

The folder is the one on which sessions are opened.

This field is used to define a connection language.

  • User code (field USR)

The User code, Password, System user and System password fields are used to define the parameters required to open sessions.
  • Login (field LOGIN)

 
  • Password (field USRMDP)

The User code, Password, System user and System password fields are used to define the parameters required to open sessions.
  • System user (field USRSYST)

 
  • System password (field SYSTMDP)

 
  • Max number entries (field MAXENTRY)

The maximum number of entries must not exceed the number of entries available in the Sage X3 license.

SEEINFO Connections opened with Java Bridge are of type 7.
  • Number of initial entries (field NBENTRY)

As the web services server, the Java server opens connections in advance, in order to improve response times.

The number of initial entries corresponds to the number of opened sessions upon launching the bridge. It is lower than or equal to the maximum number of entries.

The other sessions are opened progressively, as soon as they are required.
  • Automatic start (field AUTOSTART)

 
  • Maximum time (s) (field LIFETIME)

The maximum time is the downtime (in seconds) before a session is closed. The session reopens automatically as soon as a query is run.
  • Optimization (field IMPCLI)

 

Advanced

  • Application server (field SERVEURAPP)

 
  • Process server (field SERVEURTRT)

 
  • Port (field NOPORT)

 

Close

 

Specific Buttons

When executing the Validationbutton, an XML file is generated (adxpoolconfig_SOLUTION.xml) in the X3_ROOT/GEN/ directory of the solution, on the X3 application server. If a Bridge server is linked to the solution (i.e. the solution.xml file contains its description), this Bridge server will be contacted by means of a "funciu" call to trigger the pool update.

If several Bridge servers are linked to a solution, only the server whose description appears first will be contacted upon screen validation. In this case, a manual update is possible via the "updatePools" OSGI command of the Bridge server concerned or via the Refresh button of the web interface.

This button is used to view the setup file present on disk and created by the validation function.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation