Oracle BAM Enterprise Message Source and JDE Integration Contributors: Suzanne D’Souza Nami Fujiyama
Oracle BAM Enterprise Message Source
and JDE Integration
Contributors: Suzanne D’Souza
Nami Fujiyama
RTE Setup for JMSQueue Subscriber. WebLogic
Page 2 of 31
Table of Contents
Transaction Server Installation and Configuration for Oracle WebLogic Server ................................................ 3
1 Transaction Server Installation .............................................................................................................................. 3 1.1 Check the Technical Requirements ................................................................................................................. 3 1.2 Download the RTE Component ...................................................................................................................... 3 1.3 ESUs Required ................................................................................................................................................ 3
2 Transaction Server Configuration in Server Manager ........................................................................................... 4 2.1 Network Settings Configuration ..................................................................................................................... 4 2.2 Real Time Events Configuration ..................................................................................................................... 4
3 Transaction Server Configuration in E1 ................................................................................................................ 5 3.1 Clear E1 the Tables ......................................................................................................................................... 5 3.2 Run DBTemplates ........................................................................................................................................... 5 3.3 Configure and Activate RTSOOUT ................................................................................................................ 6
4 JMSQUEUE Subscriber Configuration in EnterpriseOne ..................................................................................... 9 4.1 Create a JMSQUEUE Subscriber ................................................................................................................... 9 4.2 Create a Subscription .................................................................................................................................... 10 4.3 Add an Event (RTSOOUT) to the Subscription ............................................................................................ 11 4.4 Add Environment to Subscription ................................................................................................................. 12
5 Create a JMS Queue in the Transaction Server Application ............................................................................... 13 5.1 Create the JMS Connection Factory ............................................................................................................. 13 5.2 Create a JMS Queue ...................................................................................................................................... 18
Configure the Oracle BAM Enterprise Message Sources ...................................................................................... 20
6 Create an Oracle BAM Data Object .................................................................................................................... 20
7 Define an Oracle BAM Enterprise Message Source ............................................................................................ 21
Appendix A: Testing and Validating the JMSQUEUE Configuration ................................................................. 25
Appendix B: Initial Information to Provide When Creating a Service Request .................................................. 31
RTE Setup for JMSQueue Subscriber. WebLogic
Page 3 of 31
Transaction Server Installation and Configuration for Oracle
WebLogic Server
1 Transaction Server Installation
1.1 Check the Technical Requirements
Make sure you check that your platform complies with the published Technical Requirements found in
Document Id 705378.1
1.2 Download the RTE Component
Transaction Server can be downloaded from Update Center or via Change Assistant.
The component to download is called 89xTy. For example the Transaction Server for 8.98.2.0 is called
898T20.
The Transaction Server is installed via Server Manager in the same way as other E1 components. Prior to
creating the RTE instance in Server Manager, you must log on to your Oracle WebLogic Administrator
Console to create the Server that will contain your RTE Application (see example below). The port
number selected to create the Server in Oracle WebLogic Administrator Console must match the value
entered when creating the RTE Instance in Server Manager.
1.3 ESUs Required
The following ESUs are required
For E1 release E90: JL13125
For E1 release 812: JK18727
For E1 release 811sp1: JJ17498
RTE Setup for JMSQueue Subscriber. WebLogic
Page 4 of 31
2 Transaction Server Configuration in Server Manager
2.1 Network Settings Configuration
The Outgoing JDENET Port is the E1 Port to which the RTE will communicate with the E1 server (E1 Port).
The Incoming JDENET Port is the port the Transaction Server listens from for incoming messages
(outgoing RTE from E1).
2.2 Real Time Events Configuration
In Configuration>Real Time Events, make sure you enter the login name and password for your Oracle
WebLogic Server Administration Console.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 5 of 31
3 Transaction Server Configuration in E1
Note: If you are configuring RTE for the first time in your environment, follow steps in sections
3.1 Clear E1 the Tables and 3.2 Run DBTemplates, otherwise, skip to section 3.3 Configure and
Activate RTSOOUT.
3.1 Clear E1 the Tables
E1 might come with data in the following table.
Clear tables F90705, F90706, F90707, F907071, F907072, F90710, F90711, F90712, F90715.
Clear the contents of the above tables before proceeding.
3.2 Run DBTemplates
DBTemplates is an executable that is provided as part of the E1 Client installation. It performs some
database operations that are important for a fully functioning Transaction Server.
Make sure you assign the appropriate privileges to your E1 System tables as outlined below:
DB2/400
No special privileges are required.
DB2 UDB
Grant the following privileges to the database proxy user. Replace jde in the following
script with the actual database proxy user name and the SY812 as required.
GRANT CONTROL ON TABLE SY812.F90710 TO USER jde
Oracle
Grant the following privileges to the JDE_ROLE or the database proxy user. GRANT CREATE ANY SEQUENCE TO JDE_ROLE; GRANT DROP ANY SEQUENCE TO JDE_ROLE;
GRANT CREATE ANY TRIGGER TO JDE_ROLE; GRANT DROP ANY SEQUENCE TO JDE_ROLE;
SQL Server
The database proxy user must have the privileges to create database triggers. Replace jde
with the actual database proxy user name. Exec sp_addrolemember db_owner,jde
From an E1 Client, while logged off the E1 Client, run DBTemplates from the DOC Command line:
C:\>dbtemplates
You should be prompted to log on to E1. Log on to the appropriate Environment.
Once DBTemplates has run, you should see the following message in the DOS Command window:
‘ Exiting the program with SUCCESS’
Look at the jde.log if any error is returned.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 6 of 31
3.3 Configure and Activate RTSOOUT
From an E1 Client, run P90701A (Fast Path). Type “RTSOOUT” in the Event Type field and click Find. If
you find RTSOOUT, skip to step 4 in the following procedure.
If you do not find RTSOOUT, you must add it from this application. Refer to the JD Edwards
EnterpriseOne Application Real-Time Events 9.0 Implementation Guide for more information (see page
163 in http://download.oracle.com/docs/cd/E13781_01/jded/acrobat/e190AAE-B0908.pdf).
1. Add RTSOHDR: Click Add.
Make sure you check the Create Activation Records check box.
2. Add RTSODTL: Click Add.
Make sure you check the Create Activation Records check box.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 7 of 31
3. Add RTSOOUT: Click Add.
Make sure you check the Create Activation Records check box.
Also, make sure you select CONTAINER for Event Aggregate.
4. Go back to Event Definition Workbench (P90701A) and find RTSOOUT.
Select RTSOOUT and ROW::Event Detail.
5. Make sure you see two single events (RTSOHDR and RTSODTL) listed here.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 8 of 31
6. Click Cancel to go back to Event Definition Workbench. Then go to Form::Event Activation.
7. Type “RTSOOUT” in the Event Type field, and activate (AV) the event for your environment by
highlighting your environment and Row::Change Status.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 9 of 31
4 JMSQUEUE Subscriber Configuration in EnterpriseOne
4.1 Create a JMSQUEUE Subscriber
Run P90702A and add a subscriber as follows. The Subscriber field must have a value matching valid E1
User.
Connection Factory JNDI Name: jms/testConnection
Queue Name: jms/TestQueue
Initial Context Factory: weblogic.jndi.WLInitialContextFactory
Provider URL : t3://RTE-ServerName-or-IPAddress:RTEPort
(Note: the RTE Server name or IP address. The RTEPort is the
port of the RTE instance (same port as shown on the RTE
instance in Server Manager)
Take note of the above values as these will be used when creating the Connection Factory in Oracle
WebLogic Server as described later in this document.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 10 of 31
Activate the Subscriber: run P90702A, find the JMSQUEUE Subscriber created in the previous step.
Select the Row\Change Status option. Make sure the Subscriber status is AV (Active).
4.2 Create a Subscription
Run P90702A. Find the JMSQueue Subscriber you created previously. Select the Event Subscriptions
option.
Click Add.
Create a Subscription. The Subscriber Name and Subscriber Description fields can have any value.
Once the Subscription is added, select the Row\Change Status option to activate the Subscription. Make
sure the status is changed from NA to AV.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 11 of 31
4.3 Add an Event (RTSOOUT) to the Subscription
Find the subscription created above. Select the Subscribed Events Row Exit.
Add RTSOOUT as shown below.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 12 of 31
4.4 Add Environment to Subscription
Find the subscription created in the previous section. Select the Subscribed Env Row Exit.
Add Environments as required.
Restart E1 Server at this time. See Appendix A for instructions on testing/validating the E1 settings.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 13 of 31
5 Create a JMS Queue in the Transaction Server Application
5.1 Create the JMS Connection Factory
Log on to the Oracle WebLogic Administrator Console. In Home Page>Services>Messaging>JMS Server,
you should have a JMS Server definition as shown in the example below:
Select the JMS Server to see the JMS Server configuration. The Targets tab should have your RTE-Server
set as the Target.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 14 of 31
In Home Page>Services>Messaging>JMS Modules, you should have a JMS Module definition as shown
in the example below:
Select the JMS Module definition to see the JMS Module configuration. This should show a list of
Queues and Connection Factories as shown in the example below:
RTE Setup for JMSQueue Subscriber. WebLogic
Page 15 of 31
Create a Connection Factory and Queue for your E1 JMS Subscriber.
In Home Page>Services>Messaging>JMS Modules, select the JMS Module and click New.
Select Connection Factory and click Next.
Create a Connection Factory as shown in the example below. Make sure you use the same values as the
ones used when setting up your JMSQUEUE Subscriber inP90702A (see above section 4.a). Click Finish.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 16 of 31
Search for and select the newly created Connection Factory (you might have to scroll through several
pages before you see your Connection Factory).
In Configuration\General, uncheck the Default Targeting Enabled check box as shown below. Click
Save.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 17 of 31
In Configuration\Transactions, check the XA Connection Factory Enabled option. Click Save.
In the Subdeployment tab, select your RTE Subdeployment.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 18 of 31
5.2 Create a JMS Queue
In Home Page>Services>Messaging>JMS Modules, select the JMS Module, click New, and create a
Queue.
Create the queue as shown in the example below. Make sure you use the same values as the ones used
when setting up your JMSQUEUE Subscriber inP90702A (see above section 4.a). Click Next.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 19 of 31
Select the RTE Subdeployement
Click Finish.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 20 of 31
Configure the Oracle BAM Enterprise Message Sources
The Oracle BAM setup involves creating a data object and then defining an enterprise message source
(EMS) in order to dequeue the messages from the JMS defined in the earlier section.
6 Create an Oracle BAM Data Object
Access the Oracle BAM home page using the following URL:
http://<host_name>:<port>/OracleBAM
Provide a valid set of credentials that has access to the complete functionality as shown below:
Click on the Architect button in order to define the data object and the EMS. Oracle BAM Architect is
launched in a new browser window. From the top left hand side dropdown list select Data Objects, the
right-hand side frame then allows creating sub-folders and data objects. The data object is defined first
because it is required within the EMS configuration.
Click on the Create Data Object link.
Provide the Name for the new data object and Location for the new data object, which in this case is
within the DataObject folder, so browse and select that location. Click on the Add a field link and add
the fields required to be tracked for an order entry.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 21 of 31
Once all the fields are added then click Create Data Object. The below diagram depicts how the data
object should look after creation:
7 Define an Oracle BAM Enterprise Message Source Define an Enterprise Message Source (EMS) that dequeues the message from the EMS JMS queue, and
then map the data to the data object.
Using Oracle BAM Architect, select Enterprise Message Source from the top left drop-down list and click
the Create link.
Now provide the below values:
Field Name Description Example
Name The name of the EMS. OrderEntryMessageSource
Initial Context Factory The Weblogic JNDI factory
that would be used for looking
up the initial context.
weblogic.jndi.WLInitialContextFactory
JNDI Service Provider URL The JNDI URL for accessing
the queue. (ensure protocol is
t3 and port is included)
t3://hostname:portnumber
RTE Setup for JMSQueue Subscriber. WebLogic
Page 22 of 31
Topic/Queue Connection
Factory Name
The JNDI name of the
Connection Factory defined
within Weblogic.
jms/testqueueCF
Topic / Queue Name The JNDI name of the Topic
defined within Weblogic
jms/testqueue
JNDI UserName & JNDI
Password
They are optional and if
specified then it should have
Weblogic console access.
Weblogic/welcome1
JMS Message Type Type of message which would
be sent by source (xml text /
map)
TextMessage
Durable Subscriber Name
(Optional)
The subscriber used for
dequeuing the message.
TEMP (It is essential to provide this
since we are using the same for
enqueue, check the package script
above.)
Message Selector (Optional) Used for filtering messages,
only one key-value pair can
be used.
optional
Data Object Name The data object which would
receive data from this EMS
/Test/TestDO (Browse and select the
data object you created in the earlier
section.)
Operation The operation to be
performed on the input record
received
(Insert/Update/Upsert/Delete)
Upsert (As the order would be
progressing through various stages
we selected Upsert [Insert if the
record does not exist, else update].)
Batching Used for batching multiple
transactions together for
performance.
No
Transaction If batching is enabled then
should be set to Yes in order
to commit in one single
transaction.
No
Start When BAM Server
Starts.
Start the EMS once the server
is up & operational.
Yes
JMS UserName & JMS
Password (Optional)
RTE Setup for JMSQueue Subscriber. WebLogic
Page 23 of 31
The following is an example configuration:
XML Formatting is not required, as the XML enqueued by JMS contains the related fields. The Message
Specification is used to define the kind of XML that is received within the queue.
Specify the Message Element Name if it is used in the XML that is created within the package. Since the
Column Value contains the exact tags (case sensitive), select the Element Tag radio button. The date-
time formatting is handled in the package script, so you need not select that check box.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 24 of 31
The Source to Data Object Field mapping is a straight map since the XML enqueued has the same tags
as the data object field names, so from the right-hand side drop-down list select the data object field
and provide the same value in the left-hand side text box as shown in the picture below. Once all the
fields have been specified click Save.
Example picture for mapping (you must check a key field if it is an update/upsert operation).
Test the EMS.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 25 of 31
Appendix A: Testing and Validating the JMSQUEUE
Configuration
If you have followed the steps to activate RTSOOUT as per this document, a Real Time Event will be
created when Adding \ Changing Sales Order record.
Before generating a RTSOOUT, stop your Transaction Server via Server Manager Console. Once the
Transaction Server is stopped, create a Sales Order Record from P4210. In the example below, a new
Sales Order record is created using demo data.
Click on ADD and enter the value below:
Branch/Plant: 10
Sold To: 4242
Quantity Ordered: 1
Item Number 210
OK to save
RTE Setup for JMSQueue Subscriber. WebLogic
Page 26 of 31
On creating\changing a Sales Order Record, a record should be written to a table F90710. If your
Transaction Server is stopped, the F90710 record with remain in the table until the Transaction is
activated. Note the value of the Event Status column (this should be 3 at this point).
RTE Setup for JMSQueue Subscriber. WebLogic
Page 27 of 31
In the Fast Path field Type in “databrowser”::Select “By Table” and enter F90710.
Click Find:
RTE Setup for JMSQueue Subscriber. WebLogic
Page 28 of 31
Now start your Transaction Server using Server Manager Console. After the Transaction Server is
started, the F90710 record should be processed, and if your configuration is correct, the record should
be removed from F90710.
The Event Status field value should go from 3 to 4 and successively from 4 to 5. Once the Event Status
reaches a value of 5, this means that the Real Time Event was “consumed” and the transaction is
deleted from the table.
To see the transaction in the JMS Queue create above, log on to the Oracle WebLogic Server
Administration Console. Go to the Transaction Server JMS Module and select the Queue you created
previously (see section 5.2 above).
RTE Setup for JMSQueue Subscriber. WebLogic
Page 29 of 31
Click on the Monitoring Tab and check mark your Queue Name.
Click on the Show Message button.
You should be able to see the content of the RTE either by selecting the messages ID link or you can
select Export to create an XML file containing the message.
RTE Setup for JMSQueue Subscriber. WebLogic
Page 31 of 31
Appendix B: Initial Information to Provide When Creating a
Service Request
To speed up resolution time for any Service Requests you might have to create with Global Support,
please provide the following information:
Enterprise Server JDE.INI.
The exact Tools Release you are running.
Whether you are running Transaction Server on OAS, WebSphere or Oracle WebLogic Server and
exact release\version your OAS, WebSphere or Oracle WebLogic Server application server.
The content of the config folder within the Transaction Server Agent where the Transaction Server
instance resides.
Logs from Server Manager generated when starting the Transaction Server. To obtain a more
detailed set of logs, create an entry in Server Manager.
Once the additional jdelog.properties definition is added as per above, stop the RTE, clear the RTE
logs, and produce the logs generated after going through the steps outlined in Appendix A.
Description of the results obtained when running the test described in above Appendix A (the status
of the F90710 record after the RTE is started).
Log Component = EVENTPROCESSOR
Log Format=’Verbose’