Configuring the jas.ini file

The jas.ini file provides configuration for JDE installations using the Java Application Server (JAS). You must configure the jas.ini file for each environment specific JDE instance.

The jas.ini is located in the following directory:

JDE INSTALL DIRECTORY\System\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes

The jas.ini file has the following sections:

[SERVER]

glossaryTextServer – Specifies the enterprise server and port number that supply glossary text information. This server returns text descriptions for errors. This is often the same host and port number as the JDE OneWorld application server. There can be more than one glossary server for different supported languages. The codepage = refers to one of the following values:
  • 1252 – English and Western European
  • 932 – Japanese
  • 950 – Traditional Chinese
  • 936 – Simplified Chinese
  • 949 – Korean

[JDENET]

This section specifies network connection parameters.
  • serviceNameConnect – the TCP/IP port number the EnterpriseOne Server uses to send communications packets.
  • enterpriseServerTimeout – the timeout value for a request to the EnterpriseOne Server
  • maxPoolSize – the JDENET socket connection pool size

[CACHE]

This section defines the cache for the connector.
  • UserSession=0
  • SpecExpire=300000000

[INTEROP]

This section defines inbound business function calls.
  • enterpriseServer – specifies the name or IP address of the host server. The value should be the same value as in the Host Name field in the JDE Credentials and Default Credentials panels in the Configuration Editor.
  • port – specifies the port number for the exchange of data. The value should be the same value as in the Port Number field in the JDE Credentials and Default Credentials panels in the Configuration Editor.
  • manual_timeout – the timeout value, in milliseconds, for a transaction in manual commit mode.
  • Repository – points to the location of the repository directory, for example, c:\connector\repository.

[Events]

This section defines outbound events.
  • port – specifies the port number for the exchange of data
  • ListenerMaxConnection – the maximum number of listener connections
  • ListenerMaxQueueEntry – the maximum number of entries in a listener queue
  • outbound_timeout – the timeout, in milliseconds, for a transaction

Communication with the J2EE server is accomplished using Java Naming and Directory Interface (JNDI). The following code is an example:

initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory

jndiProviderURL=corbaloc:iiop:localhost:2809

The following code is an example of a URL for communicating with the event client service:

eventServiceURL=http://localhost:9080/e1events/EventClientService

[Security]

This section defines the number of security servers and the IP address for the servers. The port number for the security servers is the same as the port number listed in JDENET – serviceNameConnect.
  • NumServers – specifies the number of security servers
  • SecurityServer – specifies the name or IP address for the security server

[OCM]

When set to True, the connector uses Object Configuration Mapping (OCM) to find the EnterpriseOne Server.
  • OCMEnabled=true
  • stderr=c:\stderr.txt
  • stdout=c:\stdout.txt

[LOGS]

This section provides a way to turn on debug trace, locations of log files, and a parameter to turn bug tracing on or off.

