Contents

1 Resource Configuration.......................................................................................................................2

1.1 JMS Resource configuration.........................................................................................................2

1.1.1 Queue Connection Factory Configuration............................................................................2

1.1.2 Queue Configuration............................................................................................................5

1.2 Database Resource configuration................................................................................................8

1.2.1 JDBC Providers.....................................................................................................................8

1.2.2 Data Sources......................................................................................................................14

1.2.3 Connection Pool settings....................................................................................................18

1.2.4 Transaction time out..........................................................................................................21

1.2.5 Setting for log4j configuration file......................................................................................22

1.3 Listener configuration................................................................................................................23

2 Deployment.......................................................................................................................................25

2.1 Start and Stop Listener:..............................................................................................................27

2.2 Start and Stop Application:........................................................................................................27

2.3 Configuration.............................................................................................................................27
1 Resource Configuration
1.1 JMS Resource configuration

1.1.1 Queue Connection Factory Configuration

Step 1: Go to Admin Console --> Resources --> JMS --> Connection factories

Step 2: Select the cluster scope - at which resource definition should be visible

Step 3: Click New to create new Connection factory.

Step 3: Select WebSphere MQ messaging provider as the provider and press OK

Step 4: Enter Name, JNDI name for connection factory

Step 5: Provide Queue manager name

Step 6: Provide queue manager host (10.77.16.35) and port (3111) details

Step 7: select Transport Type as CLIENT and press OK

Step 8: Follow steps 1 to 7 above for all the queue managers as listed in
Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls

1.1.2 Queue Configuration

Step 1: Go to Admin Console --> Resources --> JMS --> Queues

Step 2: Select the cluster scope - at which resource definition is visible

Step 3: Click New to create new Queue

Step 4: Select WebSphere MQ messaging provider

Step 5: Enter name and JNDI name of Queue

Step 6: Provide base queue name and base queue manager name created by MQ

Step 7: Select Target Client as JMS;

Step 8: Provide queue manager host and port

Step 9: Follow steps 1 to 7 above for all the queues as listed in

Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls

1.2 Database Resource configuration

1.2.1 JDBC Providers

Step 1: Go to Admin Console --> Resources --> JDBC --> JDBC Providers
Step 2: Select the cluster scope - at which resource definition is visible

Step 3: Click New to create a new JDBC Provider

Step 4: Select Database Type as Oracle

Step 5: Select Provider Type (Oracle JDBC Driver)
Step 6: Select Implementation Type (XA Data source)
Step 7: Enter Name of Provider (Oracle JDBC Driver (XA))
Step 8: Click Next.
Step 8: Provide the ojdbc14.jar path
Step 9: Click Next.
Step 10: Click Finish.
Step 11: Repeat steps 1 to 10 above for all JDBC providers listed in:
Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls

1.2.2 Data Sources

Step 1: Go to Admin Console --> Resources --> JDBC --> Data sources

Step 2: Select the cluster scope - at which resource definition is visible.

Step 3: Click New to create a new Data source.

Step 4: Enter Data source name and JNDI name and click Next
Step 5: Select JDBC Provider (Oracle JDBC Driver XA) and click Next

Step 6: Enter database URL; select Oracle 10g as Data Store; uncheck the Use this data source in CMP
checkbox; and click Next
Step 7: Click Finish
Step 9: Set up the JAAS J2C authentication data for data source just created

Step 11: Click New to create new alias

Step 12: Enter Alias name, Provide database user ID and password
Step 13: Click Finish
Step 14: Select the above authentication alias in Component-managed authentication alias and select
same for XA recovery

Step 15: Repeat steps 1 to 14 above for all the data sources as listed in
Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls

1.2.3 Connection Pool settings

Step 1: Go to Admin Console --> Resources --> JDBC --> Data sources
Step 2: Select the cluster scope - at which resource definition is visible and then click on one data source
to change its connection pool setting

Step 3: On the data source page, click Connection Pool properties

Step 4: Make the necessary changes in Connection pool properties

Please refer to below file for connection pool settings to be configured for each of the data source:
Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls
1.2.4 Transaction time out
Step 1: From Admin console, select Servers > Application Servers > server1

Step 2: Select Container Services > Transaction Service

Step 3: Change the settings as highlighted below

1.2.5 Setting for log4j configuration file
Step 1: From Admin console, select Servers > Application Servers > server1

Step 2: Select Java and Process Management > Process Definition > Java Virtual Machine > Custom
Properties. Click New to create new property
Step 3: Add new property with below details and save.

1.3 Listener configuration

Step 1: From Admin console, select Servers > Application Servers > server1

Step 2: Select Messaging > Message Listener service

Step 3: Select Listener Ports and click New

Step 4: Enter the Name, Connection factory JNDI name, and Destination JNDI name and click OK

Step 5: Repeat steps 1 to 4 above for all the listeners as listed in

