To deploy to WebLogic

This topic describes how to deploy an application developed using the Interface Mapping Toolkit to WebLogic Application Server.

For details of supported versions of this application server and the appropriate JDK to use, see

  1. If you have not set up a WebLogic server domain, set one up using the WebLogic Domain Configuration Wizard, following the instructions in the wizard. You can start the wizard from the Start menu.
  2. If Server Enterprise Edition (or your COBOL development system) is installed in a location that uses a spacey path, you need to copy the following files to a non-spacey location:
    • mfcobolpure.jar - This is by default in the bin directory of your Server Enterprise Edition installation or your COBOL development system installation.
    • mfconnector.jar - This is by default in the bin\j2ee-version\appserver directory of your Server Enterprise Edition installation or your COBOL development system installation. You need the jar file that corresponds to the WebLogic version that you are using, such as j2ee13\beaweblogic8 or j2ee14\beaweblogic9
  3. Open the startup script for your project in a text editor. This startup script is , and is located in your domain directory of your WebLogic installation.
  4. Go to the end of the file.
  5. Above the line , add the following lines:

    Where:

    • jdk_path is the location of the JDK installation to use for WebLogic.
    • mfcobolpure_path is the path containing mfcobolpure.jar.
    • mfconnector_path is the path containing the required mfconnector.jar. If you have copied this jar into the same directory as mfcobolpure.jar, you don't need to specify this path.
  6. Save the file.
  7. You can now run the startup script.

To start WebLogic

  1. Set up a WebLogic server domain and edit the startup script, if you have not already done so.

To start WebLogic server console:

  1. Start WebLogic.
  2. Open a browser.
  3. Enter the URL, http://localhost:7001/console where 7001 is the default port for the server console.

To deploy a resource adapter to WebLogic

  1. Start WebLogic server and the WebLogic Server Console.
  2. In the left pane of WebLogic Server Console, expand your-domain >Deployments>Connectors
  3. Click Configure a new Connector Component and follow the steps on the page. When you are asked to upload the resource adapter file, upload the required mfcobol*.rar file. For the location of the resource adapters see the section Resource Adapters in the chapter Deploying Interfaces in your Configuration and Administration Guide

    You do not need to create a connection factory or specify the JNDI name of the resource adapter because these are already specified in the deployment descriptor for the connection factory, weblogic-ra.xml

  4. Confirm that the resource adapter has been successfully deployed, by examining the Deployment Activity table on the page on the right. The resource adapter should also be listed in the hierarchy on the left.
Note: The resource adapter must be deployed on a machine where your COBOL development system is installed.

To deploy an EJB to WebLogic

  1. If you don't have a .ear file containing your EJB, package the EJB into an.ear file now. You will have a.ear if you generated a client and EJB together, and it will be in
  2. Start WebLogic server and the WebLogic Server Console.
  3. Deploy the .ear file as follows:
    1. In the left pane expand mydomain >Control> myserver
    2. Click Configure a new Application on the right, and follow the steps on the page.
    3. Confirm that the application has been successfully deployed, by examining the Deployment Activity table on the page on the right. The application should also be listed in the hierarchy on the left

To stop WebLogic

  1. Start the WebLogic server console, if it is not already started.
  2. Navigate to your server in the left-hand pane. This will probably mean expanding: mydomain >Control> myserver
  3. Right-click your server.
  4. Click Start/Stop server and follow the instructions.
Note: TheWebLogic Server Console will not be available until you restart the server.