[Switch] jde910 -- Jas. ini parameter description

Configure the JAS. ini file

The JAS. ini file can use Java™Application Server (JAS) to provide jde installation configuration. You must configure the JAS. ini file for each environment-specific jde instance.

Jas. INI is located in the following directory: jde install directory \ System \ Solaris \ J2EE \ home \ applications \ WebClient. Ear \ WebClient \ WEB-INF \ Classes

The JAS. ini file contains the following parts:

[Server]
Glossarytextserver-specifies the Enterprise Server and port number used to provide Vocabulary text information. The server returns an incorrect text description. Generally, this is the same as the host and port number of the jde oneworld application server. There may be multiple vocabulary servers for different Supported languages. CodePage = references one of the following values:
1252-English and Western Europe
932-Japanese
950-Traditional Chinese
936-Simplified Chinese
949-Korean

[Jdenet] network connection parameters can be specified in this section.
The TCP/IP Port number used by the servicenameconnect-EnterpriseOne server to send the communication package.
Enterpriseservertimeout-Timeout value for requests on the iseone Server
Maxpoolsize-size of the jdenet socket connection pool

[Cache] This section defines the cache of the connector.
Usersession = 0
Specexpire = 300000000

[InterOP] This section defines inbound service function calls.
Enterpriseserver-specify the host server name or IP address. The value should be the same as the value of the "host name" field in the "jde credential" and "Default credential" panel in the configuration editor.
Port-specifies the port number used for data exchange. The value should be the same as the value of the "jde credential" field in the configuration editor and the "port number" field in the "Default credential" panel.
Manual_timeout-the timeout value (in milliseconds) of a transaction that adopts the manual implementation method ).
Repository-point to the location of the Repository directory, for example, C: \ connector \ repository.

[Events] This section defines outbound events.
Port: Specifies the port number used for data exchange.
Listenermaxconnection-Maximum number of listener connections
Listenermaxqueueentry-Maximum number of entries in the listener queue
Outbound_timeout-transaction timeout (in milliseconds)
Java Naming and directory interfaces (JNDI) can be used for communication with the J2EE server. 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 used to communicate with the event client service:

Eventserviceurl = http: // localhost: 9080/e1events/eventclientservice

[Security] This section defines the number of security servers and the IP addresses of these servers. The security server port number is the same as the servicenameconnect port number listed in jdenet.
Numservers-number of security servers
Securityserver-specify the name or IP address of the Security Server

[OCM] when it is set to true, the connector uses the object configuration ing (OCM) to find the EnterpriseOne server.
Ocmenabled = true
Stderr = c: \ stderr.txt
Stdout = c: \ stdout.txt

[Logs] This section provides a method for opening a debug trace, the location of the log file, and parameters for enabling or disabling error tracing.

Rtdebugtrace-enable (true) or disable (false) Error Tracking

Rtlog =/vobs/Maestro/bundles/connector/jde/RT. Log

Rtdebug = c: \ rtdebug. Log

Rtlogtype = All-All: bsfn | tableio | sysfunc | MISC | er | event | thread. You can also set it

Bsfn | tableio | sysfunc | MISC | er | event | any combination of threads.

[jdbj-Bootstrap session] This section contains parameters used to enable database access capabilities for jde EnterpriseOne.
User-the user ID used to connect to the system. It is an optional parameter.
password-Password identified by the user. It is an optional parameter.
environment-Environment used to connect to the jde EnterpriseOne server. This is a required parameter. To access the system using the environment, the user must have the privilege for the environment. The following environments can be used to access the system:
Development Environment (dv812)
production environment (pd812)
prototype environment (py812)
original environment (ps812)
role-This specifies the role of the connected 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 information specified in the DB system settings section of the jde. ini file.
name-specifies the name of the data source.
databasetype-specifies the database type used by the system. Use one of the following types:
I = AS/400®
O = Oracle
S = SQL server
W = UDB
M = MSDE
name of the server-performaniseone host server. It applies to IBM®AS/400 and SQL Server.
SERVERPORT-specifies the port number of the EnterpriseOne host server. It applies to Microsoft®SQL Server.
database-database instance name. It is applicable to Oracle databases and IBM DB2®.
physicaldatabase-physical database (used as the database qualifier for ibm as/400 ). This tool is applicable to Microsoft SQL Server and IBM AS/400.
owner-this is the data source owner. This applies to Oracle databases, Microsoft SQL Server, and IBM DB2 UDB.
lob-Specifies whether lob is supported. This applies to Oracle databases and ibm as/400.
Unicode-Indicates whether Unicode conversion is supported by a Boolean value (Y or N ). This applies to Microsoft SQL Server.

