
Readme for HP Operations Manager HTTPS Agent and SPI Version T8.10-1 
for OpenVMS Integrity servers


This beta kit is applicable only for Operations Manager for 
Windows (OMW) 8.x.


The readme contains the following sections:

   1.1  Verifying the prerequisites on an OpenVMS System
   1.2  Configuring the Operations Manager Server on Windows
   1.3  Installing the HP Operations Manager HTTPS
        Agent and SPI Software on OpenVMS System
   1.4  Installing the HP Operations Manager HTTPS 
        Agent and SPI Software on OpenVMS Cluster  
   1.5  Using the HP Operations Manager HTTPS Agent 
        and SPI Software
   1.6  Uninstalling the HP Operations Manager HTTPS
        Agent and SPI Software on OpenVMS System
   1.7  Supported and Unsupported Features 
   1.8  Known Issues

 
To manage an OpenVMS system from an Operations Manager
Server, complete the following tasks on both the Operations 
Manager Server system and on the OpenVMS system before you 
install the software:

  - Verifying the prerequisites on an OpenVMS System
  - Configuring the Operations Manager Server


1.1  Verifying the prerequisites on an OpenVMS System
 
To verify the prerequisites on an OpenVMS system, follow
these steps:

HP Operations Manager HTTPS Agent and Smart Plug-In (SPI) 
software is now available on OpenVMS Integrity servers 
Version 8.2-1 or later. Ensure the following OpenVMS patches 
have been applied. 

For OpenVMS Integrity servers:
------------------------------

  - OpenVMS Integrity servers Version 8.2-1 

	- VMS821I_UPDATE V5.0 or later
	- HP I64VMS VMS821I_ICXXL V2.0 or later
	
  - OpenVMS Integrity servers Version 8.3

	- VMS83I_UPDATE V1.0 or later 
	- VMS83I_SYS V1.0 or later 
        - HP I64VMS VMS83I_ICXXL V2.0 or later 

  - OpenVMS Integrity servers Version 8.3-1H1

	- HP I64VMS VMS831H1I_ICXXL V2.0 or later

   The patches are available at the HP ITRC web address:
   http://www2.itrc.hp.com/service/patch/mainPage.do

  - SSL for OpenVMS

    You must have SSL Version 1.2 or later installed 
    and running on your OpenVMS system. The SSL kits are 
    available at the following web address:
    
    http://h71000.www7.hp.com/openvms/products/ssl/ssl.html
      
  - You need to install the HP Operations Manager HTTPS 
    Agent and SPI software on ODS-5 disk.

 
1.2  Configuring the Operations Manager Server on Windows

For Operations Manager Server on Windows, the beta kit
for HTTPS agents are included as a Windows zip file.

To configure on Operations Manager Server on Windows, follow 
these steps:

1. Log in to your Windows Management Server.

2. Extract the OVO8_BETA1_W_AGENT.ZIP files into a temporary 
   folder as shown:
   
   C:\OMW_BETA_TEMP

3. From the C:\OMW_BETA_TEMP folder, run the platform_update
   batch file, which notifies the server about the new OpenVMS platform.
   This new OpenVMS platform is now available on the management server.

4. Upload the new policies for the OpenVMS agent and for the OpenVMS SPI 
   by entering the following command:

   #C:\OMW_BETA_TEMP\Upload_Policies.bat
		   
   NOTE: These commands replace the policies supplied with earlier versions 
         of the OpenView Agent for OpenVMS. If you have customized any of the  
         policies, save them with a different policy name before executing 
         the above commands. 


1.3  Installing the HP Operations Manager HTTPS Agent and SPI 
     Software on OpenVMS System

On ODS-5 disk, install the HP Operations Manager HTTPS Agent and SPI 
software by performing the following steps:

1. Log in to the SYSTEM account on the OpenVMS managed
   node.

