Installation for Oracle Solaris with Zones with XCOM

Products

XCOM Data Transport XCOM Data Transport - Linux PC

Issue/Introduction

Install XCOM Data Transport for Oracle Solaris specifying zones.

Environment

XCOM™ Data Transport® for Oracle Solaris
XCOM™ Data Transport® for UNIX/Linux PC

Resolution

To Install XCOM into:

The Global Zone Only issue:
groupadd xcomadm (Add to Global Zone /etc/group)
pkgadd -G -d /cdrom/CAXCOM.INS (From the Global Zone)

The Non-Global Whole Root Zone issue:
groupadd xcomadm (Add to Non-Global Whole Root Zone /etc/group)
pkgadd -d /cdrom/CAXCOM.INS (From the Non-Global Whole Root Zone)

The Non-Global Sparse Root Zone that inherits /usr issue:
groupadd xcomadm (Add to both Global and Non-Global Sparse Root Zone /etc/group(s))
pkgadd -G -d /cdrom/CAXCOM.INS (From the Global Zone)
pkgadd -d /cdrom/CAXCOM.INS (From the Non-Global Sparse Root Zone)

The Non-Global Sparse Root Zone that does not inherit /usr issues:
groupadd xcomadm (Add to Non-Global Sparse Root Zone /etc/group)
pkgadd -d /cdrom/CAXCOM.INS (From the Non-Global Sparse Root Zone)

To Uninstall XCOM from a:

Global Zone Only:
pkgrm XCOM (From the Global Zone)

Non-Global Whole Root Zone:
pkgrm XCOM (From the Non-Global Whole Root Zone)

Non-Global Sparse Root Zone that inherits/usr:
pkgrm XCOM (From the Global Zone)
pkgrm XCOM (From the Non-Global Sparse Root Zone)

Non-Global Sparse Root Zone that does not inherit/usr :
pkgrm XCOM (From the Non-Global Sparse Root Zone)

Configuring TCP/IP

The Txpi Service

With Solaris 10, many standard Solaris services are now managed by the Service Management Facility or SMF. Traditional UNIX start-up scripts, init run levels, and configuration files are now stored as an XML file called manifests. They contain a complete set of properties that are associated with a service or a service instance and are stored in the service configuration repository.
Once the /etc/service and /etc/inetd.conf files have been updated, the entries need to be converted and placed into SMF service manifests.

TCP/IP Configuration Summary

In general, follow these steps to configure TCP/IP:

To support remotely initiated transfers, modify the /etc/inetd.conf configuration file to include a subserver for the txpi service.
Add a service to the file services that defines a port address for XCOM Data Transport TCP/IP transfers.
For NIS, you must edit /etc/services on the NIS server.
For NIS client systems, you must also perform a push of the services data from the server system.
Update the inetd process (command line processing only)
To /etc/services add:
txpi 8044/tcp
txpis 8045/tcp
To /etc/inetd.conf add:
txpi stream tcp nowait root /opt/CA/XCOM/bin/xcomtcp REMOTE 0
txpis stream tcp nowait root /opt/CA/XCOM/bin/xcomtcp REMOTE 0 SSL
The following procedure converts inetd.conf entries into SMF service manifests and makes the entries available to the inetd process. This procedure needs to be run anytime a third-party application that depends on inetd is added to a system. Also run this procedure, if you need to make configuration changes to the entry in /etc/inetd.conf.
a. Become superuser or assume a role that includes the Service Management rights profile.
b. Convert the inetd.conf entries. The inetconv command converts each entry in the selected file into service manifests accessible by the inetd process.
inetconv -i filename
c. The following commands can be used to list properties and show the status of the txpi/tcp service:
i. List the properties for txpi service
inetadm -l /network/txpi/tcp
ii. Show the status of the txpi service
svcs -l /network/txpi/tcp

Additional Information

For additional TCP/IP configuration information, see Transfer Files Using TCP/IP Protocols

For additional information please see the Oracle Product Documentation: System Administration Guides: IP Services

For Installing and Upgrading and for adding and removing packages also see the Oracle Solaris Product Documentation:

System Administration Guide: Oracle Solaris Containers-Resource Management and Solaris Zones