Configure for Virtual Network Computing

After you have set up a VNC server on the iSeries system, follow these instructions for each instance to configure it for use with WebSphere Portal.

While VNC can be installed through other means, the following instructions apply only to the version of VNC provided with iSeries Tools for Developers PRPQ.

Before starting these steps, have a VNC server running on the iSeries system and a WAS instance created for use with WebSphere Portal. If you used the IBM Web Administration for iSeries tool to configure WebSphere Portal, a WAS instance was created for you. You can also create one by following the steps in the Create an extended WAS topic.

 

Configure a WAS instance for VNC

Follow these instructions to configure a WAS instance for VNC:

  1. If the WAS instance is not already started, start it by following these instructions:

    1. Start the Qshell Interpreter by entering the following on an OS/400 command line: 

      STRQSH

    2. Change to the directory /qibm/proddata/webas5/pme/bin

    3. Enter the following command: 

      startServer -instance <instance> <app_server>

      where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

  2. Start the WAS administrative console by entering the following in the location bar of a Web browser: 

    http://<system_name.com>:<admin_port>/admin

    where system_name.com is the name of the iSeries server, and admin_port is the port assigned to the administrative console.

  3. In the left frame, open the Servers section by clicking the plus (+) sign.

  4. Click Application Servers.

  5. In the right frame, select the application server that the application is deployed to.

  6. On the Configuration tab, under Additional Properties, click Process Definition.

  7. Under Additional Properties, click Environment Entries.

  8. Click New.

  9. Enter DISPLAY in the Name column and <host_name>:<n> in the Value column, where host_name is the TCP/IP host name of the system, and n is the VNC server number (for example ':1').

  10. Click Apply. Click OK.

  11. Under Additional Properties, click Environment Entries.

  12. Click New.

  13. Enter XAUTHORITY in the Name column and /home/QEJBSVR/.Xauthority in the Value column.

  14. Click Apply. Click OK.

  15. Under Additional Properties, click Java Virtual Machine.

  16. Under Classpath, enter /QIBM/ProdData/Java400/jdk13/jdkawt.jar.

  17. At the bottom of the page, click Apply.

  18. At the bottom of the page, click Custom Properties.

  19. Click New.

  20. Enter os400.class.path.rawt in the Name column and 2 in the Value column.

  21. Click Apply. Click OK.

  22. At the top of the screen, under Message(s), click Save.

  23. Click Save again when prompted to confirm the changes.

  24. Restart the WAS by following these instructions:

    1. Start the Qshell Interpreter by entering the following on an OS/400 command line: 

      STRQSH

    2. Change to the directory /qibm/proddata/webas5/pme/bin

    3. Enter the following commands: 

      stopServer -instance <instance> <app_server>
      
startServer -instance <instance> <app_server>

      where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

See also