Oblicore Guarantee 6_3_SR1 Installation Guide

Oblicore Guarantee™ 6.3 Service Release 1

Installation Guide

© 2000–2009 Oblicore Inc. All rights reserved. Oblicore Guarantee™ 6.3 Service Release 1. This document is subject to the following conditions and restrictions: It contains Oblicore, Inc proprietary information. This information is supplied solely for the purpose of assisting

explicitly and properly authorized users of Oblicore Guarantee™. No part of its contents may be used for any other purpose, disclosed to any person or firm or reproduced by any

means, electronic or mechanical, without the express prior written permission of Oblicore, Inc. The text and graphics are for the purpose of illustration and reference only. The specifications on which they are

based are subject to change without notice. The software described in this document is furnished under a license. The software may be used or copied only

in accordance with the terms of that agreement. Information in this document is subject to change without notice. Corporate and individual names and data used

in examples herein are fictitious unless otherwise noted. Oblicore Guarantee™ is a trademark of Oblicore, Inc. Other company and brand products and service names are trademarks or registered trademarks of their respective holders.

Release Information

Software Version: 6.3 Service Release 1 Release Date: 14 August, 2009 Last Updated Date: 14 August, 2009

Contents Introduction ................................................................................................... 1

Target Audience......................................................................................................1 Additional Help........................................................................................................1 Package Content ....................................................................................................2

Overview ........................................................................................................ 3

Installing Oblicore Guarantee™ 6.3 Service Release 1 from Scratch....... 5 Prerequisites ...........................................................................................................6 Installation Process.................................................................................................7

Typical Installation............................................................................................................7 Custom Installation...........................................................................................................8

Creating a New Database Manually........................................................................9 From Scratch Post-installation Activities ...............................................................10

Upgrading From a Previous Version of Oblicore Guarantee™ ............... 13 Prerequisites .........................................................................................................13 Upgrading Process................................................................................................15 Upgrade Post-installation Activities.......................................................................15

Enabling the Oracle Database CURSOR Sharing Feature ...........................................18 Updating Adapters Not on Oblicore Server....................................................................18

Client Installation ........................................................................................ 19 Introduction ...........................................................................................................19 Supported Platforms .............................................................................................19 Client Components................................................................................................19 Installation Process...............................................................................................20 Post-installation Activities......................................................................................20

Online Help Installation............................................................................... 21

Creating a Local User Account .................................................................. 23

Additional Application Servers Installation .............................................. 25 Dividing Oblicore Guarantee™ Services...............................................................25 Placing Adapters on Different Servers ..................................................................26

Uninstalling Oblicore Guarantee™ 6.3 Service Release 1 ....................... 27

Typical Installation Windows ..................................................................... 29

Custom Installation Windows .................................................................... 31

Oblicore's Naming Conventions Policy for Database Objects ................ 33

Oblicore Guarantee™ Environment Checklist.......................................... 35

AdapterLocaleFix Tool................................................................................ 39

High Availability Installation....................................................................... 41 Introduction ...........................................................................................................41

Target Audience.............................................................................................................41 Using this Appendix .......................................................................................................41 Additional Help ...............................................................................................................41 Installation Platform........................................................................................................41

ii Oblicore Guarantee™ 6.3 Service Release 1 Installation Guide

Abbreviations .................................................................................................................42 Overview ...............................................................................................................42

Common Files ................................................................................................................42 Load Balancing ..............................................................................................................43

Installing Windows Clusters ..................................................................................43 Installing Windows Network Load Balance (NLB).................................................47 Installing Oblicore Software on the Clusters and NLB Nodes...............................49 Oblicore Software Configuration ...........................................................................50

Adapter Manager Configuration.....................................................................................53 Adapter XML File Configuration.....................................................................................53 Adapter Details UI Page.................................................................................................53 Adapter Data Source Files Location ..............................................................................54 Balance Oblicore Services and Adapter Programs between the Cluster Nodes...........54

Upgrading from a Previous Version of Oblicore Guarantee™ ..............................55 Index............................................................................................................. 57

Chapter 1

Introduction Oblicore Guarantee™ 6.3 Service Release 1 is an accumulative update to Oblicore Guarantee™ version 4.0 Service Release 2 or higher that can also be installed from scratch.

This guide describes instructions for installing Oblicore Guarantee™ 6.3 Service Release 1 from scratch or as an upgrade. The installation process includes database changes.

Important: The database must be backed up prior to upgrading and the servers must be rebooted after installation.

Target Audience This guide is intended for personnel who are required to install or upgrade Oblicore Guarantee™ 6.3 Service Release 1.

Additional Help For additional help installing Oblicore Guarantee™ contact the Oblicore Support team:

By Phone:

Toll free number in Germany: +49 (0) 800 189 0489

Toll free number in France: +33 (0) 800 906 553

Toll free number in the UK: +44 (0) 800 404 9235

Toll free number in the US: +1 877 534 6770

Toll free number in Australia: +1 800 193 212

International number: +972 9 762 7000

By email:

For Asia-Pacific: [email protected]

For Europe, Middle East and Africa: [email protected]

For North America: [email protected]

mailto:[email protected]�



2 Oblicore Guarantee™ 6.3 Service Release 1 Installation Guide

Package Content Prior to installation, verify that you have all the required files as listed below in order to perform the installation.

File Name Description

OG63SR1.exe Application setup file

OG63SR1.Log_Enabled.bat Batch file that runs the Application setup file and creates a log file.

OG63SR1_Onlinehelp.exe Online Help setup file

OG63SR1_Onlinehelp.Log_Enabled.bat Batch file that runs the Online Help setup file and creates a log file.

OG63SR1_Client.exe Client setup file

OG63SR1_Client.Log_Enabled.bat Batch file that runs the Client setup file and creates a log file.

Documentation Folder containing the Oblicore Guarantee™ 6.3 Service Release 1 documentation portfolio.

Post_Install Folder containing required post installation tools.

Prerequisites Folder containing files required prior to installation or upgrade of Oblicore Guarantee™ 6.3 Service Release 1.

Setup DB Folder containing files for installation or upgrade of Oblicore database instance, and other database tools.

Chapter 2

Overview Oblicore Guarantee™ 6.3 Service Release 1 can be installed on several topology types. Prior to installation, identify your topology type from the table below.

Topology Type Description Installation Sequence

Single server Database, Application, and Web components are installed on same server.

Run OG6.3SR1.Log_Enabled.bat on this server.

Two servers Distributed on two servers. First server: Database component Second server: Application

component and Web component

Installation from scratch • Create database on Database server • Install Application and Web servers

Upgrade Run OG6.3SR1.Log_Enabled.bat on Application/Web server

Three servers Distributed on three servers. First server: Database component Second server: Application

component Third server: Web component

Installation from scratch • Create database on Database server • Install Application server • Install Web server

Upgrade • Run OG6.3SR1.Log_Enabled.bat on

Application server • Run OG6.3SR1.Log_Enabled.bat on

Web server

Four servers or more

Distributed on four servers or more. First server: Database component Second server: Application

component Third server: Web component Fourth server: Additional

application components

Installation from scratch • Create database on Database server • Install Application servers • Install Web server • Install additional application

components Upgrade • Run OG6.3SR1.Log_Enabled.bat on

all Application servers • Run OG6.3SR1.Log_Enabled.bat on

Web server

Important: If you intend to change installation topology type, contact Oblicore support before performing the installation.

Chapter 3

Installing Oblicore Guarantee™ 6.3 Service Release 1 from Scratch This chapter describes the steps required to install Oblicore Guarantee™ 6.3 Service Release 1 from scratch.

The Oblicore Guarantee™ 6.3 Service Release 1 installation files can be downloaded from the Oblicore FTP site or are available on the OG6.3SR1 CD.

To receive the necessary files, contact Oblicore Support.

If using the Oblicore FTP site, download the files to a local directory.

If using the OG6.3SR1 CD, copy the contents of the CD to a local directory.

Notes:

• If Oblicore Guarantee™ 6.3 Service Release 1 is installed on more than one server, installation must be in the following sequence: Database, Application, and then Web.

• If your database naming convention is different than Oblicore's policy, print "Appendix C - Oblicore's Naming Conventions Policy for Database Objects" on page 33, fill it out and consult the Oblicore support department before installation.

• Oblicore highly recommends printing "Appendix A - Typical Installation Windows" on page 29 and "Appendix B - Custom Installation Windows" on page 31 prior to installation, so as to have handy the installation window parameters information.


Prerequisites Prior to installing Oblicore Guarantee™ 6.3 Service Release 1 verify that: Your hardware and software conform to Oblicore Guarantee™ 6.3 Service Release 1

system requirements. For more information, see the Oblicore Guarantee™ 6.3 Service Release 1 System Requirements and Supported Platforms document available from the Oblicore Support Center.

Note: Oblicore recommends contacting your DBA to make sure that the selected hardware conforms to your company’s policies and guidelines.

A user that has administration privileges is used for running the installation. If installing Oblicore Guarantee™ 6.3 Service Release 1 on three or four servers, the

Application and Web servers are time synchronized. Oracle OLEDB Provider is installed on the Application and Web servers. For the exact

version, see the Oblicore Guarantee™ 6.3 Service Release 1 System Requirements and Supported Platforms document.

Notes:

• When installing the Oracle OLEDB Provider, make sure to install it to the existing Oracle home.

• For any assistance with the Oracle OLEDB Provider installation, contact the Oblicore support team

Microsoft .NET Framework 3.5 is installed. The file is located under the \Prerequisites folder.

Oblicore recommends that you use a domain account instead of a local account during installation of Oblicore Guarantee™ 6.3 Service Release 1. When using a domain account, the same account should be used for all Oblicore servers.

