7 Installing The Client Workstation

This chapter explains how to install the client application onto your workstation. You need the client installed to complete post installation tasks for the database and application server installations.

This chapter also provides information on distributing the client application to users across a network.

Installation Methods

You can distribute the client application to workstations in the following ways:

  • By using a third-party software product such as Microsoft SMS.

  • By copying the compressed client CAB files stored on the application server to a location where you can expand them for users to copy to client workstations or use directly.

Editing Internet Explorer 11 Registry Settings

By default, Internet Explorer (IE) 11 uses WINDOWLESS SELECT control and hence you can view all the values in a drop-down list but not select them. To select a value from the drop-down list, add the WINDOWLESS Select Control value to the IE 11 registry settings.

To edit the registry settings:

  1. Open cmd.exe.

  2. Enter the following:

     "REG ADD "HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_USE_WINDOWEDSELECTCONTROL" /V tbs.exe /T REG_DWORD /F /D 1"
    

    Upon successful completion, The operation completed successfully message appears.

Installing the Client Application Manually

The following procedure explains how to install the core MSS application. It does not include any utility applications.

To install the client application manually:

  1. Create a directory in the location where the client installation will be placed.

  2. Copy the following files from the listed application server directories to the client installation location.

    • /appserver/cab

      • All CAB files

      • expand_mss.cmd

    • /appserver/config

      • jmaster.ini

      • lerg.ini

      • npasplit.ini

      • tbs.ini

      • tbs_util.ini

    • /appserver/gateway

      • gateway.ini

        Note:

        If you are copying the files using the FTP site, use the following modes for different file types:

        • CAB files: Binary mode

        • CMD, XML, and INI files: ASCII mode

  3. Run expand_mss.cmd using the Run option on the Windows Start menu.

Starting the MSS Client

Start the client using one of the following procedures:

  • On the MSS Start page, click MetaSolv Solution.

  • From the Start menu select Programs, select MetaSolv, select MetaSolv Solution v.6.3.

    If you installed manually, you must add the menu option to the Start menu in Windows to start MetaSolv Solution.

  • Double-click the executable file (tbs.exe) located in the MSS installation directory on the workstation.

  • Users can create a desktop shortcut to start the application after installation. The following example shows how the http:// address for a customized ZAC page with links might look when distributed to users.

    http://host_server_name:port_number/HTML page?app=mss 
    

    or in cluster or load balancer environment:

    http://load_balancer_virtual_IP_address:port_number/HTML page?app=mss
    

Tools and Utilities

This section describes special considerations for MSS tool and utility applications. See MetaSolv Solution System Administrator's Guide for information on using these applications.

NPA NXX Split Utility

Before you can run this application, you must:

  • Modify the INI file

  • Create Oracle tables by applying the latest MSS maintenance release

The following sections explain how to complete these tasks.

Modifying the NPASplit.ini File

Before running the utility, you must customize the npasplit.ini file. The file is set up identically to the tbs_util.ini file in the client installation directory folder, so the logon database name and Oracle SID can be copied from that file.

To modify the npasplit.ini file:

  1. Locate the file in the client installation directory and open it in a text editor.

  2. Change the Example1 text in the Profiles section to the name the users will pick from the Database drop-down box in the initial logon window.

    Any changes must match the title of the Profile listed in brackets that appears later in the file (for example: [Profile Example1]). Additional profiles can also be added in the same manner.

  3. Change the value in the ServerName field to the Oracle SID shortcut in the TNSNames.ora file.

    The easiest method of finding this information is in the tbs_util.ini file (for example:

    ServerName=@EXAMPLE1 
    
  4. Save the npasplit.ini file with these changes.

Creating NPA NXX Split Utility Oracle Tables

The utility uses Oracle tables that are not found in the MSS database. To ensure that you have the appropriate Oracle tables for the NPA Split Utility, apply the latest MSS maintenance release. These tables must be created prior to the execution of a split.

To create the tables, do the following:

  1. Download the npasplit.cab and expand_mss.cmd files from the MetaSolv_Home/server_name/appserver/cab directory, on the WebLogic Administration server, to a directory on the client workstation.

  2. On the client workstation, run the expand_mss.cmd file to expand the npasplit.cab file.

  3. Connect to SQL*Plus and run the following script:

    • Install.sql

      Note:

      There is also an Uninstall.sql file available to undo the changes, if necessary.

MetaSolv Solution Utilities

Copy the appropriate files download to your workstation and the logon window appears.

If you are installing manually, copy the appropriate files into the client installation directory for MSS. See Table 7-1 for information on which files are needed for MSS Utilities.

If you want to run the Purge utility from a client workstation, you must install the Oracle 10.2.0.4+ client on the workstation to establish a connection to the database.

Note:

Ensure that you have added the DB instance entry in the TNSNames.ora file on the workstation.

Background Processor

Oracle recommends installing this application on a separate machine. This application has two executables:

  • Job Manager - is installed on a client workstation to view and manage jobs being processed

  • Job Master - is installed on a separate machine to do processing

See MetaSolv Solution System Administrator's Guide for complete information on the Background Processor.

This application requires the Oracle client.

See Table 7-1 for information on which files are needed for this application.

Location and Routing Gateway

Copy the appropriate files into the client installation directory for MSS. See Table 7-1 for information on which files are needed for this application.

Installing a Utility to a Separate Installation Directory

Oracle recommends installing MSS applications in the same directory on the workstation. The exception to this rule is the Background Processor, which should be installed in its own directory on a separate machine.

You can install an application in a directory other than the MSS installation directory if you choose. If you use this method, you must make sure the INI file for the application you are copying is in the same installation directory as the application. If you install manually, make sure that you edit the INI file for the utility you install to point to the appropriate application server.

Table 7-1 lists the CAB, INI, and XML files required for each application.

Table 7-1 MetaSolv Solution Application Files

Application CAB file(s) required INI files required Install to

MSS core application

app.cab

dll.cab

pbvm.cab

mapping.cab

tbs.ini

Client installation directory

Job Manager

(Background Processor)

jobmgr.cab

pbvm.cab

dll.cab

jmaster.ini

Machine dedicated to running this application

Job Master

(Background Processor)

app.cab

jobmstr.cab

pbvm.cab

dll.cab

jmaster.ini

Machine dedicated to running this application

Location and Routing Gateway

lerg.cab

pbvm.cab

dll.cab

lerg.ini

Client installation directory

MetaSolv Solution Utilities

utility.cab

pbvm.cab

dll.cab

tbs_util.ini

Client installation directory

NPA NXX Utility

npasplit.cab

pbvm.cab

dll.cab

npasplit.ini

Client installation directory