This chapter contains the following topic:
The jdeinterop.ini file includes settings the server might need. The default location for the file is c:\; however, you can configure this location. Information is organized by section, for example [JDENET].
These sections are configured for the COM connector:
OCM
JDENET
Server
Security
Debug
Interop
Events
Configure these [OCM] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| DSN=ODA ITTND17 | The data source name from the system DSN of the ODBC setting. |
| OCM Datasource=COM OCM | System data source for JD Edwards EnterpriseOne client. |
| DB User=jde | User for the data source connection. |
| DB Pwd=jde | Password for the data source connection. |
| Object Owner=sysb9 | For UNIX platforms, this is the object owner in the [DB SYSTEM SETTINGS]. |
| Seperator=. | Separator used in SQL query.
For Oracle, SQL, and UDB databases, the separator is period (.); for IBM i, the separator is a slash (/). |
Configure these [JDENET] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| enterpriseServerTimeout=90000 | Timeout value for a request to the JD Edwards EnterpriseOne enterprise server. |
| maxPoolSize=30 | JDENET socket connection pool size. |
Configure these [SERVER] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| glossaryTextServer=JDED:6010 | The JD Edwards EnterpriseOne enterprise server and port that provide glossary text information. |
| codePage=1252 | The encoding scheme, such as:
1252 English and Western European. 932 Japanese. 950 Traditional Chinese. 936 Simplified Chinese. 949 Korean. |
Configure this [SECURITY] setting for the COM connector.
| Setting and Typical Value | Purpose |
|---|---|
| NumServers=1 | Number of security servers set. |
Configure these [DEBUG] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| JobFile=c:\Interop.log | Location of error file. |
| DebugFile=c:\InteropDebug.log | Location of debug file. |
| log=c:\net.log | Location of log file. |
| debugLevel=0 - 12 | Defines the level of tracing provided by the COM connector and the CallObject component in the specified log file, in the COM server only.
0 None: Logging is turned off and only errors are written to the JobFile. 2 Errors (error messages). 4 System Errors (exception messages). 6 Warning Information. 8 Min Trace (Key operations; for example, Login, Logoff, Business Function calls). 10 Trouble Shooting Information (Help). 12 Complete Debug Information (Logs everything). Note: The odd values are reserved for future levels to be added. You typically do not need to use tracing. However, tracing is useful for debugging. |
| netTraceLevel=0 | Defines the level of tracing provided by the ThinNet component in the specified log file, in the COM server only.
0 No trace. 1 Record process ID, thread ID, and the available socket status when a new connection is added and the socket pool is searched. 2 Includes the information in trace level 1 and also traces every call made in the Connection Manager class. 3 Includes all information in trace level 2, and also traces getPort calls and getHost calls. Note: You typically do not need to use tracing. However, tracing is useful for debugging. |
Configure these [INTEROP] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| SettingTime=60000 | Enables the connector to access and retrieve event information from the F90703 and F90704 tables. Defines the time for the connector applications to start up before the connector starts recovering an event.
This value is milliseconds. |
| RecoveryInterval=10000 | Enables the connector to access and retrieve event information from the F90703 and F90704 tables. Defines the time for the connector applications to start up before the connector starts recovering an event.
This value is milliseconds. |
| enterpriseServer=JDED | The JD Edwards EnterpriseOne server. |
| port=6010 | The port number of the JD Edwards EnterpriseOne server. |
| manual_timout=300000 | The time-out value for a transaction in manual commit mode. |
| Repository=c:\JDEdwards\ Interop\repository | Points to the location of the repository directory containing business object libraries (generated JAR files). |
Configure these [EVENTS] settings for the COM connector:
| Setting and Typical Value | Purpose |
|---|---|
| UseGuaranteedEvents System= True | Indicates guaranteed event delivery. Values are true and false. Must be set to True to use guaranteed event delivery. |
| Transport=HTTP | Defines the event transport mechanism. Valid values are HTTP and JMS. The default value is HTTP. |
| eventServiceURL=http://<HOST>:<PORT>/ e1events/EventClientService For a clustered transaction server: eventServiceURL=http://<HOST1>:<PORT1>/ If there are more servers in a cluster, then the eventServiceURL can be appended with | as a delimiter; for example: http://<HOST1>:<PORT1>/e1events/ |
Locates the event service. If the value for the Transport= setting is HTTP, then this setting must be configured.
For WebLogic, these ports are the Listen Port. For WebSphere, these ports are the default http ports found under Server > Communication > Ports > WC_defaulthost. |
| jndiProviderURL=
For WebLogic: jndiProviderURL=t3//<HOST>:<PORT> For a clustered transaction server: t3://<HOST1>:<PORT1>;<HOST2>:<port3> If there are more servers in a cluster, then the jndiProviderURL can be appended with ; as a delimiter; for example: t3://<HOST1>:<PORT1>;<HOST2>:<PORT2>; For WebSphere: jndiProviderURL=corbaloc::<HOST>:<PORT>/ For a clustered transaction server: corbaloc::<HOST1>:<PORT1>,: If there are more servers in a cluster, then the jndiProviderURL can be appended with ,; as a delimiter; for example: corbaloc:://<HOST1>:<PORT1>;<HOST2>:<PORT2>; |
Locates the event service. If the value for the Transport= setting is JMS, then this setting must be configured.
For WebLogic, these ports are the Listen Port. for WebSphere, these ports are the Bootstrap ports. |
| eventReceiveTimeout=60000 | Maximum number of milliseconds that the event receiver waits before unsubscribing the event from the JD Edwards EnterpriseOne server. |
| initialContextFactory=
For WebLogic: initialContextFactory=weblogic.jndi.WLInitialContextFactory For WebSphere: initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory |
Initial Context Factory |
| port=6002 | The socket port number where the EventListener receives the events from the JD Edwards EnterpriseOne server. This port should not be used by any other resource. Also, the port should not be changed dynamically when the connector is running, as this causes subsequent subscriptions to be lost. |
| ListenerMaxConnection=10 | The maximum number of connections allowed by the EventListener. The default number of connections is 10, but you can change this number. The maximum number of connections allowed is 64. |
| ListenerMaxQueueEntry=10 | The maximum number of events that the EventListener can hold before processing by the EventManager. The default number of events for the queue is 10, but you can change this number. The maximum number of events that can be held in the queue is 100. |
| Outbound_timeout=1200000 | Maximum number of milliseconds that the EventManager waits before unsubscribing the transient event from the JD Edwards EnterpriseOne server. |
This section has a single setting, CLASSPATH. Note that you must include the full directory path of each file, separating each file by a semicolon. For example, CLASSPATH=connector.jar;EventProcessor_JAR.jar;System_JAR.jar.
Note:
JD Edwards EnterpriseOne Tools Release 9.1 Update 4 and later releases require a different set of jar files.For Tools Releases prior to JD Edwards EnterpriseOne Tools Release 9.1 Update 4, copy these files from the JD Edwards EnterpriseOne server to a directory on the machine that you want to use. Unless otherwise noted, the following files can be found in the <JD Edwards EnterpriseOne Windows client installation directory>\system\classes folder:
ApplicationAPIs_JAR.jar
ApplicationLogic_JAR.jar
Base_JAR.jar
BizLogicContainer_JAR.jar
BizLogicContainerClient_JAR.jar
BusinessLogicServices_JAR.jar
castor.jar
commons-httpclient-3.0.jar
commons-logging.jar
Connector.jar
EventProcessor_JAR.jar
Generator.jar
j2ee1_3.jar
JdbjBase_JAR.jar
JdbjInterfaces_JAR.jar
JdeNet_JAR.jar
jmxremote.jar
jmxremote_optional.jar
jmxri.jar
ManagementAgent_JAR.jar
Metadata.jar
MetadataInterface.jar
PMApi_JAR.jar
Spec_JAR.jar
System_JAR.jar
SystemInterfaces_JAR.jar
xalan.jar
xerces.jar
xmlparserv2.jar
The path to the directory where the jdeinterop.ini, jdbj.ini, and jdelog.properties files exist, which must all be in one directory.
The full path to the JDBC driver files, including the filenames.
The CLASSPATH entry must end with a slash (\), which indicates it is a directory name and not a file name.
If you are using JD Edwards EnterpriseOne Tools Release 9.1 Update 4 or a later release, copy the following files from the <JD Edwards EnterpriseOne Windows client installation directory>\system\class folder:
ApplicationAPIs_JAR.jar
ApplicationLogic_JAR.jar
Base_JAR.jar
BizLogicContainer_JAR.jar
BizLogicContainerClient_JAR.jar
BusinessLogicServices_JAR.jar
castor.jar
commons-codec.jar
commons-lang2.6.jar
commons-logging.jar
Connector.jar
EventProcessor_JAR.jar
Generator_JAR.jar
httpclient.jar
httpcore.jar
httpmime.jar
j2ee1_3.jar
JdbjBase_JAR.jar
JdbjInterfaces_JAR.jar
JdeNet_JAR.jar
jmxremote.jar
jmxremote_optional.jar
jmxri.jar
ManagementAgent_JAR.jar
Metadata.jar
MetadataInterface.jar
PMApi_JAR.jar
Spec_JAR.jar
System_JAR.jar
SystemInterfaces_JAR.jar
xerces.jar
xml-apis.jar
xmlparserv2.jar
The path to the directory where the jdeinterop.ini, jdbj.ini, and jdelog.properties files exist, which must all be in one directory.
The full path to the JDBC driver files, including the filenames.
The CLASSPATH entry must end with a slash (\), which indicates it is a directory name and not a file name.
Note:
For all releases, the files on the client side and Transaction server side must always match. This is important if the Transaction server is updated.Normally IBM WebSphere MQ is included as part of other WebSphere applications, including the WebSphere Application Client. If you use WebSphere for the Java connection, you must include these additional files.
com.ibm.mqjms.jar
Normally located in the <IBM WebSphere MQ installation directory>/Java/lib folder.
com.ibm.mq.jar
Normally located in the <IBM WebSphere MQ installation directory>/Java/lib folder.
com.ibm.ws.ejb.thinclient_7.0.0.jar
Normally located in the <WebSphere installation directory>\runtime fold.
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
Normally located in the <WebSphere installation directory>\runtime folder.
com.ibm.ws.orb_7.0.0.jar
Normally located in the <WebSphere installation directory>\runtime folder.
Note:
The files on the client side and Transaction server side must always match. This is important if the Transaction server is updated.