temip_setup(1) — Commands

NAME

temip_setup − TeMIP Framework configuration tool

SYNOPSIS

temip_setup [-h] [-f filename]

DESCRIPTION

The temip_setup tool is used to configure TeMIP This tool must be run directly after product installation to set up the initial configuration, or each time the configuration must be changed.

Before changing any configuration parameters, temip_setup runs some checks (See Restrictions). These checks may abort temip_setup.

The configuration consists of several steps. It is possible to run them independently. Each step may ask some questions. Depending on previous questions, some steps may be omitted, or may produce a different result.

The possible steps are:

− Run a full TeMIP configuration:
This step will run all steps of TeMIP configuration

− Configure TeMIP Director:
This step is used to select the configuration of your director. During this step, you will have to set the Director host, the Director user account, the Director name, the Director mode and the namespace used by TeMIP Framework.

The director is configured according to your choices (temip_config call).

If the director has already been configured, this step prints the current director configuration (using temip_config -l) and then asks you if you wish to keep the current configuration or modify it.

If you answer yes, the current configuration will be kept, only the director user account can be changed.
If you answer no, the director will be reconfigured and all the applications recreated.

Director host selection:

The director host is the host name used by the local director, the default is the local host. In an ASE environment, set the director host to the virtual host name.

Director user account selection:

In the TeMIP Framework process model, each management module (AM or FM) is implemented as a single process whatever the number of different users requiring services from it.

All the management module processes run under the same user-id, called the ’Director User Id’.

This step asks you to choose the ’Director User Id’: the user account under which all management module processes will run.

Note that you do not have to reconfigure your director to change the director user name.

Director name selection:

The default director name is .temip.<hostname>_director. Note that if you change the name of your director, temip_setup will try to delete your local osi system entity.

Namespace selection:

This step asks you to choose the namespace to be used by TeMIP Framework.
The two different namespaces are TNS and MIR. If you choose a distributed namespace (TNS), you will have to configure your TNS clerk.

Note: TeMIP Framework Distribution requires the use of TNS. Selecting MIR implies a Non-Distributed director configuration.

Director mode selection:

There are 4 possible director configurations depending on the software subsets currently installed on the system:

Non-Distributed:
choose this mode if you do not wish to use TeMIP Distribution. This mode is valid if the BASE, PM and SERVER subsets are installed.

Full-Server:
choose this mode if you wish to use TeMIP Distribution and you wish to configure the system to be a distribution server - a director that can send calls to other directors (or receive calls from them). This mode is valid if the BASE, PM and SERVER subsets are installed.

AM/FM-Server:
choose this mode if you wish to use TeMIP Distribution and you wish to configure the system to be an Access Module server - a director that can send calls to other directors or receive calls from them, but that does not run any Presentation Modules. This mode is valid if at least the BASE and SERVER subsets are installed.

Client:
choose this mode if you wish to use TeMIP Distribution and you wish to configure the system to be a distribution client - a director that can send calls to other directors, but that cannot receive calls from other directors. This mode is valid if at least the BASE and PM subsets are installed.

After the director creation, all the applications needed to support the chosen director configuration, and the basic configuration are created.

OSI system selection:
If you selected Test Object in your basic configuration, you must specify the local OSI system name. In this case, the local OSI system entity is created and registered.

− Basic configuration:
This step asks you to specify if you wish to run one of the following functions:

TeMIP Alarm Handling
TeMIP Event Logging
TeMIP Trouble Ticketing
TeMIP Test Object

If you answer "no", the corresponding applications will be removed.
If you answer "yes", they will be created;
You will be also asked if you want to use the TeMIP Alarm Handling Archive function, and the TeMIP Trouble Ticketing FM. If you answer "yes" you will have to select the database system for TeMIP Alarm Handling Archive, (TeMIP Trouble Ticketing supports only the Oracle database system).

This step also asks you if you wish to use the DECnet-Plus Access Module and communication stack for Collection Access Module.

