$ run UDDI-V0100-A-AXP.EXE
UnZipSFX 5.41 of 16 April
2000, by Info-ZIP (Zip-Bugs@lists.wku.edu).
inflating:
hp-vms-uddi-v0100-a-1.pcsi$compressed
inflating:
hp-vms-uddi-v0100-a-1.pcsi$compressed_esw
$ run UDDI-V0100-A-I64.EXE
UnZipSFX 5.42 of 14
January 2001, by Info-ZIP (Zip-Bugs@lists.wku.edu).
inflating:
HP-VMS-UDDI-V0100-A-1.PCSI$COMPRESSED
inflating:
HP-VMS-UDDI-V0100-A-1.PCSI$COMPRESSED_ESW
Installing the Kit
Before you begin
installing UDDI for OpenVMS, be sure you have met the prerequisites for this
product.
Note: The
BYPASS, GRPNAM, and SYSNAM privileges are required to install UDDI.
To install the UDDI for OpenVMS kit, enter the
following command:
$ PRODUCT INSTALL UDDI
For a
description of the features you can request with the PRODUCT INSTALL command
when starting an installation such as running the IVP, purging files, and
configuring the installation, see the POLYCENTER Software Installation
Utility User's Guide.
As the
installation procedure progresses, the system displays information similar to
the following:
Installation on an OpenVMS Alpha V7.3-2, V8.2 and I64 8.2-1 system:
$ PRODUCT INSTALL UDDI /SOURCE=DISK:[UDDI_KIT] /DEST=DISK:[UDDI]
The following product has been selected:
HP VMS UDDI V1.0-A Layered Product
Do you want to continue? [YES]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
HP VMS UDDI V1.0-A: UDDI V1.0-A for OpenVMS
(C) 2007 Hewlett-Packard Development Company, L.P.
* This product does not have any configuration options.
Execution phase starting ...
The following product will be installed to destination:
HP VMS UDDI V1.0-A DISK:[UDDI.]
Portion done: 0%...20%...30%...40%...50%...60%...70%...80%...90%
*******************************************************************************
Defining system logical UDDI$ROOT...
Please add the logical UDDI$ROOT in SYS$MANAGER:SYLOGICALS.COM
For example: $define/system/trans=concealed/nolog UDDI$ROOT DISK:[UDDI.uddi4j.]
*******************************************************************************
...100%
The following product has been installed:
HP VMS UDDI V1.0-A Layered Product
$
Installation on an OpenVMS Alpha V8.3 and OpenVMS I64 V8.3 system:
$ PRODUCT INSTALL UDDI /SOURCE=DISK:[UDDI_KIT] /DEST=DISK:[UDDI]
Performing product kit validation ...
%PCSI-I-VALPASSED, validation of DISK:[UDDI_KIT]HP-VMS-UDDI-V0100-A-1.PCSI$COMPRESSED;1
succeeded
The following product has been selected:
HP VMS UDDI V1.0-A Layered Product
Do you want to continue? [YES]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
HP VMS UDDI V1.0-A: UDDI V1.0-A for OpenVMS
(C) 2007 Hewlett-Packard Development Company, L.P.
* This product does not have any configuration options.
Execution phase starting ...
The following product will be installed to destination:
HP VMS UDDI V1.0-A DISK:[UDDI.]
Portion done: 0%...20%...30%...40%...50%...60%...70%...80%...90%
*******************************************************************************
Defining system logical UDDI$ROOT...
Please add the logical UDDI$ROOT in SYS$MANAGER:SYLOGICALS.COM
For example: $define/system/trans=concealed/nolog UDDI$ROOT DISK:[UDDI.uddi4j.]
*******************************************************************************
...100%
The following product has been installed:
HP VMS UDDI V1.0-A Layered Product
$
After Installing UDDI
After
the installation is complete, perform the following tasks.
1. Run the validation tests. Enter the following command:
$ @uddi$root:[openvms]UDDI-IVP
The following output is displayed:
Starting UDDI IVP...
Note: This procedure verifies
the correct installation of the UDDI product using a bundled version of the
prerequisite SOAP and Xerces software. The full and supported products should
be installed before using UDDI.
This IVP attempts to connect to a UDDI registry
available on the internet by using the HTTP protocol. This is the same protocol
used by web browsers. Make sure that the computer on which you are running the
tests has access to the internet.
Typically, a company will have employees connect
to a HTTP proxy server on a specific port to gain access to the internet. This
IVP is not able to automatically discover the HTTP proxy server. If you use an
HTTP proxy server, specify the address and port number. For example:
Please enter proxy server name or address [press return if not
used]:
proxy.hp.com
Please enter proxy port number [press return if not used]: 8080
Running sample...
The file UDDI$ROOT:[openvms]UDDI_IVP.LOG
will contain the result of the test
%DCL-S-SPAWNED, process USER_165 spawned
%DCL-S-ATTACHED, terminal now attached
to process USER_165
%DCL-S-RETURNED, control returned to
process _TNA7:
Cleaning up...
2. Validate that the samples have run
successfully. The results of the IVP
should look similar to the
following output:
$ type UDDI$ROOT:[openvms]UDDI_IVP.LOG
*********** Running FindBusinessExample ***********
Saarland University
Sample Business
Sample Business
SAP AG
SAP AG - UDDI Business Registry node
******************************************************
Note: In order to run UDDI client IVP with a user specified UDDI
registry, the
UDDI$ROOT:[build.samples]samples.prop needs to
be edited. The following fields will
change in samples.prop file.
inquiryURL =
http://uddi.sap.com/uddi/api/inquiry/
publishURL =
https://uddi.sap.com/uddi/api/publish/
userid = openvmsuddi
password = openvmsuddi
The changes required are:
inquiryURL=
http://company_inquiry_URL
publishURL= https://company_publish_URL
userid= user name
name password= user password
The URLs have to point to the user specified UDDI registry which is up and
running for executing the UDDI client
IVP. The "userid" and "password" fields should be populated with the
authentication information.
Configuration Tips
The
IVP uses a bundled version of the prerequisite SOAP and Xerces software. The full
and supported products should be installed before using UDDI.
There
are a number of .jar files that must be in your classpath to run the UDDI
software. Refer to the file uddi$root:[openvms]SETUP-UDDI4J.COM for help with establishing
your classpath.
Removing the Kit
To
remove UDDI for OpenVMS, enter the following command:
$ PRODUCT REMOVE UDDI
The
following output is then displayed:
The following product has been selected:
HP VMS UDDI V1.0-A Layered Product
Do you want to continue? [YES]
The following product will be removed from destination:
HP VMS UDDI V1.0-A DISK:[UDDI.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80 ...90%...100%
The following product has been removed:
HP VMS UDDI V1.0-A Layered Product
$
Release Notes
This section
contains notes on the current release of UDDI for OpenVMS.
There
are currently no release notes for the Version 1.0-A
kit.
Support
Customer
Release Version
Support for UDDI
for OpenVMS is provided under
existing OpenVMS service agreements through standard support channels.
See HP Support
for worldwide support center telephone numbers.
If you do not
have a support contract and are not interested in acquiring one, you can
informally exchange information with other users in the OpenVMS newsgroup comp.os.vms.
» Provide comments or technical feedback to the UDDI Client Toolkit for OpenVMS engineering team
