BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

   http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary

 

   Tuxedo Documentation   |   Using BEA Jolt   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents   |   Index

 

Getting Started Checklist

Review this checklist before starting the TRANSFER Request Walkthrough.

Note: This checklist applies to Microsoft Active Server Pages only. It also assumes that you have already installed BEA Tuxedo and the Jolt Server on a host machine, as well as the BEA Jolt client on a machine where Microsoft IIS is installed.

Tuxedo Host Running Jolt Server

  1. Ensure that you have a supported browser installed on your client machine. The client machine must have a network connection to the Web server that is used to connect to the BEA Tuxedo environment.

  2. Configure and boot BEA Tuxedo and the BEA Tuxedo BankApp example.

    1. Make sure the TRANSFER service is available.

    2. Refer to the BEA Tuxedo user documentation for information about completing this task.

  3. Configure the BEA Tuxedo application to start Jolt. (Refer to Installing the BEA Tuxedo System for information about how to configure a Jolt server.)

    1. Note the hostname and port number associated with your Jolt Server Listener (JSL).

    2. Ensure that the TRANSFER service is defined in the Jolt Repository.

    3. Test the TRANSFER service using the Jolt Repository Editor to make sure it is accessible. Then, export the TRANSFER service using the Repository Editor to make the TRANFER service available to all Jolt clients.

Machine Running Jolt Client and Microsoft IIS

  1. If the Microsoft Java Component Framework from the Microsoft IIS SDK 4.0 is not installed, install it now. (This SDK is not installed if you chose the Typical installation of the Microsoft NT Service Pack 5.0.)

    1. Create a new directory named aspcomp in your java\Trustlib directory. This is most typically found in the %windir%\java\TrustLib directory.

      Note: Because the framework files are created in a package called aspcomp, the Java Virtual Machine (JVM) expects to find them there.

    2. Copy the Microsoft Java Component Framework class files to the java\TrustLib\aspcomp directory. (Copy only the *.class files.)

  2. Copy the jolt.jar file into the %windir%\java\Trustlib directory. Then use the jar command to unpack jolt.jar and create the Jolt class files in the java\TrustLib directory.

    Note: Since the Jolt classes are created in packages starting with BEA, the JVM expects to find them in the java\Trustlib\bea\... subdirectories.

  3. Copy the joltasp.jar file into the Windows 2000 server's java\Trustlib directory. Then use the jar command to unpack joltasp.jar and create the Jolt Pool Application Services class files in the java\Trustlib directory.

    Note: Since the Jolt Pool Application Services classes are created in packages starting with BEA, the JVM expects to find them in the java\Trustlib\bea\... subdirectories.

  4. Run the wasreg.cmd command file to register the BEA Jolt Pool Application Services classes as BEAJOLTPOOL ActiveX components. This step enables the BEAJOLTPOOL components to be accessible from the Microsoft ASP scripts.

    Note: The BEA Jolt installation includes a copy of the wasreg.cmd file, which registers your Java classes as COM objects on the server machine using the JavaReg utility (available with Visual J++ or the Microsoft SDK for Java). It also includes a copy of the wasunreg.cmd file, which unregisters your Java classes as ActiveX components. Registration can also be done manually or by a setup program, since javareg/register is only creating registry entries.

  5. After registering the ASP classes as ActiveX components, you are ready to test the sample application delivered with the Jolt ASP Connectivity for BEA Tuxedo software:

    1. Copy the %tuxdir%\udataobj\jolt\examples\asp\bankapp directory to the default Microsoft IIS directory.

    2. Start the application by entering the following URL from your browser:
      http://<web-server:port>/bankapp/tellerForm.asp

      Note: The port number is optional, depending on how your Web server is configured. In most cases, the :port is not required in the URL.

    3. Edit the bankapp.properties file to fit your environment.

      Note: Refer to the code samples shown in TRANSFER Request Walkthrough, for additional information.

  6. The following table, "Sample Bankapp Source Files," lists the files in the sample application. These files are a valuable reference for the walkthrough and are located in <extract_directory>/teller.

    Sample Bankapp Source Files

    File Name

    Description

    tellerForm.asp

    Initializes the Jolt Session Pool Manager and displays available BankApp services.

    transferForm.htm

    Presents an HTML form for user input.

    tlr.asp

    Processes the HTML form and returns results as an HTML page.

    web_admin.inc

    VBScript functions for initializing the Jolt Session Pool Manager.

    web_start.inc

    VBScript functions for initializing the Jolt Session Pool Manager.

    web_templates.inc

    VBScript functions for caching HTML templates.

    templates/transfer.temp

    HTML templates used for returning results.

     

 

back to top previous page next page

 

Copyright © 2001 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.