2. Create a temporary directory on an ODS-5 disk to
   copy the installation files.
   
   For example,  

   $ CREATE/DIRECTORY DISK$:[TEMP]

3. FTP the OVO8-T0810-I64.EXE installation file from Operations 
   Manager Server on Windows to the temporary directory. 
   
   The file OVO8-T0810-I64.EXE is available at directory 
   %OvShareDir%\packages\HTTPS\OpenVMS on the OMW server.

   The default %OvShareDir% directory is 
   C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared\

   On the Windows server:
   ----------------------
   <DOS prompt at %OvShareDir%packages\HTTPS\OpenVMS>ftp <your OpenVMS node>
   SYSTEM
   <password>
   ftp> cd DISK$:[TEMP]
   ftp> bin
   ftp> put OVO8-T0810-I64.EXE
   ftp> bye

4. To extract the installation files, run OVO8-T0810-I64.EXE
   by entering the following command:

   $ RUN OVO8-T0810-I64.EXE

     HP-I64VMS-OVBBC-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVBBC-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVXPL-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVXPL-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVCONF-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVCONF-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVCTRL-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVCTRL-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVSECCO-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVSECCO-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVSECCC-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVSECCC-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVEAAGT-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVEAAGT-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-OVDEPL-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-OVDEPL-T0810-1-1.PCSI$COMPRESSED_ESW
     HP-I64VMS-VMSSPI-T0810-1-1.PCSI$COMPRESSED
     HP-I64VMS-VMSSPI-T0810-1-1.PCSI$COMPRESSED_ESW
     OPC_INST.COM
     OPCACTIVATE.COM
     OPC_UNINST.COM
     OPC_CLU_NODE_CONF.COM
     README_OPENVMS_AGENT_OMW.TXT 
     
5. Start the installation by entering the following command:

   $ @opc_inst -srv <MgmtSrvName> -cert_srv <CertSrvName>

6. To install the certificates manually, follow these
   steps:

 	a) Set the installation type to MANUAL by entering the
	   following command:

	   $ ovconfchg -ns sec.cm.client  -set
           "CERTIFICATE_DEPLOYMENT_TYPE" "MANUAL"

	b) To check whether the settings are correct, run
	   ovconfget.

           For example,

	   [sec.cm.client]
           CERTIFICATE_DEPLOYMENT_TYPE=MANUAL

           [sec.core]
           CORE_ID=fc200278-8f86-751f-0e73-cbd79be7b384
 
           [sec.core.auth]
       	   MANAGER=my.mgmt.srvr.com                                            
           MANAGER_ID=970qedsd-4212-7564-1234-qwn6kuu2d07

	c) Log in to the Windows Management Server (OMW) and add 
           your managed node to the Operations Manager console.        

	d) Create a signed certificate and the corresponding
           private key for a specific managed node manually using the
           ovowcsacm command line tool. You must provide a password to
           encrypt the created data when requested.

           #ovowcsacm -issue -name <managed_node_name> [-file <file_name>] 
           -coreid <OvCoreId_of_managed_node>] [-pass <password>]

           For example, 

           #ovowcsacm -issue -name "alex.abc.xyz.com"  -file "C:\mycertfile"
           -coreid  "fc200278-8f86-751f-0e73-cbd79be7b384"

           The coreid of the OpenVMS managed node may be copied from 
           the output of command $ovconfget when executed on the 
           OpenVMS managed node.

 	e) Copy the file containing the signed certificate, its corresponding 
           private key, and the root certificate onto a floppy disk or other 
           portable media. Also, this file can be transferred securely over            
           the wire.

        f) Log on to the OpenVMS managed node. If the agents are running 
           stop the agents locally by entering the following command:
  
   	   $ OVC -stop

	g) On the OpenVMS managed node, copy the certificate file. Then, 
           import the certificate, the trusted root certificate, and 
           the private key using the ovcert command line tool. Specify the 
           same password used in step d when requested.

           $ ovcert -importcert -file <certificate-file-name>

	   To import the certificate, enter the following command:

           $ ovcert -importcert -file <certificate-file-name>

	h) Run ovconfchg by entering the following command:

	   $ OVCONFCHG

 	i) After installation, delete the certificate file from the 
           managed node and the data on the portable medium or 
           store it in a secured place. 

        j) Start the agent locally by entering the following command:
       
           $ OVC -start