If you answer "no", the corresponding applications will not be configured and the tool will ask if you want to use a dictionary including any DECnet-Plus definitions. A dictionary without any DECnet-Plus definitions will be significantly reduced in size.
If you answer "yes", the corresponding applications (dna4_am and dna5_am) will be created and the installed dictionary will contain the full TeMIP Framework definitions.
If you do not choose to use DECnet-Plus communication stack for Collection Access Module, UDP/IP will be used.

Note: TeMIP Distribution requires that all dictionaries be compatible in a distributed configuration. If you do not plan to use the DECnet-Plus Access Module, you should anser "no" to this question for all your directors, if you plan to use the DECnet-Plus Access Module on any director, you should answer "yes" to this question for all your directors.

− Dictionary and dispatch table installation:

Copying dictionary file:
According to the choice made in the Basic configuration step (DECnet-Plus configuration), this step installs the working dictionary.

If a dictionary exists in the /usr/mcc/mcc_system directory, this step asks you whether to keep it or to overwrite it with the default dictionary installed in the /usr/mcc/mcc_system/delivered directory.

Note that the dictionary installed corresponds to the en_US.ISO8859-1 language. Selecting another language requires manual operations.

Copying dispatch table file:
A dispatch tables file containing entries for all TeMIP modules is delivered with the kit.

This step will either install the dispatch tables file delivered with the kit or ask you if you wish to overwrite the existing dispatch tables file (in the case of a reinstallation).

If you have chosen to overwrite the existing dictionary and dispatch tables files, re-enroll any private Management Module after temip_setup execution.

− Load a predefined TeMIP configuration:

This step loads a predefined TeMIP configuration.
Default directory for configuration files storage is /var/mcc/config/temip_setup, a full path can also be used.
The configuration file format is :

<Keyword>=<Value>

The available keywords are :

TEMIP_IS_USED: Run one of the TeMIP Alarm Handling, Event Logging, Trouble Ticketing and Test Object applications. Possible value: y/n

TT_IS_USED: Run TeMIP Trouble Ticketing application. Possible value: y/n

AH_ARCHIVE_IS_USED: Run the TeMIP Alarm Handling Archive. Possible value: y/n

DATABASE_AH: Relational database used for TeMIP Alarm handling Archive. Possible value: oracle/sybase

DATABASE_TT: Relational database used for Trouble Ticketing. Possible value: oracle

DNA5_IS_USED: Run the DECnet-Plus (Phase V) or Phase IV Access Modules. Possible value: y/n

DECNET_IS_USED: Use the DECnet-Plus communication stack for collection Access Module. Possible value: y/n

OVERWRITE_DICTIONARY
OVERWRITE_DISPATCH_TABLE: In case of existing dictionary and dispatch table, overwrite flag. Possible value :y/n

INPUT_TIME_MODE: Default formats for time/date values used as input by the PMs. Possible value: LOCAL/UTC
OUTPUT_TIME_MODE: Default formats for time/date values used as output by the PMs. Possible value: LOCAL/UTC/UNIXLOCAL/UNIXUTC
OUTPUT_TIME_TRUNCATION: Significant output positions on absolute time display. Possible value: [1-79].

MIR_LOG: MIR transaction logging mechanism. Possible value: on/off

KEEP_DIRECTOR: Keep the existing director. Possible value: y/n

DIRECTOR_HOST: The Director host name. Possible value: a reachable host

DIRECTOR_NAME: The Director name.

DIRECTOR_USER_NAME: The Director user Id. Possible value: an existing user id

NAMESPACE: The namespace used for distribution. Possible value: LOCAL_NS/DEFAULT_NS/An existing namespace
LOCAL_NS for a non distributed configuration (MIR).
DEFAULT_NS for the current default namespace (set using tns_clerk_setup tool)

DIRECTOR_TYPE: The director mode. Possible value: N/F/A/C
N for a Non distributed configuration
F for a Full Server configuration
A for a AM/FM Server configuration
C for a Client configuration