Clearcase Path: EAI_MNP_WAS/Docs/WAS Resources.xls
2 Deployment
FILE_PATH = /home/IOMMNWAS - change this with actual path in Production
LOG_FILE_PATH = /logs - change this with actual path in Production
WAS_PROFILE = mnpDefaultDev - change this with actual profile name in Production
Step 1: Create the below folder structure under FILE_PATH
FILE_PATH/lib
FILE_PATH/installables
FILE_PATH/installables/backup
LOG_FILE_PATH/mnp-eai-was
The unix user for WAS should have the ownership of above folders and read /write / execute
permission for the user
Step 2: Copy ojdbc14.jar to FILE_PATH/lib folder.
Step 3: Copy log4j.xml to WAS_PROFILE/properties
Ensure the location of log file in log4j.xml is changed to point to LOG_FILE_PATH/mnp-eai-was
Step 4: Copy AccessAdapterConfig.xml, mnp_eai_messages.xsd, and removeEmptyTags.xsl
files to FILE_PATH/lib.
Step 5: Copy MNPServiceEAR.ear to FILE_PATH/installables folder
Step 6: If redeploying the application take the backup of
MNPServiceEAR.ear , AccessAdapterConfig.xml, and
removeEmptyTags.xslt FILE_PATH/installables/backup folder.
Step 7: Open Admin console, and navigate to Applications/Enterprise
Applications.

Step 8: Click on Install.

Step 9: Select Remote File System and specify the full path of ear file.
Step 10: Click Next until Finish.
Step 11: Ensure application is deployed successfully and then Save changes.
Step 12: Start application we just install.

Step 13: Stop server

FILE_PATH/bin/stopServer.sh server1 - profileName WAS_PROFILE
Step 14: Start server
FILE_PATH/bin/startServer.sh server1 -profileName WAS_PROFILE
2.1 Start and Stop Listener:
If any point of time WAS is not reading the messages from EAI, do check the listener status in
WAS admin console.
Step 1. Open Admin console, and navigate to Servers/Application Servers.
Step 2. Select the serve.
Step 3. Expand Messaging under Communications and click on Message
Listener Service.
Step 4. Select Listener Ports.
Step 5. Check the status of all listeners, and if anyone is not running select
that one and start.

2.2 Start and Stop Application:

If any point of time WAS application needs to stop and start follow
below steps.
Step 1. Open Admin console, and navigate to Applications/Enterprise
Applications.
Step 2. Select the application MNPServiceEAR..
Step 3. Click on stop and start respectively.

2.3 Configuration

FILE_PATH = /home/IOMMNWAS/lib - change this with actual path in Production

a. Steps to change EAI Schema

Step 1. Copy mnp_eai_messages.xsd to FILE_PATH.

Step 2. Copy update_xsd_schema.sql to FILE_PATH.
Step 3. Create table WAS_XSDSCHEMA. Refer Config_Tables.txt file.
Step 4. Run script $ FILE_PATH/replace_xsd.sh to update the XSD schema.

b. Steps to change WAS Configuration

Step 1. Copy AccessAdapterConfig.xml to FILE_PATH.

Step 2. Copy update_config_xml.sql to FILE_PATH.
Step 3. Create table WAS_CONFIG. Refer Config_Tables.txt file.
Step 4. Run script $ FILE_PATH/replace_config.sh to update the XSD schema.

c. Steps to change Transformation template

Step 1. Copy removeEmptyTags.xslt to FILE_PATH.

 Step 2. Copy update_stripEmptyTags_xslt.sql to FILE_PATH.
Step 3. Create table WAS_TRANSFORMATION. Refer Config_Tables.txt file.
Step 4. Run script $ FILE_PATH/replace_xslt.sh to update the XSD schema.

d. Steps to change EAI message Templates

Step 1: Create table MSG_TEMPLATE_TBL. Refer msg_template.txt.

For Ex. Port out Check response
insert into MSG_TEMPLATE_TBL(MSG_ID, TEMPLATE_XML)
values ( '1003', XMLType('<?xml version="1.0" encoding="UTF-8"?>
<mnpmsg:EAIMessage xmlns:mnpmsg="http://mnp.eai.vel/
schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" xsi:schemaLocation="http://mnp.eai.vel/schema
mnp_eai_messages.xsd ">
<EAIHeader>
<MessageID>1003</MessageID>
<ServerDetails>
<ServerName>EAI</ServerName>
<ConnectionDetail>ConnectionDetail</ConnectionDetail>
<AdditionalParam>ConnectionDetail</AdditionalParam>
</ServerDetails>
<RetryCount>0</RetryCount>
</EAIHeader>
<EAIBody>
<PortOutCheckRes>
<PortingCode></PortingCode>
<CircleID></CircleID>
<NumbersToPortRes>
<NumberFrom></NumberFrom>
<NumberAccepted></NumberAccepted>
<NumberReasonCode></NumberReasonCode>
<NumberReasonDesc></NumberReasonDesc>
</NumbersToPortRes>
<MsgCreateTimeStamp>
</MsgCreateTimeStamp>
<Comments></Comments>
 <AccountType></AccountType>
<PortOutCheckStatus></PortOutCheckStatus>
</PortOutCheckRes>
</EAIBody>
</mnpmsg:EAIMessage>'));
Similarly create the other message templates.
Clearcase Path: EAI_MNP_WAS/Config/DML_msg_template_tbl.sql

e. Steps to change the mapping of System and Circle to list of BSCS stored procedures to
be hit for polling trigger

Step 1: Create table SP_TEMPLATE_TABLE. Refer to SP_TEMPLATE_CONFIG.txt

Step 2: Insert data in this table.
For Ex.
INSERT INTO SP_TEMPLATE_TABLE VALUES
('6001','1','KV_BSCS','aid_1001','N');
Similarly insert data for all circles as in below file:
Clearcase Path: EAI_MNP_WAS/Config/DML_sp_template_table.sql