rtdebugTrace – Turn bug tracing on (True) or off (False

rtlog=/vobs/maestro/bundles/connector/jde/rt.log

rtdebug=c:\rtdebug.log

rtlogType=All – All specifies all of the following: BSFN|TableIO|SYSFUNC|MISC|ER|EVENT|THREAD. You can also set it equal to any combination of BSFN|TableIO|SYSFUNC|MISC|ER|EVENT|THREAD.

[JDBj-BOOTSTRAP SESSION]

This section has parameters that enable database access capabilities for JDE EnterpriseOne.
  • user – User ID used to connect to the system. It is an optional parameter.
  • password – Password for the user ID. It is an optional parameter.
  • environment – The environment used to connect to the JDE EnterpriseOne server. This is a required parameter. To access the system using an environment, the user must have privileges for that environment. The following environments can be used to access the system:
    • Development Environment (DV812)
    • Production Environment (PD812)
    • Prototype Environment (PY812)
    • Pristine Environment (PS812)
  • role – This specifies the role of the connecting user. It is an optional parameter.

[JDBj-BOOTSTRAP DATA SOURCE]

This section defines the data source. The parameters and information in this section should match the corresponding information specified in the DB SYSTEM SETTINGS section of the JDE.INI file.
  • name – Specifies the name of the data source.
  • databaseType – Specifies the type of database used by the system. Use one of the following types:
    • I = AS/400®
    • O = Oracle
    • S = SQL Server
    • W = UDB
    • M = MSDE
  • server – Name of the EnterpriseOne host server. It is applicable for IBM® AS/400 and SQL Server.
  • serverPort – Specifies the EnterpriseOne host server port number. It is applicable for Microsoft SQL Server.
  • database – Database instance name It is applicable for Oracle Database and IBM DB2® UDB.
  • physicalDatabase – The physical database (used as library qualifier for IBM AS/400). It is applicable for Microsoft SQL Server and IBM AS/400.
  • owner – This is the owner of the data source. This is applicable for Oracle Database, Microsoft SQL Server, and IBM DB2 UDB.
  • lob – Specifies whether lobs are supported. This is applicable for Oracle Database and IBM AS/400.
  • unicode – Boolean value (Y or N) that indicates support for Unicode conversion. This is applicable for Microsoft SQL Server.

[JDBj-SPEC DATA SOURCE]

This section defines the data source where the serialized spec tables reside. JDBj uses this at bootstrap time and after to look up serialized spec objects on demand. JDBj first looks for the name specified in this section in the Data Source Master table (F98611). If it finds a data source there, it uses it to read the serialized spec tables. If it does not find the data source in the Data Source Master table, it initializes a new data source based on the rest of the fields in this section. If this section is not specified, JDBj uses OCM to find the serialized spec tables. Use the  JDBj-BOOTSTRAP DATA SOURCE section for information on which fields must be filled in for each database type.

[JDBj-JDBC DRIVERS]

This section lists the JDBC drivers for the databases.
  • ORACLE=oracle.jdbc.driver.OracleDriver
  • AS400=com.ibm.as400.access.AS400JDBCDriver
  • SQLSERVER=com.microsoft.jdbc.sqlserver.SQLServerDriver
  • UDB=COM.ibm.db2.jdbc.app.DB2Driver

[JDBj-LOGS]

Set to True to enable logging by JDBC drivers. This parameter does not control JDBj logging which is controlled by jdelog.properties.

jdbcTrace=false

[JDBj-SERVER]

This section is for iSeries/AS400. Set to true when JDBj is referencing iSeries® double-byte data. When set to false, disables explicit checking for malformed double-byte characters in iSeries data.

dbcsConversionTolerant=false

[JDBj-CONNECTION POOL]

This section defines the connection pool parameters.
  • minConnection – The minimum number of connections to a data source. When closing old connections, the number of connections set by this parameter will remain in the pool regardless of use. A valid value is 0 or greater; the default value is 5.

    minConnection=5

  • maxConnection – The maximum number of connections to a data source for all users. Additional connection requests beyond this value are queued for the next available connection. Valid values are 1 or greater and equal to or greater than "minConnection"; the default value is 50.

    maxConnection=50

  • initialConnection – The number of connections to initialize upon pool creation. A valid value is a value equal to or greater than "minConnection" and equal to or less than "maxConnection"; the default value is 5.

    initialConnection=5

  • poolGrowth – The increment of connections the system will create when a request for a connection cannot be satisfied with the current allocation as long as the maxConnection value has not been reached. Valid values: The rule of thumb is (poolGrowth >= maxConnection/10). The default value is 5.

    poolGrowth=5

  • connectionTimeout – The amount of time, in milliseconds,  that a connection remains idle before it is flagged for cleanup. Setting this value high might improve performance. Reducing the value might reduce memory consumption. A valid value is 0 or greater. The default value, in milliseconds, is 1800000 (30 minutes).

    connectionTimeout=1800000

  • cleanPoolInterval – The interval, in milliseconds, that the pool cleaner is set to clean data sources that have a validation string. When cleaning occurs, any connections that are flagged as idle will be cleaned up. The amount of time between a connection becoming idle and being cleaned up can be as long as the connectionTimeout value plus the cleanPoolInterval value. A valid value is 0 or greater. The default value is 600000 (10 minutes).

    cleanPoolInterval=600000

  • maxSize – The maximum number of JDBC prepared statements cached on each JDBC connection. A valid value is 0 or greater. The default value is 50.

    maxSize=50

  • cachePurgeSize – The number of JDBC prepared statements purged from a JDBC connection if the maxSize limit is reached. The statements purged are the statements in the cache which have not been used for the longest amount of time. A valid value, by rule of thumb, is (cachePurgeSize >= maxSize/10 + 2). The default value is 5.

    cachePurgeSize=5