Any account that will be in use, must be a member of the local administrator group and the necessary details for installation must be known.

Oblicore Guarantee™ 6.3 Service Release 1 installation directory name does not contain the '&' and '.' (dot) characters.

The operating system's regional settings are identical to the Oracle's regional settings to avoid an error.

If installing Oblicore Guarantee™ 6.3 Service Release 1 on more than one server, verify that the Oracle client and the database connection configuration (for example, TNSnames.ora) components are installed and configured correctly so as to establish connection to the database via OLEDB.

On the Web server, in the IIS Manager window, under Web Service Extensions, set the Active Server Pages extension to Allow.

Set the Computer Browser service to Start.

Note: This service is required for installation purposes only. If your company's policy is to have this service disabled, contact your system administrator for assistance.

Set the Distributed Transaction Coordinator service to Start. Set the World Wide Web Publishing Service service to Start.

Installing Oblicore Guarantee™ 6.3 Service Release 1 from Scratch 7

Installation Process To install Oblicore Guarantee™ 6.3 Service Release 1: 1. Verify that the Computer Browser service is started.


2. In the local directory to which you downloaded or copied the installation files, double-click OG63SR1.Log_Enabled.bat. The Welcome window opens.

3. Click Next. The Organization Information window appears. 4. Type your organization's name. If your organization name contains special characters (e.g.

&), add the ^ character before each special character (e.g. AT&T should be written as AT^&T).

5. Click Next. The Select Installation Type window appears. 6. Select Typical or Custom and click Next.

If you selected Typical, proceed with Typical Installation on page 7. If you selected Custom, proceed with Custom Installation on page 8.

Typical Installation To perform a typical installation of Oblicore Guarantee™ 6.3 Service Release 1: 1. In the Destination Folder window:

a. Click Browse to select a destination folder and click Next. OR

b. Click Next to use the default destination folder. The Select Features window appears. 2. Select the components you want to install and click Next.

Use the following table and "Appendix A - Typical Installation Windows" on page 29 to help with the installation process. Selected Servers Related Windows

Database Database Creation

Database + Application + Web Logon Information, Database Creation

Application Logon Information, Database Connection

Application + Web Logon Information, Database Connection

Web Logon Information, Log Server Configuration, Database Connection

3. Click Next. The Ready to Install the Application window appears. 4. Review the settings that were made so far. To change any of the previous settings, click

Back. To cancel the installation, click Cancel. Otherwise, click Next. The Updating System window appears and installation begins.

5. When installation finishes, a window appears confirming a successful installation and prompts you to restart the computer (by default, Yes is selected). Click Finish. The system restarts.


Custom Installation To perform a custom installation of Oblicore Guarantee™ 6.3 Service Release 1: 1. In the Destination Folder window:

a. Click Browse to select a destination folder and click Next. OR

b. Click Next to use the default destination folder. The Select Features window appears. 2. Select the components you want to install and click Next.

Use the following table and "Appendix B - Custom Installation Windows" on page 31 to help with the installation process. Selected Servers Related Windows

Database Database Creation

Database + Application + Web Logon Information, Website Configuration, Services Startup Type, Log Server Configuration, Database Creation

Application Logon Information, Services Startup Type, Log Server Configuration, Database Connection

Application + Web Logon Information, Website Configuration, Services Startup Type, Log Server Configuration, Database Connection

Web Logon Information, Website Configuration, Log Server Configuration, Database Connection





Creating a New Database Manually This section describes how to manually create a new database (not from the EXE).

Note: This procedure must be performed prior to installation.

Note: Oblicore highly recommends printing "Appendix D - Oblicore Guarantee™ Environment Checklist" on page 35 prior to creating a new database manually, so as to compare typical values to local environment values.

1. In the local directory to which you downloaded or copied the installation files, go to the Setup DB\InstallDB folder and edit the start_parameter.ini file as described in the following table.

Parameter Description

OBLICORE_ROOT Desired database location. Setup creates a new folder with database name under this folder. For example: c:\Oblicore.

ORACLE_HOME Folder where Oracle Home is located (according to the registry).

DB_NAME Database name. Length of name should be less than or equal to 8 characters.

ORACLE_VERSION Main Oracle version. Supported versions are: 9, 10, and 11.

DB_SIZE Database size. Available options are: SMALL or LARGE (default).

SYS_PASS SYS user password.

OBLICORE_USER Name of schema where Oblicore's database objects are located.

OBLICORE_PASS Schema password.

2. On a Windows-based system, run the Main.bat file located in the Setup DB\InstallDB folder.

3. On a UNIX-based system, run the Main.sh file located in the Setup DB\InstallDB folder. 4. Review the parameters indicated in the pop-up window. 5. Type Y to start the database creation process. 6. At the prompt, click any key to finish the process. 7. Check the log created at the location indicated by the pop-up screen for errors.


From Scratch Post-installation Activities After installation, the following activities must be performed: 1. If Oblicore Guarantee™ 6.3 Service Release 1 was installed on three or more servers, login

to Oblicore Guarantee™ and: a. Click Administration->Preferences->Advanced->Dashboard->Addresses.

b. Click next to the Dashboard Service Url parameter. c. Replace the word localhost with the name of the Application server.

2. If Oblicore Guarantee™ 6.3 Service Release 1 was installed on one server and Oracle 11 is installed, perform the following steps: a. Stop the Oblicore-PSLWriter service. b. From the local directory to which you downloaded or copied the installation files, copy

the files located in \Post_Install\Oracle11 into the <installation directory>\Oblicore\bin.

c. Click Start->Run and type Regsvr32 PSLDebuggerPrj.dll. d. Click OK. e. Click Start->Run and type Regsvr32 CurrentStatusEngineDO.dll. f. Click OK. g. Click Start->Run and type dcomcnfg. h. Click OK. The Component Services window appears. i. Go to Component Services->Computers->My Computer->COM+ Applications-

>Oblicore Engine->Components. j. From the <installation directory>\Oblicore\bin folder, drag and drop the

PSLDebuggerPRJ.dll file into Components. k. Start the Oblicore-PSLWriter service.


3. Verify the services you selected were installed properly as follows: a. Click Start->Run and type services.msc. b. Click OK. The Services window is displayed. c. Use the following table to verify the services were installed properly according to the

components you selected during installation.

Service Name*

Service Description Mandatory Service for:

Service Catalog Modeling

Service Level Calculations

Business Impact Analysis

Adapter Listener

This service is used to communicate with the adapters. It reads the data from the adapters and stores it in Oblicore’s database. This service communicates with the adapters through a TCP/IP socket.

No Yes No

Adapter Deployment

This service is responsible for creating adapters. This service receives requests to create, update or delete adapters from the adapter wizard. The communication with this service is done through a web service interface.

No Yes Yes

Alerts This service receives events from various parts of the system. The service compares the data in those events to the set of Alert Profiles defined in the system. When a certain event matches a certain Alert Profile, this service generates an alert. This service receives the events through a queue in the database.

No Yes Yes

Current Status Engine

This service is responsible for the calculation of the Current Status indicators in the dashboard.

No No Yes

Dashboard This service is responsible for the calculation of the severity of each entity represented in the dashboard.

No No Yes

Log Server This service is responsible for writing log messages from various parts of the system into the database. Each component in Oblicore communicates with this service through a TCP/IP socket whenever it wants to log a message.

Yes Yes Yes

Penalty Writer This service is responsible for calculating penalties. By default penalties are no longer used since their functionality can be achieved by the use of metrics. This service still exists for backwards compatibility reasons.

No No Yes


Service Name*





Psl Writer This service is the main calculation engine of the system. It is responsible for calculating the service level of each metric in each contract in the system. For scalability reasons it is possible to install more than one Psl Writer service on a single machine. In those cases those services will be typically named “Psl Writer N” where N is a number that represents a unique id given to each of those services.

No Yes Yes

Reports Scheduler

This service is responsible for running scheduled reports.

No No Yes

Tasks Host This service is responsible for small maintenance operations that are done by the system asynchronously. It does tasks such as: Changing the status of a

contract when it expires nalyzing raw data to see if there

are missing events Calculating indicators that tell

whether a certain contract is up-to-date so that data can be seen in the system when viewing the contract

Running the “Translation Scripts”

Yes Yes Yes

* All Oblicore Services displayed in the service control panel with “Oblicore –“ prefix.

Chapter 4

Upgrading From a Previous Version of Oblicore Guarantee™ This chapter describes the steps required to upgrade from Oblicore Guarantee™ 4.0 Service Release 2 or higher. The upgrade process includes running the OG63SR1.Log_Enabled.bat file on all Application servers, Web servers and Adapter servers (if exist). The upgrade file recognizes on which server it is run and updates the necessary files.

Important:

• The migration script automatically runs on the Application server that includes the Oblicore Alerts service.

• Upgrading must be performed on the Application server that contains the Oblicore Alerts service first and only afterwards on all other servers.

Prerequisites Prior to upgrading Oblicore Guarantee™ verify that: The installed Oblicore Guarantee™ version is 4.0 Service Release 2 or higher and you are

able to perform basic operations such as logging into Oblicore Guarantee™.

Note: Oblicore Guarantee™ 6.3 Service Release 1 does not contain all fixes included in Oblicore Guarantee™ 6.1 Service Release 1. Contact Oblicore support prior to upgrading from version 6.1 Service Release 1.

All Oblicore folders and files are backed up and a database dump is created prior to the upgrade, so as to enable rollback.

Note: To perform a rollback, you must uninstall Oblicore Guarantee™ 6.3 Service Release 1, install the previous version and import the backed up data.