1.4  Installing the HP Operations Manager HTTPS Agent and SPI Software 
     on OpenVMS Cluster  


     Installing on Cluster Nodes with their Own System Disk:
     -------------------------------------------------------
    
     If you are installing HP Operations Manager HTTPS Agent and SPI 
     software on nodes in a cluster that does not have a common system disk, 
     you must install HP Operations Manager HTTPS Agent and SPI 
     software on each node separately and configure each node separately. 
     For more information on installing, see Section 1.3, Installing the 
     HP Operations Manager HTTPS Agent and SPI Software on OpenVMS System.

  
     Installing on Cluster Nodes with Common System Disk:
     ----------------------------------------------------

     To install the HP Operations Manager HTTPS Agent and SPI software 
     on cluster nodes with common system disk, follow these steps:

     1.	Install the HP Operations Manager HTTPS Agent and SPI software on 
        a shared disk, on any one of the cluster nodes as described in 
        Section 1.3, Installing the HP Operations Manager HTTPS Agent and 
        SPI Software on OpenVMS System.

     2.	Uninstall OpenVMS DCE agents and OSSPI on other cluster nodes if 
        you have installed the software previously by entering the 
        following commands:

        $ @SYS$STARTUP:VMSSPI$SHUTDOWN
        $ @SYS$STARTUP:OVO8$SHUTDOWN
        $ PRODUCT REMOVE OVOAGENTS
        $ PRODUCT REMOVE VMSSPI

     3.	Run the OPC_CLU_NODE_CONF.COM on each of the other cluster nodes 
        in the cluster. 
      
        $ @sys$manager:opc_clu_node_conf -srv <MgmtSrvName> -cert_srv <CertSrvName>         
          
     4.	To install the certificates manually on each of these cluster 
        nodes, follow step 6 as described in section 1.3, Installing the 
        HP Operations Manager HTTPS Agent and SPI Software on OpenVMS System.


1.5  Using the HP Operations Manager HTTPS Agent and SPI software

1. Start the HP Operations Manager HTTPS Agent by entering the
   following commands:

   $ @SYS$STARTUP:OVO8$STARTUP

2. Use the Management Server to distribute the policies that you want to use 
   on your OpenVMS node. To distribute the policies, follow these steps:
      
	a) Deploy the policies that are provided with this beta kit. 
    
	b) Use the Management Server to deploy the policies
           that you want to use on your OpenVMS node. The policies
           that are provided with the OpenVMS HTTPS OVO Agents and
           SPI are available in the following policy groups:

	   \Policy management\Policy groups\OpenVMS_policies
           \Policy management\Policy groups\OpenVMS_SPI_policies

3. Start the OSSPI by entering the following command:
  
   $ @SYS$STARTUP:VMSSPI$STARTUP

   To customize the SPI configuration files, refer to the
   manual "HP OpenView Smart Plug-In (SPI) for OpenVMS User's
   Guide." You can locate this manual at OVO$POSIX_ROOT:
   [000000]VMSSPI_USER_GUIDE.PDF

4. Stop the Operations Manager Agent and OSSPI by entering the
   following commands:

   $ @SYS$STARTUP:VMSSPI$SHUTDOWN
   $ @SYS$STARTUP:OVO8$SHUTDOWN

 
