Installation information checklist
You can define checklists for all Netcool Configuration Manager servers that are to be installed as part of the deployment. Details you must assemble before installation include server names, passwords and system paths.
IDT servers
If you have multiple presentation servers in a deployment of Netcool Configuration Manager, one server must be chosen as the main, or master, presentation server. This means that all IDT connections will be passed through this server if you are running IDT in master mode. For more information, see the Administration Guide.
Netcool Configuration Manager installation information
As part of a presentation server installation, you can install Netcool Configuration
Manager using a federated
repository. - Required
- If you are installing into the same DASH instance as an existing deployment of Network Manager and Tivoli Netcool/OMNIbus, using a federated repository is a requirement.
- Optional
- If you are installing into a separate instance of DASH, you can still set up Netcool Configuration Manager authentication with the Tivoli Netcool/OMNIbus Object Server as described in Creating and configuring a federated user repository for Netcool Configuration Manager.
Note: Ensure the default administrator, observer
and operator users are created in the federated repository.
Note: Do not make use of spaces in any names provided for the checklist.
| Type | Information | Details | Default value |
|---|---|---|---|
|
Note: If you do not supply a root realm, it defaults to itncm
|
|||
| License | Accept / reject | You can choose to print the license, or return to the previous screen. If you do not accept the license, the installation is aborted. | none |
| Installation directory | You can choose your own location. Note: Install Manager requires an empty
directory for an initial installation of Netcool Configuration
Manager.
|
/opt/IBM/tivoli/netcool/ncm | |
| Server Installation type | Presentation server + worker server / Worker server | Depends on whether the installation is part of a stand-alone installation, or
a distributed installation. Note: To improve load balancing, a distributed installation can have
more than one 'GUI server + worker server' installation type.
|
Presentation server + worker server |
| Database | Oracle or DB2 | Must be installed and configured beforehand | DB2 |
| If Oracle database | IP address/ hostname | ||
| Port | 1521 | ||
| SID | itncm | ||
| Service name | itncm | ||
| Username | |||
| Password | |||
| If DB2 database | IP address/ hostname | ||
| Port | 50000 | ||
| Name | |||
| Alias | itncm | ||
| Username | |||
| Password | |||
| Netcool Configuration Manager details | Root realm | ITNCM | |
| Superuser password | |||
| FTP | Server | ||
| User account | |||
| Password | |||
| User account directory | /home/icosftp | ||
| SMTP server | SMTP server | For example, smtp.IBM.net | |
| Current server | Instance name | Unique Netcool Configuration Manager server name | |
| If worker server installation type | Activate Configuration-core | Depends on what kind of distributed installation is being performed. Note: A
mandatory selection in a presentation installation.
|
Selected |
| Activate Compliance Core | Depends on what kind of distributed installation is being performed. If not selected during a Presentation server installation, then the Compliance GUI and Compliance Core will not be available. | Selected | |
| Linked Server | Enables the worker server about to be installed to reuse the
drivers already installed on this server. Note: The existing installation must have the drivers
installed and the correct deployment keystore files in place. If you choose to link to an existing
server, you must provide the installation directory (default =
/opt/IBM/tivoli/netcool/ncm).
|
Not a Linked Server | |
| Not a Linked Server | |||
| Administration ports Note: If you are installing a
worker server and linking it to an existing Netcool Configuration
Manager installation on the
same server, the default ports will already be in use. Therefore you must specify new, unused
ports.
|
Admin port | 8101 | |
| Log server admin port | 8102 | ||
| Log server port | 8103 | ||
| IDT daemon port | 8104 | ||
| Compliance administration port + next five consecutive ports | Specifies the Netcool Configuration Manager - Compliance administration port. The next five consecutive ports will be selected automatically. | 8110 | |
| Main IDT Daemon Server | Yes / No | Depends on whether the installation is part of a stand-alone installation, or a distributed installation. Also depends on what kind of distributed installation is being performed. | Yes |
| Network Manager DASH server | NM Hostname | ||
| NM port to connect to | 16311 | ||
| NM User | itnmadmin | ||
| NM User password | |||
| NM User password confirmation | |||
| Realm | The realm to import the devices to | ITNCM/@DOMAINNAME | |
|
|
Using a federated repository | From fix pack 2 onwards you can install Netcool Configuration Manager using a federated repository. This repository requires two groups and three users to be created before the Install Groups. | User names are case-sensitive. Groups:
Users:
|
| Jazz for Service Management properties | Configuration for a Presentation Server Only | ||
| Installation Directory Details | |||
| AppServer Installation Directory Details | |||
| User Name | |||
| Password | |||
| Automatically Configured Variables | |||
| Server Name | Selected automatically depending on the JazzSM Installation Directory given | ||
| Server Cell t | |||
| Server Node | |||
| HTTP Port | |||
| HTTPS Port | |||