Your hardware and software conform to Oblicore Guarantee™ 6.3 Service Release 1 system requirements. For more information, see the Oblicore Guarantee™ 6.3 Service Release 1 System Requirements and Platforms document available from the Oblicore Support Center.

Note: Oblicore recommends contacting your DBA to make sure that the selected hardware conforms to your company’s policies and guidelines.

A user that has administration privileges is used for upgrading. If upgrading three or four servers, the Web and Application servers are time synchronized. Oracle OLEDB Provider is installed on the Application and Web servers. For the exact

version, see the Oblicore Guarantee™ 6.3 Service Release 1 System Requirements and Supported Platforms document.

Notes:

• When installing the Oracle OLEDB Provider, make sure to install it to the existing Oracle home.

• For any assistance with the Oracle OLEDB Provider installation, contact the Oblicore support team.


Microsoft .NET Framework 3.5 is installed. The file is located under \Prerequisites folder. Oblicore recommends that you use a domain account instead of a local account during

installation of Oblicore Guarantee™ 6.3 Service Release 1. When using a domain account, the same account should be used for all Oblicore servers.

Any account that will be in use, must be a member of the local administrator group and the necessary details for installation must be known.

Oblicore Guarantee™ is in idle mode by performing the following steps: Stop all Oblicore adapters on all relevant servers. Stop all adapters in the UI. Stop all Oblicore Guarantee™ services.

If you have a distributed system, stop all the relevant services for each server. Stop the web site (but not the WWW service and not the IIS Admin service).

Important: Do not stop the relevant Oracle database service.

If you are upgrading from version 6.0 or lower (including fixes and updates), during the upgrade process, the migration script checks whether a split process was previously performed. If it was not, the script automatically runs the split process. Therefore, Oblicore highly recommends that you read the Split and Partitioning Scripts guide.

Perform the following steps on the Oblicore database. If you do not have SYS privileges have the SYS DBA perform the steps: a. Run the oblicore_privs.sql. The file is supplied with the installation package and is

located under \Prerequisites folder. b. If you are upgrading from a version lower than 5.0, run the cre_tbs_and_grant.sql

script located under the \Prerequisites folder. c. If you are upgrading from a version lower than 6.0 and have not performed a split

process, run the cre_tpsl_data_tbs.sql, cre_temp_tab.sql and cre_tpsl_ind_tbs.sql scripts located under the \Prerequisites folder.

If you are upgrading from version 6.0 or higher (including fixes and updates), on the Web and/or Web Services server verify, in the registry, that the WWWRootFolderLocation string value exists under HKEY_LOCAL_MACHINE\SOFTWARE\Oblicore\Install Data and that the data for this string value contains the folder path for the Oblicore web folder. For example, “C:\Inetpub\wwwroot\Oblicore” (see capture below).

If your topology consists of a server designated as an Application server only, perform the above on this server, verifying that the string value does not exist. If it does, delete it.

In the Init.ora file, verify, and change if not, that the job_queue_processes parameter is set to 2.

The Computer Browser service is set to Start.


The Distributed Transaction Coordinator service is set to Start.

Upgrading From a Previous Version of Oblicore Guarantee™ 15

Upgrading Process To upgrade to Oblicore Guarantee™ 6.3 Service Release 1: 1. Verify that the Computer Browser service is started.


2. In the local directory to which you downloaded or copied the installation files, double-click OG63SR1.Log_Enabled.bat. The Welcome window appears.

3. Click Next. The Database Connection window appears. 4. Select the Oracle client version. The default version is the server default. 5. Type the Oblicore database instance TNS name. 6. Select the Run Migration Script check box, which runs the SQL script that updates the

database directly from the EXE installation file, if running the EXE file for the first time. 7. Click Next. The Logon Information window appears. 8. In User Name, type a user name or browse to select the local user used during the

installation of the current Oblicore Guarantee™ version.

Note: The default user name that appears is the one that was used to log in and start the upgrade process.

9. In Password type the password of the user that is selected in the User Name field. 10. Click the New User Information button to create a new domain user account. For more

information, see Creating a Domain User Account. "Creating a Local User Account" on page 21



13. If the Run Migration Script check box was selected, a window appears. Follow the onscreen instructions. If upgrading from version 6.1 (including fixes and updates) or lower the AdapterLocaleFix Tool is invoked. Follow the onscreen instructions and refer to "Appendix E - AdapterLocaleFix Tool" on page 39 for more information.


Upgrade Post-installation Activities After upgrading, the following activities must be performed: 1. Start the web site. 2. If you are upgrading from a version lower than 6.0 and your database user credentials are

not the Oblicore default values, modify the Registry.xml file located in the <installation directory>\Oblicore\bin folder on each Oblicore server with your user credentials.

3. If the Run Migration Script check box was not checked in the Ready to Install the Application window during installation, the required database changes must be applied on each server as follows: a. Double click on the OG63xMigration.bat file located under the <installation

directory>\Oblicore\Setup\Migration folder. b. Follow the onscreen instructions.


4. Oblicore Guarantee™ 6.3 Service Release 1 utilizes a three-color representation of threshold values instead of a four-color representation that was used in previous versions. If you have used threshold values when setting up reports, no action is necessary. Your system is converted to the three-color representation automatically. If you did not use threshold values when setting up reports, you may want to convert the report generation mechanism so that only three colors are indicated as is in the Dashboard. To migrate the system to three-color representation, go to <installation directory>/Oblicore/Setup/Migration and run the DashboardThresholdsMigration.exe file.

Important: This action is irreversible.

5. If you are using a proxy server to access Oblicore Guarantee™, perform the following steps: a. Clear the cache on the organization’s proxy server. b. In Internet Explorer, clear the cache (delete temporary Internet files).

6. Verify the services you selected were installed properly as follows: a. Click Start->Run and type services.msc. b. Click OK. The Services window is displayed. c. Use the following table to verify the services were installed properly according to the

components you selected during installation.

Service Name*





Adapter Listener

This service is used to communicate with the adapters. It reads the data from the adapters and stores it in Oblicore’s database. This service communicates with the adapters through a TCP/IP socket.

No Yes No

Adapter Deployment

This service is responsible for creating adapters. This service receives requests to create, update or delete adapters from the adapter wizard. The communication with this service is done through a web service interface.

No Yes Yes

Alerts This service receives events from various parts of the system. The service compares the data in those events to the set of Alert Profiles defined in the system. When a certain event matches a certain Alert Profile, this service generates an alert. This service receives the events through a queue in the database.

No Yes Yes

Current Status Engine

This service is responsible for the calculation of the Current Status indicators in the dashboard.

No No Yes

Dashboard This service is responsible for the calculation of the severity of each entity represented in the dashboard.

No No Yes

Upgrading From a Previous Version of Oblicore Guarantee™ 17

Service Name*





Log Server This service is responsible for writing log messages from various parts of the system into the database. Each component in Oblicore communicates with this service through a TCP/IP socket whenever it wants to log a message.

Yes Yes Yes

Penalty Writer This service is responsible for calculating penalties. By default penalties are no longer used since their functionality can be achieved by the use of metrics. This service still exists for backwards compatibility reasons.

No No Yes

Psl Writer This service is the main calculation engine of the system. It is responsible for calculating the service level of each metric in each contract in the system. For scalability reasons it is possible to install more than one Psl Writer service on a single machine. In those cases those services will be typically named “Psl Writer N” where N is a number that represents a unique id given to each of those services.

No Yes Yes

Reports Scheduler

This service is responsible for running scheduled reports.

No No Yes

Tasks Host This service is responsible for small maintenance operations that are done by the system asynchronously. It does tasks such as: Changing the status of a

contract when it expires nalyzing raw data to see if there

are missing events Calculating indicators that tell

whether a certain contract is up-to-date so that data can be seen in the system when viewing the contract

Running the “Translation Scripts”

Yes Yes Yes

* All Oblicore Services displayed in the service control panel with “Oblicore –“ prefix.


Enabling the Oracle Database CURSOR Sharing Feature The Oracle database cursor sharing feature is supported as of Oblicore Guarantee™ 4.0 Service Release 1. Oblicore recommends that users enable this feature on Oracle in order to improve the application performance.

If you are installing from scratch or upgrading from Oblicore Guarantee™ 4.0 Service Release 2 and have enabled this feature, no further action is required.

If you are upgrading from Oblicore Guarantee™ 4.0 Service Release 2 and have not enabled this feature, perform the following steps to enable the feature. To enable the Oracle database cursor sharing feature: 1. After upgrading to Oblicore Guarantee™ 6.3 Service Release 1, and running the migration

SQL script, open the initoblicore.ora file (using any text editor) located in the database folder where the database was installed (by default in \oblicoredb\admin\pfile).

2. Add the following lines at the end of the file: cursor_sharing=SIMILAR _adjust_literal_replacement=true

3. Restart the database.

Updating Adapters Not on Oblicore Server In some systems the adapters are installed on servers other than the Oblicore server. The migration file does not upgrade these adapters. To update adapters that are not on the Oblicore server a manual migration is required. To update adapters installed on servers other than Oblicore:

Copy the following files from the adapter directory of a previously migrated server to the adapter directory of this server: TextFileAdapter.exe SqlAdapter.exe

Important: Make sure to backup all adapter configuration files before starting the migration.

Chapter 5

Client Installation Introduction Oblicore Guarantee™ pages require additional third party applications to be installed on the end user’s browser. These applications can be retrieved from the specific pages or be installed by the client installation kit.

This document describes the installation instructions for installing the Oblicore Guarantee™ 6.3 Service Release 1 client.

