OSM Migration and Configuration Guide (G06.30+)

OSM Server-Based Components
OSM Migration and Configuration Guide—527273-021
3-2
Optional OSM Configuration
Optional OSM Configuration
It is not necessary to create a configuration file to use OSM with the default settings.
However, if you want to alter any default settings or take advantage of the following
OSM features, you must create and use an OSMCONF file:
•
Configuring Additional TCP/IP Processes for OSM Connectivity on page 3-3.
•
Adjusting the processor priority rating assigned to OSM processes relative to other
applications. For more information, see “OSM Performance Considerations”
Support Note (S03133A).
•
Disabling Creation of System Inventory Files on page 3-4.
•
Some optional parameters for Configuring Automatic Data Collection on page 3-4.
•
Enabling Secure Sockets Layer (SSL) on page 3-6
Creating and Using an OSMCONF File
OSMINI is a template file delivered as part of T0682, to assist you in creating your own
(optional) customized OSMCONF file. Because the OSMCONF file is user-created and
not installed by OSM, when you upgrade to a new T0682 SPR, your customized
settings are not overwritten.
1. Go to $SYSTEM.ZSERVICE and copy OSMINI to create a new file named
OSMCONF.
2. Edit the OSMCONF file to customize the default settings as desired. To avoid
possible problems, delete blank lines from the OSMCONF file.
3. When you start OSM server processes, configuration settings are read from the
OSMCONF file if one exists in that location. If not, OSM default settings are used.
To change your settings after OSM is running, select Reload Configuration
Settings from the OSM Service Connection Tools menu. To complete this
operation, you are instructed to restart the $ZOSM and $ZOEV processes.
If you are already using a customized OSMCONF, and an updated OSMINI template
(with new settings that you want to take advantage of) is released, you can either:
•
Copy those particular settings (such as the setting for Enabling Secure Sockets
Layer (SSL)) into your existing OSMCONF file, and customize as needed; or
•
Use the OSMINI to create a new OSMCONF (in which case you would then have
to redo any changes you made to default settings in your previous OSMCONF).
To take advantage of new functionality that is enabled by default (such as Creation of
System Inventory Files), you do not have to add those settings to your OSMCONF file;
OSM uses default settings unless you override them in an OSMCONF file.