Step 1. Perform Preparatory Steps

1. Check that you have a supported browser installed on your client machine:
   • Netscape Communicator 4.7 or later
   • Internet Explorer 5.0 or later
2. The client machine must have a network connection to the WebLogic Server that is used to connect to the Tuxedo environment.
3. Configure and boot Tuxedo and the simpapp example.
4. Follow the directions in the Tuxedo user documentation to bring up the server-side simpapp application. Ensure the TOUPPER service is available.
5. Set up the Jolt Server. Refer to the Using Oracle Jolt for information about how to configure a Jolt Server.
   • Note the hostname and port number associated with your Jolt Server Listener (JSL).
   • Use the Jolt BulkLoader file to ensure that the TOUPPER service is defined in the Metadata Repository.
   • Use the Jolt BulkLoader file to ensure that the TOUPPER service is defined in the Metadata Repository.

   The simpapp example directory has a simpapp.rep file that contains the TOUPPER service definition. Your system administrator should use the BulkLoader to add this service definition to the existing Metadata Repository on the Tuxedo server. Refer to Using Oracle Jolt for details.

   On the Tuxedo server, the following code example uses the Jolt BulkLoader to add the TOUPPER service definition:

   java -DTM_ALLOW_NOTLS=Y bea.jolt.admin.jbld //host:port simpapp.rep

   where host and port are the hostname and port number of your Jolt Server Listener (JSL), and the simpapp.rep is the BulkLoader file provided by Oracle Jolt, in the current directory. If the file simpapp.rsp is not located in current directory, please specify full path of the file:

   The Java property -DTM_ALLOW_NOTLS=Y is to specify non-SSL connection to JSL.
6. Confirm that you have properly set up your CLASSPATH during installation. The WebLogic Server classes library contains the three .jar files that you will need to run this example:
   • jolt.jar
   • joltjse.jar
   • joltwls.jar