Supported Platforms The supported platforms for Oblicore Guarantee™ 6.3 Service Release 1 client are: Microsoft Windows XP (32-bit version) SP1, SP2 and SP3 Microsoft Windows Vista (32-bit version)

Client Components The following table indicates the components that are required by Oblicore Guarantee™ 6.3 Service Release 1 pages and are installed by the Oblicore Guarantee™ 6.3 Service Release 1 client.

Component Name Third Party Application

Used In

Time Slot Editor Applet Catalog->Template Library->Timeslots Templates->View always timeslot

Java Runtime Environment 1.4.2.3 Java Framework->Template Library->Timeslots Templates->View always timeslot

MSXML 4.0 SP2 Module Service Delivery Navigator

Microsoft Office Web Components 2003 MSI Contract->Contract details->All Metrics->Objective statement->Parameters->add Parameter

TeeChart Pro ActiveX Reports->Report Wizard->Generate

Flowchart ActiveX Service Delivery Navigator

Script Editor ActiveX Catalog->Template Library...->Business Logic Templates->Add Business Logic Template

DataSourceAnalyzerAX ActiveX Configuration->Adapters->Add New Text File/SQL Adapter

ActiveQueryBuilderXControls ActiveX Configuration->Adapters->Add New SQL Adapter


Installation Process Oblicore Guarantee™ 6.3 Service Release 1 client should be run on any end-user machine before logging into the Oblicore Guarantee™ website. To install: 1. Make sure that a user that has administration privileges is used for running the installation. 2. Double click on OG63SR1_Client.Log_Enabled.bat. The Welcome window appears. 3. Follow the on-screen steps until installation completes.

Post-installation Activities After installation, the Microsoft Office Web Components 2003 component needs to be installed. To install: 1. In the installation directory where Oblicore Guarantee™ 6.3 Service Release 1 client was

installed (default is \Program Files\Oblicore\Client), double click on owc11.exe. The Welcome window appears.

2. Follow the on-screen steps until installation completes.

Chapter 6

Online Help Installation After installation, the Oblicore Guarantee™ 6.3 Service Release 1 online help must be installed.

Important: The Oblicore Guarantee™ 6.3 Service Release 1 online help must be installed on the Web server.

To install: 1. In the local directory to which you downloaded or copied the installation files, double-click

OG63SR1_Onlinehelp.Log_Enabled.bat. The Welcome window appears. 2. Click Next. The Destination Folder window appears. 3. Click Next. The Updating System window appears and installation begins. 4. When the installation finishes, a window appears confirming a successful installation. Click

Finish.

Chapter 7

Creating a Local User Account When installing Oblicore Guarantee™ 6.3 Service Release 1 from scratch or when upgrading to Oblicore Guarantee™ 6.3 Service Release 1, Oblicore recommends that you use a domain account for each machine on which Oblicore Guarantee™ 6.3 Service Release 1 is installed. If you still need to create a local user account, perform the following steps. To create a local user account: 1. In the Logon Information window, click New User Information. The New User

Information window appears. 2. Type or browse to the server name. 3. In Group, browse to the Administrators group. 4. Type the desired account. Oblicore recommend that you use an account with meaning such

as OblicoreServiceAccount. 5. In Password, type in a password.

Note: The password should meet the company policy.

6. Confirm the password. 7. Click OK.

Chapter 8

Additional Application Servers Installation This chapter describes the required steps to install additional Oblicore Guarantee™ Application servers. Additional Application servers are installed when: Oblicore Guarantee™ services are divided between several servers. Some or all of the adapters are placed on a different server Additional Calculation Engine instances are required on dedicated servers

Important: Prior to the Oblicore Guarantee™ additional Application servers installation, verify that the Oracle client and the database connection configuration (for example, TNSnames.ora) components are installed and configured correctly to establish connection to the database.

Dividing Oblicore Guarantee™ Services This section describes the steps required to divide Oblicore Guarantee™ services on several Application servers. To divide Oblicore Guarantee™ services on several Application servers: 1. Perform a Custom Application server installation. 2. Under the Services feature, clear the components that should not be installed on the current

Application server. The following table describes each component under the Services feature.

Component Description

Adapter Deployment

Adapter Listener Installs Adapter Listener

Alerts Installs Alert service (Note: Alerts can be installed only once)

Dashboard Installs Dashboard service

Log Server Installs Log server service

OLAP Assistant Only valid if organization is using Panorama and would like to use Oblicore reporting to run Panorama reports

Penalty Writer Installs penalty service

PSL Writer Installs one instance of Calculation Engine service

Report Scheduler Installs report scheduler service

Task Host Installs task host service

3. After you install the initial Application server, install additional Application servers using the Custom installation procedure per additional services/features needed.


Placing Adapters on Different Servers This section describes the steps that need to be performed on each server that is installed with adapters. To place adapters: 1. Perform a Custom Web Server installation. 2. In the Select Features window, clear the Website, Services, Administration Tools, and

Database features.

Note: Make sure that one of the Additional Application servers includes the Adapter Listener.

Chapter 9

Uninstalling Oblicore Guarantee™ 6.3 Service Release 1 Important Notice:

Oblicore Guarantee™ 6.3 Service Release 1 cannot be uninstalled unless Oblicore Guarantee™ 6.3 is uninstalled. To uninstall Oblicore Guarantee™ 6.3 Service Release 1, the whole Oblicore Guarantee™ 6.3 application must be uninstalled.

Uninstalling Oblicore Guarantee™ 6.3 Service Release 1 must be performed on all servers according to the installation topology type. To uninstall Oblicore Guarantee™ 6.3 Service Release 1: 1. In Control Panel, double-click Add or Remove Programs. 2. If the installation was from scratch, select Oblicore Guarantee™ and click Remove. 3. Restart the machine. 4. If upgraded form a previous version, select Oblicore Guarantee™ and click Remove. 5. Restart the machine. 6. In Control Panel, double-click Add or Remove Programs. 7. Select the latest Oblicore Guarantee™ service release and click Remove. 8. Restart the machine. 9. Repeat steps 6–8 for all installed Oblicore Guarantee™ service and major releases.

Appendix A

Typical Installation Windows This appendix lists all Typical installation windows and related parameters.

Window Name Parameters Possible Values Remarks

Database Creation Oracle Version DB File Location DB Server Name

Default: server default

Location of DB file Name of DB server

Logon Information User Name Password New User

Information button

Name of user that ran installation

User password See New User

Information row

Default assigned user name is user of account that ran installation. Oblicore recommends changing user and password to a domain account. If you need to create a new local account, see Creating a Domain User Account "Creating a Local User Account" on page 21.

New User Information

Domain or server Group User Name Password Confirm Password

Database Connection Oracle Version Oblicore Database

Instance TNS Name

Type TNS name of the Oblicore Guarantee™ database as it appears in TNSNAMES.ORA file.

Log Server Configuration

Log Server Network Address

Log Server Network Port

Default is localhost Default is 4040

Appendix B

Custom Installation Windows This appendix lists all Custom installation windows and related parameters.

Window Name Parameters Values Remarks

Database Creation Oracle Version 9, 10 or 11 Default: server default

DB File Location Location of database file

A new folder is created under this location with name given in DB Server Name field where all files are installed.

DB Service Name Name of database server

Logon Information User Name Name of user Default: User of account that ran installation. Oblicore recommends changing user and password to a dedicated domain account. If you need to create a new local account, see Creating a New User Account "Creating a Local User Account" on page 21.

Password User password

New User Information button

See New User Information row

New User Information Domain or server Name of local server

Group Administrators

User Name Name of user

Password User password Conforms to company policy.

Confirm Password Confirm password

Services Startup Type Automatic All services are setup to start automatically when system starts up.

Manual Default: All services are setup to start manually when system starts up. Note: Log server service is always set to Automatic.

Database Connection Oracle Version 9, 10 or 11 Default: Server default

Oblicore Database Instance TNS Name

Type TNS name as it appears in TNSNAMES.ORA file.

Log Server Configuration Log Server Network Address

Address where Log server is installed.

Default: localhost

Log Server Network Port Port used by Log server.

Default: 4040

Website Configuration WWWRootfolder Location of WWWRoot folder.

Default: Current folder where website is installed.


Window Name Parameters Values Remarks

SessionDataFolder Location of SessionDatafolder.

Default: Installation directory.

SessionTimeout Time it takes for session to timeout.

Default: 300

Appendix C

Oblicore's Naming Conventions Policy for Database Objects The following table provides a checklist, which specifies Oblicore's naming convention policy. If your database naming convention is different than Oblicore's policy, fill the difference in the appropriate row and consult the Oblicore Support department before starting installation.

Oblicore Naming Convention Customer Naming Convention

Tablespace

TBS_CSL_DATA_TAB_01

TBS_CSL_INDEX_TAB_01

TBS_OBL_DATA_01

TBS_OBL_INDEX_01

TBS_PSL_DATA_TAB_01

TBS_PSL_INDEX_TAB_01

TBS_SLA_DATA_01

TBS_SLA_DATA_02

TBS_SLA_INDEX_01

TBS_SLA_INDEX_02

Oblicore Users

OBLICORE

USRCSL

USRDASH

USREDR

USRMTN

USRPSL

USRRPT

USRSLA

Oblicore Privileges

CONNECT TO OBLICORE

CREATE PROCEDURE TO OBLICORE

CREATE PUBLIC SYNONYM TO OBLICORE

DROP PUBLIC SYNONYM TO OBLICORE

EXECUTE ANY PROCEDURE TO OBLICORE

EXECUTE ON DBMS_SHARED_POOL TO OBLICORE

UNLIMITED TABLESPACE TO OBLICORE

