You are on page 1of 2

10/10/2017 Document 660197.

E1: OUTBND: How to test guaranteed RTE with Java Dynamic Connector (Doc ID 660197.1)

In this Document

Goal
Solution

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version 8.98 and later


Information in this document applies to any platform.

GOAL

How can you test guaranteed Real Time Events to make sure that events are able to be delivered through the transaction
server.

SOLUTION

Using the sample Java Dynamic Connector, you can verify the setup and configuration of guaranteed real time events
using the transaction server.

Extract the following files from the E812\system\classes\samples directory into a new directory making sure to select to
use folder names.

- connector_samples_src.jar
- ConnectorSamples.zip

Once extracted the .bat file to be used is called:

- runDynConNewEventDriver.bat

Edit this file and replace the existing value for java_home with appropriate directory:

REM========================================================
REM Set the environment variables
REM==========================================================
set JAVA_HOME=C:\j2sdk1.4.2_11

Go to the config directory and find the following .ini files to be configured:

- jdbj.ini
- jdeinterop.ini
- jdelog.properties

Make sure a tnsnames.ora file exists in this directory with appropriate connection info if connecting to oracle database.

In order to make sure the settings are correct for jdbj.ini, you can copy the jdbj.ini file from the transaction server. You
find this under:

X:\[JDE_Home]\targets\[transactionServerName]\config

Open the jdeinterop.ini file and make the following changes.


Make sure all port numbers are correct and E1 server name is correct within the file.

Under the following stanza complete the following parameter. Make sure the initialContextFactory setting is correct for the
Application server you are running. See examples for OAS 10.1.3.1 and WAS 6.1.0.9

[EVENTS]
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ho0e34ruu_37&id=660197.1 1/2
10/10/2017 Document 660197.1

initialContextFactory
jndiProviderURL=
eventServiceURL=

For OAS:

initialContextFactory=com.evermind.server.rmi.RMIInitialContextFactory

jndiProviderURL=opmn:ormi://[machine_name:port#:default_group/[transaction_Server_name
eventServiceURL=http://[machine_name]:[httpPort#]/e1events/EventClientService

You can find this setting in the JAS.ini for the Transaction server

Example:

jndiProviderURL=opmn:ormi://[machineName]:6003:default_group/E1_TransServer_96_EventProcessor_EAR
eventServiceURL=http://machineName:[port#]/e1events/EventClientService

For WAS:

[EVENTS]

initialContextFactory=com.evermind.server.rmi.RMIInitialContextFactory
jndiProviderURL=corbaloc:iiop:[machine_name]:[port#]/NameServiceServerRoot

Example:

jndiProviderURL=corbaloc:iiop:DENMLGSCINT1.mlab.jdedwards.com:2810/NameServiceServerRoot
eventServiceURL=http://[machineName]:[port#]/e1events/EventClientService

Open the jdelog.properties file and change the current path to absolute path so that you know where to find the logs:

Example:

FILE=c:\interop\logs\jderoot.log

To capture more details for troubleshooting, include the following components for the jas.log and jasdebug.log

COMPONENT=RUNTIME|JAS|JDBJ|EVENTPROCESSOR|INTEROP

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=ho0e34ruu_37&id=660197.1 2/2