Deployment Descriptors

Deployment descriptors are xml files containing deployment information, such as the settings you specify in the Interface Mapping Toolkit. J2EE application servers require deployment descriptors for the archive files (.jar, .war and .ear) to be deployed. At run time, the J2EE application server reads the descriptors and acts accordingly. Deployment descriptors are not required for the generated Java beans.

When you generate an EJB or client, the following generic deployment descriptors are created and packaged into the relevant archive files:

• application.xml, which defines and is packaged in the enterprise archive file (.ear)
• ejb-jar.xml, which defines and is packaged in the EJB Java archive file (.jar) to be deployed.
• web.xml, which defines and is packaged in the Web archive file (.war) to be deployed.

Some J2EE application servers require additional deployment descriptors in the archive files. These descriptors are generated automatically for the supported application servers. See the for details of the supported J2EE application servers.

If your application server requires additional deployment descriptors and these are not generated, you need to create them manually and add them to the archive files. In many cases, you can do this using the administration console for your application server. You need to specify the following information in the relevant deployment descriptors:

• The JNDI name of the EJB. This can be any name you like, but it must match the JNDI name that other components of your application use when they refer your EJB.
• The JNDI name for the resource adapter. The resource adapter's reference name (also called its coded name) is CCIMFCobol_v1.0, which is the name of the connection factory. The JNDI name that you specify is eis\MFCobol_v1.0. You must use the names stated here.