CREATE SESSION TO USRCSL

ROLE_USR_REG_PRIVS TO USRCSL

CREATE SESSION TO USRDASH


Oblicore Naming Convention Customer Naming Convention

ROLE_USR_REG_PRIVS TO USRDASH

CREATE SESSION TO USREDR

ROLE_USR_REG_PRIVS TO USREDR

CREATE SESSION TO USRMTN

ROLE_USR_REG_PRIVS TO USRMTN

CREATE SESSION TO USRPSL

ROLE_USR_REG_PRIVS TO USRPSL

CREATE SESSION TO USRRPT

ROLE_USR_REG_PRIVS TO USRRPT

CREATE SESSION TO USRSLA

ROLE_USR_REG_PRIVS TO USRSLA

Oblicore Role

ROLE_USR_REG_PRIVS

Appendix D

Oblicore Guarantee™ Environment Checklist The following table provides a list, which specifies environment parameters that might affect Oblicore Guarantee™ 6.3 Service Release 1 functionality.

Oblicore recommends comparing the typical values to the local environment before starting installation. If some of the values are different than the recommended ones, fill the difference in the appropriate row and consult the Oblicore Support department before starting installation.

Parameter Typical Value Customer Value

General

Number of Machines Three Servers

Name of Oblicore Application User OblicoreSrv

Name of Oblicore Database Users OBLICORE USRCSL USRDASH USREDR USRMTN USRPSL USRRPT USRSLA

Application Server

Number of Application Servers 1

Services installed on each Application Server

Adapter deployment Adapter listener Alerts Dashboard Current status Log Server Penalty Writer PSL Engine Report Scheduler Task Host

Application Server IP

Application Server Processor Dual CPU, At least 2.8 GHz

Application Server Memory 2 GB RAM

Total Hard Disk Space

Available Disk Space

Application Operating System and Service Pack

Windows Server 2003 (Standard/Enterprise) SP1 or SP2

Application Language Setting English



Application Locale and Regional Settings

US

Application Time Zone

Oracle Client Version According to Oracle database version

Database TNS Name Oblicore

Web Server

Web Server IP

Web Server Processor Dual CPU, At least 2.8 GHz

Web Server Memory 1 GB RAM


Available Disk Space

Web Operating System Windows Server 2003 (Standard/Enterprise) SP1 or SP2

Web Language Setting English

Web Locale US

Web Time zone

Oracle Client Version According to the Oracle database version

Web Server Version IIS 6 – Windows 2003

Windows Components – Through add/remove windows components->Application Server-> Details->verify installed components

ASP .Net Enable network COM+ access

.NET Framework 3.5

Database TNS Name Oblicore

Is the environment configured to work in secured mode (https)

Is the environment configured to work with reverse proxy

Database Server

Database Server IP

Database Server Operating system Oracle 9i, 10 or 11.

Database Server Processor Dual CPUs, At least 2.8 GHz

Database Server Memory 2 GB RAM


Database Service Pack Oracle 9i Enterprise Edition running on any Oracle certified operating system. For more information, see the System Requirements and Supported Platforms document.

Database Language Setting English

Database Server Locale

Database Time zone

Oblicore Guarantee™ Environment Checklist 37


NLS Lang AMERICAN_AMERICA.WE8MSWIN1252

Oracle Version 9i

Oracle Client Version According to Oracle DB Version

Client Stations

Microsoft Office Version 2003 or 2007

Internet Explorer Client Version (1) Internet Explorer 6.0 (2) Verify client browser setting (internet options -> Settings) is set to "Automatic" and NOT to "every time you start Internet Explorer".

Adapters

Number of machines installed with adapters

Servers IP

Adapters Types (SQL, File)

Data sources

Used Ports

Access Options To External Sources

Oblicore FTP

Customer FTP

Internet Explorer

Dump Can be Sent to Oblicore

Remote Access

Appendix E

AdapterLocaleFix Tool This tool assists in the migration of time zone information from unmanaged adapter configuration files to the Oblicore database.

The purpose of this tool is to assist in ensuring that all unmanaged adapters have their correct time zone assigned, after referencing the time zone information in their configuration file.

This tool: Affects only unmanaged adapters. Goes through all unmanaged adapters with unassigned time zones, and attempts to make a

recommendation if there is a suitable time zone for which it should be assigned to. Compares the time zone information in the unmanaged adapter configuration file to the

new/assigned time zone and reports on how closely they match. Is aware of the daylight saving periods (both in the configuration file and in the Oblicore

database).

Note: Unmanaged adapters with existing time zones assigned that are not a good match to the configuration file are shown with a warning, but no recommendation is given for a better time zone assignment.

If the time zone data within the Oblicore database needs to be updated, update it within the Oblicore website, and thereafter click on Refresh Time Zone List.

In order to successfully save the details captured on the form, every adapter listed must have a time zone assigned (i.e. no error icons shown).


The possible values of two of the columns in the tool are: Source of new time zone

Manually updated Current value Recommendation None

Comparison of configuration file to new time zone No configuration file Time Zones differ Investigation required Time Zones match, but daylight savings periods differ Times Zones match. Daylight savings periods similar Good match

In certain cases, the Status bar on the bottom on the form may contain additional information about the current adapter time zone.

Appendix F

High Availability Installation Introduction This appendix describes the installation instructions for installing Oblicore Guarantee™ on high availability environments.

Target Audience This appendix is intended for personnel who are required to install or upgrade Oblicore Guarantee™ on high availability environments.

Using this Appendix This appendix should be used when installing the Oblicore Guarantee™ Application, Adapter and Web components on a high availability environment.

Additional Help For additional help installing Oblicore Guarantee™ contact the Oblicore Support team:

By Phone:

Toll free number in Germany: +49 (0) 800 189 0489

Toll free number in France: +33 (0) 800 906 553

Toll free number in the UK: +44 (0) 800 404 9235

Toll free number in the US: +1 877 534 6770

Toll free number in Australia: +1 800 193 212

International number: +972 9 762 7000

By email:

For Asia-Pacific: [email protected]

For Europe, Middle East and Africa: [email protected]

For North America: [email protected]

Installation Platform For Oblicore Guarantee™ to work in a high availability environment, a Windows 2003 SR1 platform must be used. For more information, see the Oblicore Guarantee™ System Requirements and Supported Platforms document.





Abbreviations OBC-APP/n

This document references names for Oblicore Application cluster nodes. For example, OBC-APP/1 refers to Oblicore Guarantee™ Application first cluster node name.

OBC-ADP/n This document references names for Oblicore Adapter cluster nodes. For example OBC-ADP/1 refers to Oblicore Guarantee™ Adapter first cluster node name.

OBC-WEB/n This document references names for Oblicore NLB nodes. For example OBCWEB/1 refers to Oblicore Guarantee™ first NLB node name.

OG Oblicore Guarantee™

Overview Installing Oblicore Guarantee™ in a high availability environment is based on Windows Cluster Technology and Windows Network Load Balance (NLB) Technology. Installation includes the Oblicore Web, Application and Adapter components.

Note: The Oblicore Database component is not part of the installation.

Installing Oblicore Guarantee™ in a high availability environment is implemented over Oblicore Guarantee™ distributed environments of three and four-tier topologies as shown in the following table:

Topology Description Installation Rule

Three-tier Application and Adapter components - Clustered over two or more physical servers

Web component - NLB over two or more physical servers

Database component (not included in the cluster)

1. Run the Oblicore Guarantee™ installation and install Oblicore Application and Adapter components on every physical server in the cluster.

2. Run the Oblicore Guarantee™ installation and install Oblicore Web component on every physical server in the NLB.

Four-tier Application component - Clustered over two or more physical servers

Adapter component - Clustered over two or more physical servers

Web component- NLB over two or more physical servers

Database server (not included in the cluster)

1. Run the Oblicore Guarantee™ installation and install Oblicore Application component on every physical server in the cluster

2. Run the Oblicore Guarantee™ installation and install Oblicore Adapter component on every physical server in the cluster

3. Run the Oblicore Guarantee™ installation and install Oblicore Web component on every physical server in the NLB

Common Files For Oblicore Guarantee™ to work properly, common files are required to store the Oblicore application data. These common files are stored in the clustered shared storage (Quorum) disk. These common files are used exclusively by the active cluster node.

High Availability Installation 43

Load Balancing The active cluster node and standby cluster node are used simultaneously to split the load of running the Oblicore components. The following diagram illustrates a typical four-tier Oblicore cluster solution with load balance:

Installing Windows Clusters This section provides instructions for installing Windows clusters. These servers host the Oblicore Adapter (OBC-ADP/n) and Application (OBC-APP/n) components. To install windows clusters: 1. Verify Cluster Prerequisites as follows (verification of the cluster prerequisites is required

on OBC-APP/1 and on OBC-ADP/1): a. Shared storage is of minimum size 1 GB for cluster operation. b. Public and private network interfaces configuration settings. c. Network and name resolution. d. Domain membership. e. Create a cluster user account. The cluster service requires a domain user who is a

member of the Local Administrators group on each node under which the Cluster service can run. Because setup requires a user name and password, this user account must be created before configuring the Cluster service. This user account should be dedicated to running the Cluster service and should not belong to an individual.


2. Install the cluster service on the first node of each cluster as follows (installation of the cluster service on the first node of each cluster is required on OBC-APP/1 and on OBC-ADP/1): a. Click Start->All Programs->Administrative Tools->Cluster Administrator. The

Open Connection to Cluster dialog box opens. b. In Action, select Create new cluster from the drop-down list. c. Click OK. The New Server Cluster Wizard window opens. d. Click Next. The Cluster Name and Domain window opens. e. Select a domain in which the cluster is to be created from the drop-down list. f. Type a unique NetBIOS name for the cluster of up to 15 characters.

