Upgrading from Servicecontrol Manager 2.5 to 3.0

The SCM upgrade will install the 3.0 version of SCM and migrate your SCM data to be compatible with SCM 3.0. The upgrade installation migrates all custom data including:

users
nodes
node groups
tools
roles
authorizations

Multiple versions of SCM cannot coexist on the same system.




	CAUTION: The following directories are deleted during the SCM upgrade: /var/mx/ /etc/opt/mx/ /opt/webadmin/mx/ /opt/mx/ If you have stored files in these directories, you need to relocate those files prior to upgrading, or the data will be lost.




	NOTE: You must be running SCM 2.5 to upgrade to 3.0. If you are running a version of SCM earlier than 2.5, you must upgrade to 2.5 before upgrading to 3.0.SCM 3.0 agents are only compatible with an SCM 3.0 central management server (CMS). SCM 2.5 agents must be upgraded to 3.0 before you can manage them with a CMS running SCM 3.0.Linux managed nodes must be installed as new nodes. This procedure includes steps to remove existing SCM software from Linux managed nodes and install SCM 3.0.

Procedure 2-9 To upgrade from SCM 2.5 to 3.0:

Verify that SCM 2.5 is running on the system.
swlist B8339BA
If SCM 2.5 isn’t running, start it.
/sbin/init.d/ServCtlMgr start
Back-up your SCM data by copying the output of the mx commands into a file.
mxnode -ln > /directory/mxnode.scm25
mxngroup -ln > /directory/mxngroup.scm25
mxauth -lf > /directory/mxauth.scm25
mxuser -lf > /directory/mxuser.scm25
mxtool -lf > /directory/mxtool.scm25
mxrole -lt > /directory/mxrole.scm25
where directory is a directory that won’t be deleted during the installation upgrade.
Install the software on the CMS by following the instructions in the section “Installing Servicecontrol Manager on HP-UX”.
CAUTION: When upgrading the CMS, do not install the SCM software with other products at the same time.
Check the swagent.log file on the CMS for errors:
/var/adm/sw/swagent.log
Remove Debian 2.2 managed nodes if applicable. Debian is no longer a supported operating system.
1. Remove the agent software on each managed node:
  rpm -e mxagent
2. Remove the agent from the CMS configuration:
  mxnode -r -n node
  where node is the hostname of the managed node.
Upgrade existing HP-UX managed nodes:
1. Upgrade the SCM software on each HP-UX node and install the WBEM agent:
  swinstall -s server:directory B8339BA.SysMgmtAgent B8465BA
  where server is the hostname of the depot server and directory is the location of the depot files on the depot server.
2. Configure the managed node:
  /opt/mx/bin/mxagentconfig -a -n cms -p password
  where cms is the hostname of the CMS and password is the MxConfigPassword that you verified earlier.
3. Configure WBEM and start the cimserver on each managed node:
  /opt/wbem/sbin/cimconfig -s enableRemotePrivilegedUserAccess=true -p
  /opt/wbem/sbin/cimserver
Remove and add existing Linux managed nodes:
1. Remove any existing SCM software from the Linux managed nodesTitle not available. Follow the steps in “Removing Servicecontrol Manager”.
2. Add the Linux nodes by following the instructions in “Adding Managed Nodes”. This step can be performed in conjunction with adding new managed nodes in the following step.
Add new managed nodes by following the instructions in “Adding Managed Nodes”.

Additional Suggested Removal and Clean-up Tasks

There are several additional tasks you may want to perform to fully remove SCM 2.5 from your CMS system.

Remove Netscape Directory Server (NDS)

NDS provided the repository for SCM 2.5, and it is not removed during the upgrade in case you need to extract data from it after you upgrade. SCM 3.0 uses MySQL instead of NDS for the repository. Once you have verified that all your data successfully converted over to SCM 3.0, you can remove the NDS.




	CAUTION: Removing NDS deletes the data in the SCM 2.5 repository. If the data is important, make sure it is backed up first.

Procedure 2-10 To remove Netscape Directory Server:

Uninstall NDS by entering the commands:
cd /var/opt/netscape/server4
./uninstall
Select ALL to uninstall the entire NDS.
Remove the NDS product by running the command:
swremove J4258BA
Check the output for errors. If errors are reported, refer to the swagent.log file:
/var/adm/sw/swagent.log

Manually Converting a Tool From SCM 2.5 to 3.0

When you upgrade from SCM 2.5 to 3.0, your tools should automatically be converted from a TDEF file to a new XML tool definition file. If you need to manually convert tools after the upgrade, you can use the following procedure.

Procedure 2-11 To manually convert a tool

Create the XML file from the TDEF using the conversion tool:
/opt/mx/lbin/def2xml -t tdef_filename xml_filename
where tdef_filename is the name of the original TDEF file and xml_filename is the name of the new XML file.
Add the tool to SCM:
mxtool -a -f xml_filename
where xml_filename is the name of the new XML file.
Verify the tool:
mxtool -ld -t “Tool Name”
where Tool Name is the name of the new tool.

Upgrading from Servicecontrol Manager 2.5 to 3.0

Technical documentation

» Table of Contents

» Glossary

» Index

Additional Suggested Removal and Clean-up Tasks

Remove Netscape Directory Server (NDS)

Manually Converting a Tool From SCM 2.5 to 3.0