Version 6.3.8 for OpenVMS
 —  Natural Web I/O Interface  —

Installing the Natural Web I/O Interface Client on Sun Java System Application Server

If you want to use the Natural Web I/O Interface client with Sun Java System Application Server, you must proceed as described in this document. The following topics are covered:


Installation Steps

The Natural Web I/O Interface client is installed using the Adminstration Console of Sun Java System Application Server.

The following is assumed:

The following topics are covered below:

First-time Installation

Start of instruction setTo install the Natural Web I/O Interface client

  1. Download the Natural Web I/O Interface client for Sun Java System Application Server from Empower (https://empower.softwareag.com/) and unzip the contents to a directory of your choice on your hard disk.

    Or:
    Natural for UNIX, Natural for OpenVMS and Natural for Windows: Copy the complete contents of the nwo/<platform>/j2ee/v<nnnn>/sun-apps directory from the installation medium to a directory of your choice on your hard disk.

  2. On UNIX platforms: Dearchive the TAR file using the following command:

    tar -xvf nwonnnn.tar
  3. Edit the file <sunas>/domains/domain1/config/server.policy and add the following setting in order to enable the Java Logging API:

    grant {
    	permission java.util.logging.LoggingPermission "control";
    };
    

    Important:
    If you do not add this setting, the resource adapter will not start and the Natural Web I/O Interface client will therefore be inoperative.

  4. Make sure that the application server is running.

  5. Open your web browser and enter the following URL:

    http://<host>:<adminport>

    This opens the Adminstration Console.

  6. Deploy the resource adapter naturalunicode.rar:

    1. Open the tree node Applications > Connector Modules.

    2. Choose Deploy.

    3. Select naturalunicode.rar as the package file to be uploaded to the application server.

    4. Choose Next. "naturalunicode" is automatically included as the application name.

    5. Choose Finish.

  7. Define the JNDI name for the resource adapter:

    1. Open the tree node Resources > Connectors > Connector Connection Pools.

    2. Choose New.

    3. Enter "NatPool" (the name is arbitrary) as the name.

    4. Select naturalunicode as the resource adapter.

    5. Each connection to a Natural host results in a new connection being made. Since each user requires a unique host session, connection pooling cannot be used. Therefore, you should make sure there are enough sessions for your users. The default maximum number is "32".

    6. Choose Next.

    7. Choose Next.

    8. Choose Finish.

    9. Open the tree node Resources > Connectors > Connector Resources.

    10. Choose New.

    11. Enter "eis/NaturalUnicodeRA" as the JNDI name.

    12. Select NatPool (or whatever name you specified previously) as the pool name.

    13. Choose OK.

  8. Deploy the enterprise application natuniapp.ear:

    1. Open the tree node Applications > Enterprise Applications.

    2. Choose Deploy.

    3. Select natuniapp.ear as the file to upload.

    4. Choose Next.

    5. Choose OK. The deployment may take several minutes.

  9. Restart the application server.

Update Installation

Start of instruction setTo update the Natural Web I/O Interface client

  1. Make a backup copy of your sessions.xml file which is located in ../AppServer/domains/domain1/applications/j2ee-apps/natuniapp/natuniweb_war/WEB-INF. If you have changed any other files (such as style sheets), also make backup copies of these files.

  2. Download the Natural Web I/O Interface client for Sun Java System Application Server from Empower (https://empower.softwareag.com/) and unzip the contents to a directory of your choice on your hard disk.

    Or:
    Natural for UNIX, Natural for OpenVMS and Natural for Windows: Copy the complete contents of the nwo/<platform>/j2ee/v<nnnn>/sun-apps directory from the installation medium to a directory of your choice on your hard disk.

  3. On UNIX platforms: Dearchive the TAR file using the following command:

    tar -xvf nwonnnn.tar
  4. Edit the file <sunas>/domains/domain1/config/server.policy and make sure that the following setting has been defined:

    grant {
    	permission java.util.logging.LoggingPermission "control";
    };
    

    Important:
    This setting is required as of Natural Web I/O Interface Version 1.3.2. If this setting is missing, the resource adapter will not start and the Natural Web I/O Interface client will therefore be inoperative.

  5. Make sure that the application server is running.

  6. Open your web browser and enter the following URL:

    http://<host>:<adminport>

    This opens the Adminstration Console.

  7. Undeploy the resource adapter naturalunicode.rar:

    1. Open the tree node Resources > Connectors > Connector Connection Pools.

    2. Mark the check box Natpool (or the check box for whatever name you specified previously).

    3. Choose Delete.

    4. Open the tree node Applications > Connector Modules.

    5. Mark the check box naturalunicode.

    6. Choose Undeploy.

  8. Undeploy the enterprise application natuniapp.ear:

    1. Open the tree node Applications > Enterprise Applications.

    2. Mark the check box natuniapp.

    3. Choose Undeploy.

  9. Deploy the resource adapter naturalunicode.rar as in a first-time installation.

  10. Define the JNDI name for the resource adapter as in a first-time installation.

  11. Deploy the enterprise application natuniapp.ear as in a first-time installation.

  12. Copy your backup files back to the required places.

  13. Restart the application server.

Top of page

Installation Verification

It is assumed that http://<host>:<port> is the URL of your application server.

Start of instruction setTo verify the installation

  1. Enter the following URL in your web browser:

    http://<host>:<port>/natuniweb/natural.jsp

    For example:

    http://myhost:8080/natuniweb/natural.jsp

    The Natural Web I/O Interface client is now started in your browser. The entries which appear in the resulting logon page depend on the settings in your configuration file. For further information, see Configuring the Client.

Top of page