Note: Adherence to DNS naming rules is recommended.

g. Click Next. The Select Computer window opens. If you are logged on locally with an account that is not a Domain User with Local Administrator privileges, the wizard will prompt you to specify an account. This is not the account the Cluster service will use when starting.

h. In Computer name, type or Browse to the name of the server that is going to be used as the first node to create the cluster. This should be done because it is possible to configure clusters remotely.

i. Click Advanced to set the analyze mode. The Advanced Configuration Options window opens.

j. Select Advanced (minimum) Configuration and click OK. k. Click Next. The Analyzing Configuration window is displayed and the wizard

performs an analysis of the cluster configuration. l. Click Next. The IP Address window opens. m. Type the unique cluster IP address and click Next. The Cluster Service Account

window opens. n. Type the user name and password for the domain account under which the cluster

service will be run. o. Select the domain from the drop-down list and click Next. The Proposed Cluster

Configuration window opens. p. Click Quorum and select the resource or resource type that you would like to use for

the quorum resource. q. Click OK. r. Click Next. The cluster creation process begins. s. Review any warnings or errors encountered during the cluster creation process and

click Next. t. Click Finish to complete the installation. u. Validate the cluster installation as follows:

Click Start->All Programs->Administrative Tools->Cluster Administrator. The Cluster Administrator console is displayed.

Click File and select the cluster. Verify that the State column of all resources indicates Online.


3. Install the cluster service on all other nodes as follows (installation of the cluster service on all other nodes is required on OBC-APP/n>1 and on OBC-ADP/n>1):

Note: Installing the cluster service on all other nodes requires less time than on the first node because setup configures the cluster service network settings on the other nodes based on the configuration of the first node. You can also add multiple nodes to the cluster at the same time.

Note: For this step, leave Node1 and all shared disks turned on. Then turn on Node2. The cluster service will control access to the shared disks at this point to eliminate any chance of corrupting the volume.

a. Click Start->All Programs->Administrative Tools->Cluster Administrator. The Cluster Administrator console opens.

b. Click File and select a cluster. c. Click File->New->Node. The Add Nodes Wizard window opens. d. Click Next. the Select Computers window opens.

If you are not logged on with appropriate credentials, you will be asked to specify a domain account that has administrative rights over all nodes in the cluster.

e. Enter the name of the computer you want to add to the cluster and click Add. f. Click Advanced to set the analyze mode. The Advanced Configuration Options

window opens. g. Select Advanced (minimum) Configuration and click OK. h. Click Next. The Analyzing Configuration window opens, and the wizard performs an

analysis of the cluster configuration. i. Click Next. The Cluster Service Account window opens. j. Type the password for the account used to start the cluster service and click Next. The

Proposed Cluster Configuration window opens. k. Review any warnings or errors encountered during cluster creation and click Next. l. Click Finish to complete the installation.

4. Install Network DTC access as follows (on each of the cluster nodes OBC-ADP/n and OBC-APP/n): a. In Control Panel, double-click Add or Remove Programs. b. Click Add/Remove Windows Components. c. Select Application Server and click Details. d. Check the Enable network DTC access check box and click OK. e. Click Next. The component is installed. f. Click Finish. g. Stop and restart the Distributed Transaction Coordinator service.


5. Configure the Cluster Resources and Groups as follows: a. Install MSTDC Service on the cluster using the CreateMTDCResourceOnCluster.bat

script (supplied with the package). Before invoking the script open the script in Edit mode and validate the correct variable setting in the script header. Run the script within one of the Oblicore Guarantee™ application cluster nodes. For more information, see http://support.microsoft.com/default.aspx?scid=kb;en-us;301600 http://support.microsoft.com/default.aspx?scid=kb;en-us;301600.

b. Create a file share resource using the CreateFileShareResourceOnCluster.bat script (supplied with this document). Before invoking the script open the script in Edit mode and validate the correct variable setting in the script header. Run the script within each of the Oblicore Guarantee™ application cluster nodes. For more information, see http://support.microsoft.com/?kbid=224967 http://support.microsoft.com/?kbid=224967.

Note: The shared folder user permissions setting is explained in the Oblicore Software Configuration on page 50 section.

For additional references, see: Microsoft Cluster Service Installation Resources

http://support.microsoft.com/?id=259267 Quorum Drive Configuration Information

http://support.microsoft.com/?id=280345 Recommended Private "Heartbeat" Configuration on Cluster Server

http://support.microsoft.com/?id=258750 Network failure detection and recovery in a two-node Windows Server 2000 cluster

http://support.microsoft.com/?id=242600 How to Change the Quorum Disk Designation

http://support.microsoft.com/?id=280353 Microsoft Windows Clustering: Storage Area Networks

http://www.microsoft.com/windows.netserver/techinfo/overview/san.mspx Geographically Dispersed Clusters in Windows Server 2003

http://www.microsoft.com/windows.netserver/techinfo/overview/clustergeo.mspx Server Clusters: Network Configuration Best Practices for Windows 2000 and Windows

Server 2003 http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/clstntbp.mspx http://www.microsoft.com/technet/prodtechnol/virtualserver/deploy/cvs2005.mspx http://support.microsoft.com/default.aspx?scid=kb;en-us;197047&sd=tech

http://support.microsoft.com/default.aspx?scid=kb;en-us;301600�

http://support.microsoft.com/?kbid=224967�

http://support.microsoft.com/?id=259267�





http://www.microsoft.com/windows.netserver/techinfo/overview/san.mspx�

http://www.microsoft.com/windows.netserver/techinfo/overview/clustergeo.mspx�

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/clstntbp.mspx�

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/clstntbp.mspx�

http://www.microsoft.com/technet/prodtechnol/virtualserver/deploy/cvs2005.mspx�

http://support.microsoft.com/default.aspx?scid=kb;en-us;197047&sd=tech�


Installing Windows Network Load Balance (NLB) This section provides information for installing Windows NLB servers. These servers host the Oblicore Web component (OBC-WEB/n). To install windows NLB servers: 1. Click Start->All Programs->Administrative Tools->Network Load Balancing

Manager. The Network Load Balancing Manager console appears. There are no NLB arrays configured by default. You will need to create an NLB array that allows all of the Oblicore Web servers to listen on a single IP address on the external interface.

2. Click Cluster->New. The Cluster Parameters window opens. 3. Fill in the information as follows:

IP address - Dedicated IP address for the NLB. This is the virtual IP address used by all of the members of the NLB array. The Network Load Balancing Manager application automatically binds this address to the external interface of all the array members

Subnet mask - This is the subnet mask for the virtual IP address Full Internet name - DNS name for the Web GUI. This is the Fully Qualified Domain

Name used to access the cluster IP address for command line remote administration. Enter a name here if you choose to allow command line remote administration. This name must also be entered into the public DNS.

Cluster operation mode - The Windows Server 2003 NLB service can operate in either Unicast or Mulicast mode. Select Mulicast mode unless you have Cisco routers or switches on the same network segment as the external interface and those routers or switches do not support mapping unicast IP addresses to multicast MAC addresses. For more information about NLB, unicast and multicast modes, see the Windows Server 2003 Help.

4. Click Next. The Cluster IP Addresses window opens. 5. Add more cluster IP addresses if necessary and/or click Next. The Port Rules window

opens displaying a default rule. 6. Click Add to add more port rules as necessary or click Edit to create customized port rules

that determine how connections are load balanced across all the servers in the array. The Add/Edit Port Rule window opens.


7. Fill in the information as follows: Cluster IP address - This entry determines what IP address this rule applies to. The

default port rule applies to all addresses in the NLB array. Port range - This entry determines what inbound ports the rule applies to. The default

port rule applies to all inbound ports. Protocols - The rule can apply to TCP, UDP or Both. The default port rule applies to

both TCP and UDP protocols.

Note: The Windows Server 2003 NLB port rules can only be applied to TCP and UDP protocols. Port rules cannot be applied to other protocols such as ICMP.

Filtering mode - Select from: Multiple host

Specifies whether multiple hosts in the cluster handle network traffic for the associated port rule. The default port rule applies to all hosts in the array and the Affinity setting is set to Single.

Single host Specifies that network traffic for the associated port rule be handled by a single host in the cluster according to the specified handling priority. This filtering mode provides port specific fault tolerance for the handling of network traffic.

Disable this port range Specifies whether all network traffic for the associated port rule will be blocked.

8. Click OK. 9. Click Next. The Connect window opens. 10. Type the name of the machine you are running the Network Load Balancing Manager

application on and click Connect. A list of interfaces on this machine is shown in the Interface available for configuring a new cluster list.

11. Select the external interface of the Web Server member and click Next. The Host Parameters window opens.

12. Fill in the information as follows: Priority - Specifies a unique ID for each host. Start from 1 and increase for each node. IP address - Physical node IP address. This is the IP address on the external interface

of the NLB array member for traffic not associated with the cluster (for example, Telnet access to a specific host within the cluster). Type the IP address in standard Internet dotted notation (for example, w.x.y.z). This IP address is used to individually address each host in the cluster and hence should be unique for each host.

Subnet mask - This is for the subnet mask for the IP address specified. Type the mask in standard Internet dotted notation (for example, 255.255.255.0).

Default state - Specifies the default host state of the Network Load Balancing cluster when Windows is started. Select Started if you want the host to immediately join the cluster when Windows is started. Select Stopped if you want this host to start without joining the cluster. Select Suspended if you want this host to start without joining the cluster and instead enter a suspended state.

