Installation Guide for Oracle Self-Service E-Billing > Configuring IBM WebSphere > Process of Deploying Oracle Self-Service E-Billing Applications on IBM WebSphere >

Deploying the Command Center Application on IBM WebSphere

Follow these steps to deploy the Command Center application EAR file on IBM WebSphere.

This task is a step in Process of Deploying Oracle Self-Service E-Billing Applications on IBM WebSphere.

To deploy the Command Center application on IBM WebSphere

1. Select Applications, Enterprise Applications, and Install.
2. Select Local file system if your EAR file is on the local computer or select Remote file system, and browse to the full path of the EAR file: EDX_HOME/ebilling603/J2EEApps/commandcenter/websphere. In the path, EDX_HOME is the location where Oracle Self-Service E-Billing is installed.
3. Click Next, and give an appropriate name to the Command Center application, leaving the settings as they are.
4. Click Next, and select all the modules to map to servers and click Next.
5. Leave the EJB Logger module options as they are.
6. To bind the listeners for the message-driven enterprise bean to the Activation Specification for the Logger, use the default values for the Target Resource JNDI and Destination JNDI names. For the Activation Spec authentication alias, add the prefix CC_node/ to the default value Logger_ASAuthAlias to create CC_node/Logger_ASAuthAlias.
7. To bind the listeners for the message-driven enterprise bean to the Activation Specification for Events, specify the following values.

   Field	Value
   Target Resource JNDI Name	jms/MessageDispatcher
   Destination JNDI name	edx.queue.outbound
   Activation Spec authentication alias	CC_node/MessageDispatcher_ASAuthAlias

8. Ignore the application resource warnings, and click Continue.
9. Map the empty EJBs whose target Resource JNDI name is blank, and give the target resource JNDI names as shown.

   Resource Reference	Class	Target Resource JNDI Name
   ejb/AppMgr	com.edocs.services.application.IAppMgr	edx/ejb/AppMgr
   ejb/VersionManager	com.edocs.services.versioning.IVersionManager	edx/ejb/VersionManager

10. In the Specify authentication method section, check None. Specify the Target Resource JNDI Name as edx.databasePool for the JNDI name, then click Next.
11. On the Map virtual hosts for Web modules screen, select all application names, and click Next.
12. View the summary, then click Finish. Click Save to save directly to the master configuration.