Configuring Tivoli Enterprise Portal Server

You can configure the portal server by using either the command line or GUI.

About this task

This configuration accomplishes the following tasks:
  • Automatically enables application support on the portal server for the base monitoring agents.
  • Includes steps for configuring the connection between the portal server and the following components:
    • The hub monitoring server
    • The portal server database
    • The Tivoli Data Warehouse database
Follow these steps to configure the server by using command line:

Procedure

  1. Log in to the computer where the Tivoli Enterprise Portal Server is installed as root user.
  2. Change to the <install_dir>/bin directory from command line, where <install_dir> is the directory where you installed the product.
  3. Run the following command to start configuring the Tivoli Enterprise Portal Server: 
    ./itmcmd config -A cq
    Where cq is the product code for the portal server.
  4. Use the default values in the prompts that appear as follows: 
    
Agent configuration started...
Edit "Common event console for IBM Tivoli Monitoring" settings? [ 1=Yes, 2=No ] (default is: 1):
Edit 'ITM Connector' settings? [ 1=Yes, 2=No ] (default is: 1):
Enable this connector [ 1=Yes, 2=No ] (default is: 1):
Connector name (default is: ITM1):
Maximum number of events for this connector (default is: 100):
View closed events [ 1=Yes, 2=No ] (default is: 2):
Edit 'TEC Connector' settings? [ 1=Yes, 2=No ] (default is: 1):
No 'TEC Connector' settings available.
Edit 'TEC Connector' settings, [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5):
Edit 'OMNIbus Connector' settings? [ 1=Yes, 2=No ] (default is: 1):
No 'OMNIbus Connector' settings available.
Edit 'OMNIbus Connector' settings, [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5):
Edit 'Names of Extra Columns' settings? [ 1=Yes, 2=No ] (default is: 1):
Name of extra column 1 (default is: ):
Name of extra column 2 (default is: ):
Name of extra column 3 (default is: ):
Name of extra column 4 (default is: ):
Name of extra column 5 (default is: ):

Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):

Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe):

     Now choose the next protocol from one of these:
     - ip
     - sna
     - ip.spipe
     - ip6
     - ip6.pipe
     - ip6.spipe
     - 0 for none
Network Protocol 2 (Default is: 0):
TEMS Host Name for IPv4 (Default is: tnpmuslnx0107):
IP.PIPE Port Number (Default is: 1918):
Enter name of KDC_PARTITION [type 0 for null] (Default is: 0):

Enter Optional Primary Network Name or 0 for "none" (Default is: 0):
Enable SSL for TEP Clients (1=Yes, 2=No)(Default is: 2):
Notice: Embedded TEPS DB is not supported for distributed cluster configurations.
Which database would you like to use for TEPS (1=Embedded, 2=DB2)(Default is: 2): 1
Notice: The Warehouse DB must be an existing database, no new database will be created automatically.
Are you using DB2, Oracle or None for Warehouse? [1=DB2, 2=Oracle, 3=None] (Default is: 1): 3

LDAP Security: Validate User with LDAP ? (1=Yes, 2=No)(Default is: 2):

Enable the dashboard data provider ? (1=Yes, 2=No)(Default is: 2):
Tivoli Enterprise Portal server configuration was updated to reflect Eclipse Help Server 
configuration changes.
... running InstallPresentation.sh
... InstallPresentation.sh completed
Agent configuration completed...