Retain suspended state after computer restarts - Specifies whether the host will remain suspended when Windows is restarted when the host was suspended prior to shutting down.

13. Click Finish. The details of the NLB array configuration are shown in the log entry pane on the bottom of the console window.

14. Add other machines to the array by right clicking on the name of the array in the left pane of the Network Load Balancing Manager console and selecting Add Host to Cluster. The Connect window opens.

15. Repeat steps 10 to 13.


16. Double-click the log entry with the description Update 2 succeeded [double-click for details…]. The log entry provides verbose details associated with that entry.

17. Click OK and close the Network Load Balancing Manager console. 18. Register the DNS name (4.c) of the NLB in the DNS servers.

For additional references, see: http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-

us/Default.asp?url=/resources/documentation/windows/2000/server/reskit/en-us/distrib/dsdc_cls_ynnk.asp

http://www.isaserver.org/tutorials/basicnlbpart1.html http://www.isaserver.org/articles/basicnlbpart2.html http://www.isaserver.org/tutorials/nlbpart3.html

Installing Oblicore Software on the Clusters and NLB Nodes Installing the Oblicore software in a clustered or NLB environment is similar to a standard Oblicore installation. Read this section prior to installing Oblicore Guarantee™ software. For more information on how to install Oblicore Guarantee™, see Installing Oblicore Guarantee™ "Installing Oblicore Guarantee™ 6.3 Service Release 1 from Scratch" on page 5.

Note: The cluster and NLB installations must be done prior to the Oblicore software installations.

To install the oblicore software in a clustered or NLB environment: 1. Install Oblicore Adapter component on all Adapter cluster nodes. 2. Install Oblicore Application component (services) on all Application cluster nodes. 3. Install Oblicore Web component on all NLB cluster nodes. The Services startup type

window opens. 4. Set the services activation type upon startup to Manual.

Note: Oblicore services are controlled by the Cluster service and therefore must be configured to Manual upon startup.

Important: Change Oblicore Log Sever startup settings to Manual after installation is completed. This service is always set to start automatically upon startup for all activation type modes.

5. Click Next. The Log Server Configuration window opens. 6. Set the log server virtual network name given by the Create - ADV Mode.bat cluster

configuration scripts (supplied with the package) in the LogSNetworkName parameter. The default log server network name is OBNLOGS. Before invoking the script, open the script in Edit mode and validate the correct variable setting in the script header. Run the script within one of the Oblicore Guarantee™ application cluster nodes.

Important: Verify that the port specified is open and not being used by another application. Use the log server network virtual name that is set during the cluster configuration. Do not use localhost.

http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/windows/2000/server/reskit/en-us/distrib/dsdc_cls_ynnk.asp�



http://www.isaserver.org/tutorials/basicnlbpart1.html�

http://www.isaserver.org/articles/basicnlbpart2.html�

http://www.isaserver.org/tutorials/nlbpart3.html�


Oblicore Software Configuration Oblicore Guarantee™ Web components require access to system folders and files. These folders and files must conform to the Oblicore Guarantee™ structure. Since the NLB does not have a common file system it must use the Application cluster shared storage (Quorum) disk. In addition, access to the common file system is required. To create the web storage: 1. Create the Web folders and copy the folder (with the files) by using the "Create Web Shares

on App.bat" script (supplied with the package). Before invoking the script, open the script in Edit mode and validate the correct variable setting in the script header. Run the script within one of the Oblicore Guarantee™ Web NLB nodes. -OR- Create the Web folders on the Application cluster quorum disk shared folder (OBCAPP\ClusFileShare\Oblicore) using the structure below:

Validate that the following files are included in the folders: ...\Oblicore\Export\Types folder should include Export3.0.xml file. …\Oblicore\Packages\conf folder should include conf.xml file. …\Oblicore\Booklet Templates folder should include BookletTemplate.rtf file. …\ Oblicore\Export Templates folder should include SLATemplate.rtf file.

2. Update the Web storage paths in the t_system_configurations table by running the sqlplus oblicore/oblicore@oblicore@db_cluster_setting.sql commands (supplied with the package). -OR- Execute the following updates commands: Update t_system_configurations set

sys_config_value=’\\obcapp\ClusFileShare\Oblicore\Booklet Templates\’ where sys_config_id=359

Update t_system_configurations set sys_config_value = ‘\\obcapp\ClusFileShare\Oblicore\Export Templates\SLATemplate.rtf’ where sys_config_id=227

Update t_system_configurations set sys_config_value =’\\obcapp\ClusFileShare\Oblicore\Packages\’ where sys_config_id=512

Update t_system_configurations set sys_config_value = ‘\\obcapp\ClusFileShare\Oblicore\Packages\Conf\’ where sys_config_id=514

Update t_system_configurations set sys_config_value = ‘\\obcapp\ClusFileShare\Oblicore\Packages\Lib\’ where sys_config_id=513

Update t_system_configurations set sys_config_value = ‘\\obcapp\ClusFileShare\Oblicore\Packages\Lib\Log\’ where sys_config_id=515

Update t_system_configurations set sys_config_value = ‘\\obcapp\ClusFileShare\Oblicore\export\’ where sys_config_id=241

Update t_system_configurations set sys_config_value = 'OBC-WEB' where sys_config_id=362


To set permissions: 1. Create a new domain user on the domain: username – OblicoreSrv 2. Add the new user DOMAIN\OblicoreSrv to the local administrators on each of the Web

and Application cluster nodes. 3. Create a new user on the domain: username – OblicoreIISA 4. Add the new user DOMAIN\OblicoreIISA to the local administrators on each of the Web

cluster nodes. 5. Open the Cluster Administrator. 6. Connect to the OBC-APP cluster. 7. Drill-down to the Resources cluster, Oblicore – FileShare resource. 8. In the Parameters tab, click Permissions and give full control permission to

Domain\OblicoreSrv and to Domain\OblicoreIISA users. 9. Make sure that both new users have access to the shared folder on the NTFS level. This

should be done once on one of the application servers.

On the web NLB: 1. Change the anonymous user of the IIS to DOMAIN\OblicoreIISA.

a. Click Start->All Programs->Administrative Tools->Computer Management. The Computer Management console opens.

b. Under Services and Applications->Internet Information Services->Web Sites right-click Oblicore Guarantee and select Properties. The Oblicore Guarantee™ Properties window opens.

c. Click the Directory Security tab. d. In Authentication and Access Control, click Edit. The Authentication Methods window

opens. e. Check the Enable anonymous access check box. f. In User Name type Domain\OblicoreIISA. g. In Password, type the Domain\OblicoreIISA password. h. Click OK twice.

2. Change the application pool identity to DOMAIN\OblicoreIISA on the Oblicore site application pool (by default it is the DefaultAppPool). a. Click Start->All Programs->Administrative Tools->Computer Management. The

Computer Management console opens. b. Under Services and Applications->Internet Information Services->Application

Pools right-click DefaultAppPool and select Properties. The DefaultAppPool Properties window opens.

c. Click the Identity tab. d. Select Configurable.

In User name type Domain\OblicoreIISA. In Password, type the Domain\OblicoreIISA password.

a. Click OK. 3. Add the Domain\OblicoreIISA user to the IIS_WPG group.


b. Under Local Users and Groups->Groups right-click IIS_WPG and select Properties. The IIS_WPG Properties window opens.

c. Click Add. The Select Users, Computers, or Groups dialog box opens. d. In Enter the object names to select, type Domain\OblicoreIISA. e. Click OK twice.

4. Reset the IIS. 5. Repeat steps 1 to 4 for all NLB nodes.


6. Change the local OblicoreSrv “run as” user of Oblicore Com+ Engine to DOMAIN\OblicoreSrv. a. Click Start->All Programs->Administrative Tools->Component Services. The

Component Services console opens. b. Under Component Services->Computers->My Computer->COM+ Applications

right-click Oblicore Engine and select Properties. The Oblicore Engine Properties window opens.

c. Click the Identity tab. d. Select This user.

In User type Domain\OblicoreIISA. In Password, type the Domain\OblicoreIISA password. In Confirm Password, retype the Domain\OblicoreIISA password.

e. Click OK. 7. Shutdown the COM + Oblicore Engine application.

a. Click Start->All Programs->Administrative Tools->Component Services. The Component Services console opens.

b. Under Component Services->Computers->My Computer->COM+ Applications right-click Oblicore Engine and select Shutdown.

8. Repeat steps 6 and 7 for all NLB nodes.

On the adapter cluster:

Configure Cluster Resources and Cluster Groups using the CreateOblicoreADPGroup.bat setup script (supplied with the package).

Before invoking the script, open the script in Edit mode and validate the correct variable setting in the script header. Run the script within one of the Oblicore Guarantee™ adapter cluster nodes.

On the application cluster: 1. Change the OblicoreSrv user in the Oblicore services to DOMAIN\OblicoreSrv.


b. Under Services and Applications->Services right-click Oblicore - <service name> and select Properties. The Oblicore - <service name> Properties window opens.

c. Click the Log On tab. d. Select This account and type Domain\OblicoreSrv.

In Password, type the Domain\OblicoreSrv password. In Confirm Password, retype the Domain\OblicoreSrv password.

e. Click OK. 2. Verify all Oblicore services are set to manual upon restart including Oblicore Log Service. 3. Repeat steps 1 and 2 for all Application cluster nodes. 4. Configure cluster resources and cluster groups using the

CreateOblicoreResourcesOnCluster - ADV Mode.bat scripts (supplied with the package). Before invoking the script, open the script in Edit mode and validate the correct variable setting in the script header. Run the script within one of the Oblicore Guarantee™ application cluster nodes.


