To Create Deployment Descriptors Manually

You can create deployment descriptors using the administration tool provided by your J2EE application server. Alternatively, you can generate a sample descriptor using the Interface Mapping Toolkit and edit the sample. You need to specify the following information in the deployment descriptor:

• 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 and resource reference name of the Micro Focus resource adapter.

  Among other things, the deployment descriptors specify the following connection information, and you must not change this.

  Note: The JNDI name and the reference name that you enter both depend upon your J2EE version.

  	JNDI name	Reference name
  J2EE 1.3	eis\MFCobol_v1.0	CCIMFCobol_v1.0
  J2EE 1.4	eis\MFCobol_v1.5	CCIMFCobol_v1.5
  Java EE 5	eis\MFCobol_v1.5	CCIMFCobol_v1.5
  Java EE 6	eis\MFCobol_v1.5	CCIMFCobol_v1.5

To create deployment descriptors from dummy ones:

1. Generate a dummy EJB and client using the Interface Mapping Toolkit.
2. Create deployment descriptors, by deploying the dummy EJB using the Deploy tool:

   The descriptors are packaged in the myService.ear file in the folder repos/myService.deploy. The following descriptors are generated:

   • *application*.xm?
   • *ejb-jar*.xm?
   • *web*.xm?
3. Extract the descriptors from the .ear file using jar commands similar to the following for WebSphere:

   jar -xvf JMapServ-WS.ear JMapServ.jar JMapServ.war
   jar -xvf JMapServ-WS.ear META-INF/ibm-application-bnd.xmi
   jar -xvf JMapServ-WS.ear META-INF/ibm-application-ext.xmi
   jar -xvf JMapServ.jar META-INF/ibm-ejb-jar-bnd.xmi
   jar -xvf JMapServ.jar META-INF/ibm-ejb-jar-ext.xmi
   jar -xvf JMapServ.war WEB-INF/ibm-ejb-web-bnd.xmi
   jar -xvf JMapServ.war WEB-INF/ibm-ejb-web-ext.xmi
   

4. Make copies of the descriptors and edit them using an XML editor of your choice, making sure that you retain valid XML. Edit the descriptors as follows:
   • *application*.xm?. Replace the .jar and .war filenames with the names of your files.

     For WebLogic, a weblogic-application.xml file is not required.

   • *ejb-jar*.xm?. Replace the JNDI name with the JNDI name of your EJB. Notice that the JNDI name of the resource adapter is set to eis/MFCobol_*** (where *** is the version), which you must not change.
   • *web*.xm?. Replace the JNDI name with the JNDI name of your EJB.
5. Put each descriptor into a subdirectory below the archive file to which the descriptor belongs, as follows:

   Descriptor	Directory
   *application*.xm?	my-ear-dir\meta-inf
   *ejb-jar*.xm?	my-jar-dir\meta-inf
   *web*.xm?	my-war-dir\web-inf

6. Package your descriptors into your archive files using jar commands similar to:

   jar -uvf myService.ear META-INF/myAppServer-application.xml
   jar -uvf myService.jar META-INF/myAppServer-ejb-jar.xml
   jar -uvf myService.war WEB-INF/myAppServer-web.xml
   

7. Package your updated .jar and .war into your .ear file, using jar command similar to:

   jar -uvf myService.ear myService.jar myService.war 

Note that deployment descriptors are automatically created for the supported application servers that are listed in Servers > Settings on the EJB Generation tab in the Application server field.