TEMIP_MODE: The TeMIP V3.1 backward compatibility flag. Possible value: V3.2/V3.1

LOCAL_OSI_SYSTEM: Local OSI System name

UPDATE_MAN_PAGES: Update Man pages flag. Possible value: y/n

HELP_MODE: On line Help mode. Possible value: remote/local
HELP_REMOTE_URL: URL value for TeMIP documentation location.

START_DIRECTOR: Starting director flag. Possible value: y/n

The special values %HOSTNAME% and %FULL_HOSTNAME% can be used to specify the local host name.

Example : If your local host is myhost.xyz.com

DIRECTOR_NAME=.temip.%HOSTNAME%_director
Will be replaced by
DIRECTOR_NAME=.temip.myhost_director

DIRECTOR_HOST=%FULL_HOSTNAME% Will be replaced by
DIRECTOR_HOST=myhost.xyz.com

Templates of configuration files are installed in the /usr/mcc/mmtoolkit/examples directory.

temip_full_server.conf for a Full Server configuration
temip_no_distri.conf for a Non distributed configuration
temip_client.conf for a PM Client configuration
temip_amfm_server.conf for an AM/FM server configuration

− Save the current TeMIP configuration:

This step saves the current TeMIP configuration in a file.
Default directory for configuration file storage is /var/mcc/config/temip_setup, or enter a different full path.

− Configure TeMIP for an ASE configuration:

Run this step after the configuration of the director on the first member of an ASE configuration, on all the other members. This step will create softlinks needed by TeMIP and add the local host to the support hosts list of the director.

− Configure TeMIP Documentation (man pages, HTML):

This step updates the man pages database with TeMIP utilities man pages. This step also configures the PM on line help with the HTML documentation.

− Check system parameters and TeMIP subsets:

This step checks that your system parameters are set with the value recommended by TeMIP, and displays all installed TeMIP product subsets (TeMIP, OSI Access Module, Graphical Ascii Toolkit...).

− Run scripts for other TeMIP products setup

This step asks if you want to run the setup scripts for all other TeMIP products (Visual TeMIP, OSI Access module...) if they are installed. You can customize the list of the scripts in the file /usr/mcc/mcc_system/temip_setup.conf:

<script name># <script description>

Example :
/usr/bin/visual_temip_setup# Visual TeMIP C++ Developer Toolkit setup

− Director starting:
At the end of execution, temip_setup asks if you want TeMIP Framework to be started.

If you answer "yes", you will be able to enter TeMIP Framework commands directly after temip_setup execution.
If you answer "no", TeMIP Framework will be stopped after temip_setup execution. Use the temip_start command to start TeMIP Framework.

− Configure TeMIP Development Mode:

This step asks if you want to configure TeMIP Development Mode. This option is only available if the "Visual TeMIP C++ Developer Toolkit" subset is installed on the system.
If you answer "yes", any users who belong to the "TeMIP director user" group will be able to run the TeMIP MSL Translator (mcc_msl), the TeMIP Parser table builder (mcc_ptb) and the TeMIP Enroll utility (temip_enroll). The TeMIP director user will also be able to start and stop TeMIP using temip_stop and temip_start tools, and to change the director configuration using temip_config. The default user profile becomes the root user profile.

FLAGS

The following options are allowed with temip_setup:

-h
displays the help

-f filename
Loads a predefined TeMIP configuration from a file.

RESTRICTIONS

temip_setup can only be run under super-user.

Some options cannot be run if TeMIP Framework processes are currently running.

temip_setup cannot be run if the minimum TeMIP Framework subsets required are not installed.

temip_setup may modify or overwrite some files including user definitions. After temip_setup execution, such files must be updated in order to re-enter user definitions. The files are as follows (those marked with ∗ are saved before being overwritten):

dictionary
dispatch table
configuration file (∗)

FILES

temip_setup may modify a lot of configuration files of TeMIP Framework,
depending on the selected configuration.

Museum

Related Articles