Adapter Manager Configuration The Adapter cluster Quorum disk shared folder is used to store the following common adapter files: Adapter data source files Control files XML configuration files

The common adapter files are used mutually exclusive by the adapter programs of the active cluster nodes and standby cluster nodes. 1. Click Start->All Programs->Oblicore->Oblicore Adapter Manager. The Adapter

Manager console opens. 2. Click File->Add Adapter. The Oblicore Adapter Install Wizard window opens. 3. Follow the instructions in the Oblicore Adapter Install Wizard to create the new adapter. 4. Specify the Adapter configuration file and set the path to point to the cluster Quorum disk

shared folder (created previously by the cluster installation script). Set the Adapter log file to the location.

5. Follow the Wizard instructions to complete the configuration. 6. Repeat steps 1 to 4 for each of the ADP cluster nodes.

Adapter XML File Configuration The Oblicore adapters’ connections mode can set to be adapter or server initiator. The required setting depends on the organization security policy. To set to adapter initiator mode: 1. Locate the adapter XML file configuration in the cluster Quorum disk shared folder. 2. Open the adapter XML file in edit mode. 3. In the XML General node, set the attributes of ConnectionInitiator and Adapter as shown in

the example below. When the OBNADPL is the default listener service cluster network name. <General …. ConnectionInitiator=”adapter” Address=”OBNADPL” …. </General>

4. Close and save the Adapter XML file configurations settings.

To set to server initiator mode: 1. Locate the adapter XML file configuration at the cluster shared drive and folder. 2. Open the adapter XML file in Edit mode. 3. In the XML General node set the adapter working folder to point to the cluster shared drive

and folders by setting the WorkingDirectoryName to Q:\ClusterFS\oblicore\adapters\[adapter name].

4. Close and save the Adapter xml file configurations settings.

Adapter Details UI Page In the adapter details page (Oblicore UI pages->Resources->Adapters), set the network address to be the Adapter group virtual network name in case you set the adapter listener to act as the initiator (Initiator = Server)


Adapter Data Source Files Location The adapter data source files should be located on the Quorum disk shared folder only in order the adapter programs running on the cluster nodes to mutually handle the data source information. The Quorum disk shared folder is accessible to any of the adapter programs running on the cluster nodes. To schedule the adapter program: 1. Use Window scheduler or any other scheduler utility to coordinate the adapter program

execution time and granularity. As the scheduled program use the pre-adapter utility and not the adapter program itself. The pre-adapter script (Preadapter.vbs) checks the adapter program execution node cluster status. Only in case the node is the active node the pre adapter wrapper invokes the adapter program.

2. Before using the pre-adapter script, set the following parameters within the pre-adapter script (Preadapter.vbs): ActionScript - Adapter program link name and path ClusterName - Adapter cluster virtual network name ADPGroupName - Adapter group name

Balance Oblicore Services and Adapter Programs between the Cluster Nodes Balance the Oblicore services and Adapters programs load between the Application and Adapter clusters nodes by setting the clusters group failbacks and preferred owners. To set the application cluster group failback policy: 1. Click Start->All Programs->Administrative Tools->Cluster Administrator. The

Cluster Administrator console opens. 2. Click File and select a cluster. 3. Under <cluster>->Groups right-click an Oblicore - <group name> and select Properties.

The Oblicore - <group name> Properties window opens. 4. Click the Failback tab. 5. Select Allow failback. 6. Select Failback between and set to be between 21 to 22 hours. 7. Click Apply. 8. Click OK. 9. Repeat steps 3 to 8 for every Oblicore cluster group.

To set the application cluster group preferred owner: 1. Refer to the table below to balance the preferred owner.

Oblicore Services Preferred Owners

Application Node A Application Node B

Oblicore – Log Server Oblicore – Adapters Listener

Oblicore – Alerts Oblicore – Psl Writer

Oblicore – Task Host Oblicore – Database Maintenance

Oblicore – Dashboard Oblicore – Penalty Writer

Oblicore – Psl Writer1 Oblicore – Reports Scheduler

2. Click Start->All Programs->Administrative Tools->Cluster Administrator. The Cluster Administrator console opens.

3. Click File and select a cluster.


4. Under <cluster>->Groups right-click an Oblicore - <group name> and select Properties. The Oblicore - <group name> Properties window opens.

5. Click the General tab. 6. In Preferred Owners, click Modify. The Modify Preferred Owners window opens. 7. Select nodes from the Available nodes side and move to the Preferred owners side. 8. Click OK. 9. Click Apply. 10. Click OK. 11. Repeat steps 4 to 10 for every Oblicore cluster group. 12. Distribute the Oblicore cluster groups. Refer to the table above to balance the cluster groups. 13. Move the cluster groups to the configured preferred nodes.

a. Click Start->All Programs->Administrative Tools->Cluster Administrator. The Cluster Administrator console opens.

b. Click File and select a cluster. c. Under <cluster>->Groups right-click an Oblicore - <group name> and select Move

Group.

Upgrading from a Previous Version of Oblicore Guarantee™ Upgrading from a previous version of Oblicore Guarantee™ is performed on each server (Application, Web and Adapter). To upgrade the application server: 1. Connect to the first Application cluster node via Remote Desktop. 2. Open the Cluster Administrator program. 3. In Action, select Open connection to cluster. 4. In Cluster or server name, select the Application cluster you want to connect to. 5. Click OK. 6. Check that the first Application cluster node is the owner of all Oblicore services, on

Cluster Group and on Shared folders. 7. Stop all Oblicore services by right clicking on each service and selecting Take Offline. 8. Right-click on Shared folders and select Take Offline. 9. Make sure that Cluster Group is Online and the first Application cluster node is the owner. 10. Run the Oblicore Guarantee™ installation. 11. Restart the first Application cluster node machine. 12. Repeat steps 2 to10 making sure that the second Application cluster node is the owner. 13. Connect to the first Application cluster node via Remote Desktop. 14. Open the Cluster Administrator program. 15. Change the owner of all Oblicore services, on Cluster Group and on Shared folders to be

the first Application cluster node. 16. Leave all services and the Shared folders group Offline. To upgrade the web server: 1. Connect to the first Web cluster node via Remote Desktop. 2. Run the Oblicore Guarantee™ installation. 3. Restart the first Web cluster node machine. 4. Connect to the second Web cluster node via Remote Desktop. 5. Run the Oblicore Guarantee™ installation. 6. Restart the second Web cluster node machine.


To upgrade the adapter server: 1. Connect to the first Adapter cluster node via Remote Desktop. 2. Open the Cluster Administrator program. 3. In Action, select Open connection to cluster. 4. In Cluster or server name, select the Application cluster you want to connect to. 5. Click OK. 6. Check that the first Adapter cluster node is the owner of all Oblicore services, on Cluster

Group and on Shared folders. 7. Check that Cluster Group and Shared folders are Online. 8. Run the Oblicore Guarantee™ installation. 9. Restart the first Adapter cluster node machine. 10. Connect to the second Adapter cluster node via Remote Desktop. 11. Run the Oblicore Guarantee™ installation. 12. Restart the second Adapter cluster node machine. 13. Connect to the first Adapter cluster node via Remote Desktop. 14. Change the owner of all Oblicore services, on Cluster Group and on Shared folders to be

the first Adapter cluster node. 15. Leave all services and the Shared folders group Offline.

Index A Abbreviations • 42 Adapter Data Source Files Location • 54 Adapter Details UI Page • 53 Adapter Manager Configuration • 53 Adapter XML File Configuration • 53 Additional Application Servers Installation

• 25 Additional Help • 1, 41 Appendix A - Typical Installation Windows

• 5, 7, 29 Appendix B - Custom Installation Windows

• 5, 8, 31 Appendix C - Oblicore's Naming

Conventions Policy for Database Objects • 5, 33

Appendix D - Oblicore Guarantee™ Environment Checklist • 9, 35

Appendix E - AdapterLocaleFix Tool • 15, 39

Appendix F - High Availability Installation • 41

B Balance Oblicore Services and Adapter

Programs between the Cluster Nodes • 54 C Client Components • 19 Client Installation • 19 Common Files • 42 Creating a Local User Account • 15, 23, 29,

31 Creating a New Database Manually • 9 Custom Installation • 7, 8 D Dividing Oblicore Guarantee™ Services •

25 E Enabling the Oracle Database CURSOR

Sharing Feature • 18 F From Scratch Post-installation Activities •

10 I Installation Platform • 41 Installation Process • 7, 20 Installing Oblicore Guarantee™ 6.3 Service

Release 1 from Scratch • 5, 49 Installing Oblicore Software on the Clusters

and NLB Nodes • 49 Installing Windows Clusters • 43 Installing Windows Network Load Balance

(NLB) • 47

Introduction • 1, 19, 41 L Load Balancing • 43 O Oblicore Software Configuration • 46, 50 Online Help Installation • 21 Overview • 3, 42 P Package Content • 2 Placing Adapters on Different Servers • 26 Post-installation Activities • 20 Prerequisites • 6, 13 S Supported Platforms • 19 T Target Audience • 1, 41 Typical Installation • 7 U Uninstalling Oblicore Guarantee™ 6.3

Service Release 1 • 27 Updating Adapters Not on Oblicore Server

• 18 Upgrade Post-installation Activities • 15 Upgrading from a Previous Version of

Oblicore Guarantee™ • 55 Upgrading From a Previous Version of

Oblicore Guarantee™ • 13 Upgrading Process • 15 Using this Appendix • 41

Date post:	03-Oct-2014
Category:	Documents
Upload:	jitesh-sharma
View:	130 times
Download:	2 times

Oblicore Guarantee 6_3_SR1 Installation Guide

Documents