1.6  Uninstalling the HP Operations Manager HTTPS Agent and SPI 
     Software on OpenVMS System

     To uninstall HP Operations Manager HTTPS Agent and SPI software 
     on nodes in a cluster that do not have a common system disk, 
     enter the following command on each node separately:

     $ @SYS$MANAGER:OPC_UNINST.COM 

     Note: Run @SYS$MANAGER:OPC_UNINST.COM on any one of the cluster 
     nodes sharing a common system disk to uninstall the HP Operations 
     Manager HTTPS Agent and SPI software.


1.7 Supported and Unsupported Features 

The following features are supported in HP Operations 
Manager HTTPS Agent and SPI Version T8.10-1:

- OpenVMS Integrity servers Version 8.2-1 or later
- Secure message passing through HTTPS communication
- Interoperation with Operations Manager Server for Windows 8.x
- Manual installation of certificates
- Heartbeat polling
- Static tracing
- VMS-SPI Support

The following features are "NOT" supported in HP Operations 
Manager HTTPS Agent and SPI Version T8.10-1:

- Non-English VMS boxes (Not certified for I18N compliance) 
- Remote installation of agents from the server
- Cluster fail-over (Claw)
- Dynamic tracing
- Automatic deployment of certificates
    o Requesting certificates from managed node using OVCERT 
      utility is not supported
- Tools/Utilities not supported:
    o Ovappinstance
    o Ovclusterinfo
    o ovcreg
    o ctrlbbcregwait
    o ctrlconfupd
    o ovdeplserver
    o ovlogdump
    o ovlogmsg
    o ovpath
    o ovtrcmsg
    o ovxplmsg
    o opccma
- Flexible Management
    o Agents on OpenVMS do not support this feature to configure more
      than one management server. Agents can send messages to the
      only Management server configured.
- Advanced Monitoring 
    o Agents do not support monitor type policies created using
      advance monitoring features such as pattern matching, 
      end action, and so on. 
- Service Discovery 
- Event Correlation
    o Agents do not identify relationships between event streams to
      generate manageable information.
- Interoperability with OVPA 4.0 on OpenVMS 
- Outbound only communication 

1.8 Known Issues

The following are the known issues in HP OpenVMS 
HTTPS Operations Manager Agent and SPI Version 8.10-1:

  - Some of the command utility options do not work, 
    For example,
    o You cannot use -DEREGISTER, -MIGRATE, -OVRG with bbcutil.exe
    o You cannot use -TRACE option with ovc.exe

  - On OpenVMS, the name of the trace configuration file (*.tcf)
    must be in mixed-case (i.e., OVTrace.tcf) for enabling 
    static tracing.

  - On OpenVMS, APP line in the trace configuration file (*.tcf) 
    must be in mixedcase (that is, OVTrace.txf) and must have 
    the .EXE extension.

    For example, 
    APP: OPCMSGA.EXE

  - The following error message can be ignored that is displayed 
    by some of the command utilities:  
    "ERROR: No input stream".
    
  - You cannot use the same shared disk to install the HP 
    Operations Manager HTTPS Agent and SPI software on more 
    than one cluster node.

  - Increase in I/O count for opcmsga and opcmsgi processes.

  - Co-existence of OVPA 4.0 with HP OpenVMS HTTPS Operations Manager 
    Agent and SPI Version T8.10-1.

    The default port used by the communication broker of HTTPS Agents 
    is 383. This has to be changed for HTTPS agents to a customized port
    number if the HTTPS Agents and OVPA 4.0 are to be used on the same 
    managed node.    

  - Following options are only supported by ovpolicy utility:
        -LIST
        -REMOVE
        -ENABLE
        -DISABLE

  - Ovdeploy only supports the -CMD option. 
    
    Note: This release does not support the rest of the ovdeploy options.
	
  - You cannot start ovbbccb and ovcd from the command prompt. 
    Ovbbccb is started by ovcd and ovcd is started by ovc.
 
  - /NAMES=AS_IS qualifier has to be used while compiling programs, 
    which are written using HTTPS Agents APIs. If you do not specify this
    qualifier, C converts the opc API calls to uppercase, and they 
    cannot be found at link time.

