To deploy to Oracle Application Server

Introduction

To run an application on Oracle Application Server you need to:

• Have Oracle Application Server installed.
• Deploy one of the Micro Focus resource adapters, which are supplied, together with default deployment descriptors.
• Deploy the application .ear file. You can generate this automatically when you generate a client for your EJB using the Interface Mapping Toolkit. Default deployment descriptors are also generated and packaged in the .ear file when you generate a client.

You can deploy using the Web-based administration console, called Enterprise Manager, or you can deploy using the command line tool dcmctl.

When you deploy an application .ear file or a resource adapter, you deploy it to an instance of Oracle Application Server Containers for J2EE (OC4J). An OC4J instance called Home is created by default when you install Oracle Application Server.

Installing and Starting Oracle Application Server

You can install Oracle Application Server by downloading it from http://www.oracle.com

To open Oracle Application Server, enter the URL http://localhost:7777 in your browser.

$ORACLE_HOME/bin/emctl start iasconsole

The default ports are:

Resource Adapters

The following resource adapters are supplied for Oracle Application Server:

• mfcobol-notx-ora.rar - does not support transactions
• mfcobol-localtx-ora.rar - supports local transactions
• mfcobol-xa-ora.rar - supports XA transactions

For the location and details of the resource adapters, see the section Resource Adapters in the chapter Deploying Interfaces in your Configuration and Administration Guide

Deployment Descriptors

Default deployment descriptors for your application are automatically generated when you generate a client for the EJB. They are packaged in the archive files (.ear .jar .war) and are named orion-*.xml

A default deployment descriptor for the resource adaptors is included in the supplied .rar archive files. This deployment descriptor,oc4j-ra.xml contains configurations for deploying resource adapters to OC4J. It includes:

• EIS connection information that matches the information specified in the deployment descriptor of the resource adapter
• JNDI name to be used
• Connection pooling parameters
• Resource principal mapping mechanism and configurations

You might need to modify oc4j-ra.xml. For example, you might need to change the server host from localhost to the name of the machine on which your enterprise server is running. To modify this file, extract it from the required .rar file, and reinstate it there after editing.

Deploying Using the Command Line

You can use the command line tool dcmctl to deploy a resource adapter or your application .ear file, and for other administration tasks. For full details of all the commands and their syntax, see the Oracle documentation. The following commands are a few simple examples.

opmnctl startall
opmnctl stopall

To deploy the resource adapter mfcobol-notx-ora.rar, use a command such as:

dcmctl deployApplication -f $COBDIR/lib/mfcobol-notx-ora.rar -a mfcobol-notx-ora

To deploy the application myapplication.ear, use a command such as:

dcmctl deployApplication -f myproject/repos/myapplication.ear -a myapplication

Setting Up Logging

To switch on logging, use Enterprise Manager. Go to the Command Line Options and specify the following options:

Further Information

For further information, see the Release Notes for your Oracle Application Server installation and the OC4J Connectors FAQ on the Oracle Web site.