[Jdbj-Spec data source] This section defines the data source where the serialization specification table is located. Jdbj uses this method to search for serialized standard objects as needed at the time of execution of the pilot program. Jdbj first searches for the name specified in this section in the data source master table (f98611. If a data source can be found, the data source is used to read the serialization specification table. If the data source is not found in the data source main table, the new data source is initialized Based on the remaining fields in this section. If this part is not specified, jdbj uses OCM to find the serialization specification table. Use the jdbj-Bootstrap data source section to obtain information about the fields that must be filled in for various database types.

[Jdbj-JDBC drivers] This section lists the JDBC drivers of the database.
Oracle = oracle. JDBC. Driver. oracledriver
As400 = com. IBM. as400.access. as400jdbcdriver
Sqlserver = com. Microsoft. JDBC. sqlserver. sqlserverdriver
UDB = com. IBM. db2.jdbc. App. db2driver

Set [jdbj-logs] to true to enable the JDBC driver record function. This parameter cannot control jdbj records (which will be controlled by jdelog. properties ).

Jdbctrace = false

[Jdbj-server] This section applies to iseries/as400. When jdbj references iseries®Set double-byte data to true. When this parameter is set to false, explicit checks for double-byte characters with incorrect formats in iseries data are disabled.

Dbcsconversiontolerant = false

[Jdbj-connection pool] This section defines the connection pool parameters.
Minconnection-minimum number of connections to the data source. After the old connection is closed, the number of connections set by this parameter will remain in the pool (whether or not the connection is used ). The valid value is 0 or greater. The default value is 5.
Minconnection = 5
Maxconnection-Maximum number of connections to the data source (for all users ). Other connection requests exceeding this value will be queued to wait for the next available connection. The valid value is 1 or greater and must be equal to or greater than "minconnection". The default value is 50.
Maxconnection = 50
Initialconnection-Number of connections to be initialized when a pool is created. The valid value must be equal to or greater than "minconnection" and equal to or less than "maxconnection". The default value is 5.
Initialconnection = 5
Poolgrowth-the incremental connection (as long as it does not reach the maxconnection value) created when the current allocation cannot meet the connection request ). Valid value: the basic rule is (poolgrowth> = maxconnection/10 ). The default value is 5.
Poolgrowth = 5
Connectiontimeout-the amount of time (in milliseconds) when the connection is marked as idle before it is cleared ). Setting this value to a higher value may improve performance. Reducing this value may reduce memory usage. The valid value is 0 or greater. The default value (in milliseconds) is 1800000 (30 minutes ).
Connectiontimeout = 1800000
Cleanpoolinterval-interval (in milliseconds) set by the pool cleaner to clean data sources containing verification strings ). When cleaning, all connections marked as idle will be cleared. The maximum time between idle connections and cleanup can be the sum of the connectiontimeout value and cleanpoolinterval value. The valid value is 0 or greater. The default value is 600000 (10 minutes ).
Cleanpoolinterval = 600000
Maxsize-Maximum number of JDBC prepared statements connected to the cache by each JDBC. The valid value is 0 or greater. The default value is 50.
Maxsize = 50
Cachepurgesize-the number of JDBC prepared statements to be cleared from the JDBC connection after the maxsize limit is reached. The cleared statement is the statement that is not used for the longest time in the cache. Valid values (based on basic rules) are (cachepurgesize> = maxsize/10 + 2 ). The default value is 5.
Cachepurgesize = 5

 

The preceding content is transferred from:

Http://pic.dhe.ibm.com/infocenter/wci/v6r0m0/index.jsp? Topic=%2fcom.ibm.websphere.cast_iron.doc%2fjde_javasing_the_jas.ini_file.html

[Switch] jde910 -- Jas. ini parameter description