HP OpenVMS Systems

HP is pleased to provide you with a new HP-supported, customer release version of the Web Services Integration Toolkit for OpenVMS.

The Web Services Integration Toolkit provides a set of individual tools to significantly help you develop a JavaBean to expose legacy application logic. These tools are designed to be valuable both individually or in combination. All of the WSIT tools run on HP OpenVMS.

See the "Requirements" section in WSIT Installation Guide and Release Notes for using the Web Services Integration Toolkit on HP OpenVMS, and these additional WSIT pages:

» Documentation
» Download kits
» Software support and feedback
» Software licensing

New features in Web Services Integration Toolkit Version 3.4-1 include:

• Modified bind behavior of WSI$MANAGER process. All the generated WSIT applications binds to a single or multiple LAN address by defining the following logicals:
  ○   $ DEFINE /SYSTEM/EXECUTIVE_MODE WSI$MANAGER_BIND <"IP_ADDRESS">
  ○   $ DEFINE /SYSTEM/EXECUTIVE_MODE WSI$BIND_ <"IP_ADDRESS">
• Implements the XML schema validation for all ‹application-name›.WSI files. The WSI$MANAGER process validates all ‹application-name›.WSI files while deploying the application and reports an error in the WSI$MANAGER.LOG file for every failed validation.
• The process WSI$MANAGER scans the ‹application-name›.WSI file in the WSI$ROOT: [DEPLOY] location to check if the parameter values are correctly loaded in the parameter list of the application.
• Provides support for Java 6.0 for Integrity servers platform.
• Provides support for Pascal nested structure data types.
• Provides enhanced support for log files purging mechanism.

• Automatic stack expansion for single threaded applications. This feature removes the need for the system manager to determine the appropriate maximum stack size for the thread that executes the application code.
• Support for the generation of sample AXIS2 web services (not intended for production environments).
• PCSI kit includes an option to install the WSIT runtime only.
• ANT is no longer bundled with WSIT.
• Generated web services have login and logout methods when authentication is specified using the -l switch on the generator tool (idl2code.jar).
• New application tracing feature is supported (WSI$APPTRACING).
• New log file generation feature allow out of process applications to print to a log file (WSI$LOGFILE).
• Documentation for debugging out-of-process features.
• AXIS2 services now have argument names in WSDL.
• WSI$JNISHR_G defined for debug environments.
• Miscellaneous bug fixes.

Version 2.0 included support for sending and receiving BLOBs, with no maximum size for messages. It also included support for built-in tracing for all wrapped routines and parameters, an extended WSIT IDL to allow fine grained tracing at the level of individual parameters, tighter checking of Boolean values in IDL, and support for POJO clients with zero parameters.

Version 1.2 included support for using an optionally generated JSP (Java Server Page) sample client with authentication and an optionally generated POJO (plain old Java object) sample client running an application out-of-process. For more information, see the section "Generating Sample Clients" in the WSIT Developer's Guide.

The Web Services Integration Toolkit for OpenVMS provides tools that help you to:

• Create an XML IDL file on Integrity servers
  Create an XML interface definition file (IDL) that describes the interface to be exposed. You create an XML IDL file using the tool named OBJ2IDL.EXE for 3GL languages or STDL2IDL.JAR for ACMS. OBJ2IDL.EXE runs on HP OpenVMS Integrity servers only. If you have both HP OpenVMS Integrity servers and AlphaServer systems, run OBJ2IDL.EXE on Integrity servers and copy the resulting XML IDL file to your AlphaServer system.

  OpenVMS Alpha users who do not have an Integrity servers system can run OBJ2IDL.EXE on an OpenVMS Integrity servers system provided by the HP TestDrive Program.

• Validate the XML IDL file
  Verify that the XML IDL file correctly describes the interface being exposed. The validate.jar tool allows you to verify that an XML IDL file conforms to the HP OpenVMS integration.xsd schema. Use this tool to validate all XML IDL files before they are passed to the IDL2CODE.JAR tool.
• Generate components
  Generate one WSIT server interface wrapper and one WSIT JavaBean using the IDL2CODE.JAR tool for the interface exposed. The generated source code must be built on the OpenVMS system that hosts the application.
• Use the generated code
  Call the generated WSIT JavaBean from the technology of your choice, including BEA Web Logic Server, Apache Axis, Java Message Service, Java Remote Method Invocation, Java 2 Platform, Enterprise Edition,(J2EE) or another JavaBean.
• (Optional) Download BWX2IDL.JAR
  Convert your existing BridgeWorks connections to an XML Interface Definition Language (IDL) file that you can use with the Web Services Integration Toolkit. BridgeWorks Version 3.0A installed on Windows is a prerequisite.

Note: Before using the Web Services Integration Toolkit, you must evaluate the original application and design one or more interface classes to expose different features of the business logic.

» Contact the Web Services Integration Toolkit engineering team