Configure E1 Business Service with WebLogic [10.3.5.0] Server & JDeveloper [11.1.1.5]

1.     Certification Matrix for Building BSSV Package

This installation is done by following Oracle Document ID 2167546.2

2.     Installation of JDeveloper

Install JDeveloper 11.1.1.5 [as this is certified to weblogic version 10.3.5.0. Installation is standard there is no change to default setting while installation. After clicking on installable following screen will appear:

Click on Next

Change Middleware Home Directory & click on Next

Click on Next

Click on Next

Click on Next

Click on Next

Click on Next

Click on Next

Click on Next

This will install JDeveloper

3.     Post E1 Client Installation task

• WebDev Configuration

Ensure that WebDev features are working properly by accessing localhost thru FAT Client login. This is necessary as business services will only work if localhost is up and running

• E1 client jde.ini

Client jde.ini should contain section [MTR VALIDATION]. Modify jde.ini with following contents:

[MTR VALIDATION]

BusobjInMB=350

CDiskInMB=200

DeployDiskInMB=5000

NMakeVersion=6.00.8168.0

MDACVersion=2.60.6526.2

LiteRecords=12

JDeveloperVersion=11.1.1

JDeveloperInstallPath=D:\OracleE1\Middleware

MigrateOAStoWls=0

WeblogicHomepath=

BuildForJAXWSWLS=1

BuildForJAXWSWAS=0

WebSphereInstallPath=

• E1 Client ‘misc’ folder

The E1 client ‘misc’ folder must contain the JDBC’s to connect to both E1Local & Server database.

• ‘ini\sbf’ folder

The E1 client ‘dv910\ini\sbf’ contains number of files that needs to be properly configured. These configuration files are created as part of the WebDev client install. A WebDev Client need to be configured as part of the BSSV requirements for a E1 Client. The jdbj.ini contained in this directory should be configured the same way as the jdbj.ini that is used for WebDev. The jdeinterop.ini in this 'ini\sbf' folder is key and must be configured correctly. Folling is changed jdeinterop.ini:

[SERVER]

glossaryTextServer=TNE9XTST:6017

codePage=1252

[JDENET]

serviceNameListen=6667

serviceNameConnect=6017

enterpriseServerTimeout=90000

maxPoolSize=30

maxKernelRanges=1

[JDENET_KERNEL_DEF1]

krnlName=SBFServerJava Kernel

processClassName=oracle.e1.bssvfoundation.impl.jdenet.SBFServerJavaKernel

startMessageRange=16201

endMessageRange=16450

maxNumberOfThread=10

#==========================================================

# Define Cache feature for Connector

#==========================================================

[CACHE]

UserSession=18000000

SpecExpire=300000000

#==========================================================

# Define the features for inbound Business Function call

#==========================================================

[INTEROP]

enterpriseServer=LOCALHOST

port=6081

manual_timeout=30000000

Repository=c:\connector\repository

#==========================================================

# Define the features for outbound events

#==========================================================

[EVENTS]

port=6010

ListenerMaxConnection=100

ListenerMaxQueueEntry=100

outbound_timeout=6000000

#==========================================================

# JNDI information for communication with the J2EE server.

#==========================================================

initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory

jndiProviderURL=corbaloc:iiop:localhost:2809

#==========================================================

#  URL for communicating with the event client service.

#==========================================================

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

#==========================================================

# Security Server. Security server port is in [JDENET]

#==========================================================

[SECURITY]

NumServers=1

SecurityServer=TNE9XTST

#==========================================================

# OCMEnabled--It will enforce Connector to use OCM to find

# enterpriser server or use setting in [Interop]section.

#==========================================================

[OCM]

OCMEnabled=true

[TRANSACTIONS]

ReapInterval=5

MaxAge=10

[WEB DEVELOPMENT]

WebDevelopment=TRUE

#==========================================================

# These settings are for Async HTTP callback from

# third party system to BSSV server.

# HTTPCallbackEndpoint-This setting contains the server,

# port and context root information for the BSSV server.

#==========================================================

[HTTPCallbackSettings]

HTTPCallbackEndpoint=localhost:8888/LOCALDEV

#==========================================================

# These settings are for Async HTTP with SSL

# keystorefile - This setting will be the path to the

#                keystore file.

# keystorepasswd - This setting will be the keystore password.

# keyalias - This setting will be the keystore alias name.

# certificatepasswd -This setting will be the keystore

#                    certicate password.

# truststorefile - This setting will be the path to the

#                  truststore file.

# truststorepasswd - This setting will be the truststore

#                    password.

#==========================================================

[KEYSTORE]

keystorefile=

keystorepasswd=

keyalias=

certificatepasswd=

[TRUST_STORE]

truststorefile=

truststorepasswd=

• JDeveloper installation path in P9603

This application must have the path to a valid Jdeveloper installation. A value in the 'Path Code' field needs to be entered. Tabbing out of the 'Path Code' field will 'activate' the remaining header fields. Enter a valid path for JDeveloper 11g.

1. Accessing application using OMW

Add the JDeveloper install path in OMW:

- In OMW, add a Business Service object (JPR01000 for example) to a project.

- Go to 'Design' for this object.

- Select the 'Design Tools' tab

- Click the 'JDeveloper Install Path' icon to enter the JDeveloper 11g install path.

Click on Invoke JDeveloper

First time to display code in java need to click on Initiate EOne Workspace

This will in turn display java code

4.     Business Services Server Installation and Configuration

1. Creating Business Services Instance

Business Services that are made available to external sources need to be deployed to a Business Services Server. In other words, E1 functions are 'exposed to the outside world' via Business Services that are deployed to a Business Service Server.

1. Create a J2EE container
2. J2EE container can be created using JD Edwards EnterpriseOne Server manager. Login into Server manager and click on WebLogic

Click on Domain

Enter Server Name, Listen Port and Machine and click on create server

This will create J2EE Container. Then select container & click on start

1. Create a BSSV Instance
2. Once container is ready we are ready for creation of BSSV instance.

Select the EnterpriseOne business services Server and click on continue

Enter BSSV server container information and then click on continue

On Next tab click on continue

BSSV instance created successfully and it is in running status

Once the Business Service Server instance is created and configured properly, it can receive packages containing Business Services objects. These packages are built and deployed to the Business Services Server via a E1 Client as described above. A Business Service package will need to be deployed to the BSSV instance before the BSSV instance can be started. Attempting to start a BSSV server instance prior to deploying a Business Service package will produce an error.

• Building a business service package

One E1 client is configured, next logical step to complete BSSV setup is to build and deploy business service server. [Assuming that FAT client is working properly with WebDev feature]

From fast path GH9083 select application Package Assembly – P9601

Click on Add button, Enter Package Name, Description and Path code and then click on Next

Select Update radio button, select check box of Build business server and select Parent package then click on End button

Click on activate & then click on define build from row exit

Click on Next

Click on Next button

Click on end button

Click on Activate and then click on Submit Build

Select Screen and click on Button

Review Package build logs and after successful completion deploy this to business service server.

• Deploying a Business Service Package to the Business Service Server

Select package to deploy. After click on deploy in the next screen click on Next button

Select check box Business Service Server & click on Next

Select check box Enable push installation and enter server manager manage url in management server url

Following screen will populate business service server. Select required business service server & click on Next button

Select Business Service Application Server & click on Deploy button from row exit

5.    Verify Configuration

Oracle document ID 1274889.1 has detailed steps which will ensure that JDeveloper can connect to E1 and execute standard Business Service in the local JDeveloper J2EE container.

This is very important steps as JDeveloper 11.1.1 comes with integrated Weblogic as before deploying any object on server this verification will ensure the correct functionality locally.