Opalis Installation

ContentsOverview...............................................................................................................................................1

Process..................................................................................................................................................2

Installing the Management Server........................................................................................................4

What Is Installed................................................................................................................................8

Database Configuration.........................................................................................................................9

Configuring the Datastore to use Microsoft SQL Server....................................................................9

To install required software on the Operator Console computer........................................................13

Overview

Opalis Integration Server is a suite of applications that enable you to create, deploy, and execute Policies that will automate your well-known and repeatable IT procedures. It includes the following components:

Client - The Opalis Integration Server Client enables you to build, deploy, and maintain your policies.

Operator Console – The Operator Console enables you to see which Policies are currently running, view their real-time status, and start or stop them from a browser console interface.

Policy Testing Console – The tool used by administrators to test Policies that are developed in the Client before they are deployed.

Action Server – The engine that executes Policies. Action Servers have failover mechanisms that ensure performance and stability.

Management Server – The central communication hub of the other components.

Deployment Manager - This tool enables you to view your entire Opalis Integration Server infrastructure and deploy Action Servers, Clients, Integration Packs, and Hotfixes from one place.

Remote Trigger - Opalis Integration Server now includes an additional utility that you can configure on a remote system to execute policies from a 3rd party system.

ProcessInstall:

Management Server Datastore Client Operator Console Action Server Import Operations Manager 2007 Integration Pack

Note: Powershell version 2 (not v1 is required). If you have version 1 installed, you’ll need to uninstall this prior to installing version 2.

http://geekzguru.wordpress.com/2008/02/16/howto-uninstall-powershell-10/

Installing the Management ServerPerform the following procedure to install the Management Server.

1. Click Install the Management Server in step 1 of the Install Opalis Integration Server splash screen.The Management Service Setup screen appears.

2. Click Next. The License Agreement page appears.

3. Select the I accept the license agreement option and click Next. The User Information page appears.

4. Type your name and your organization’s name in the respective fields, then select which users on your computer will have access to the application. Click Next.

6. Click Browse to choose a different destination folder, or click Next to accept the default.

7. The Logon Information page appears.Type the user name (DOMAIN\Username format) and password that the Management Service and Operator Console Service will use. Click Next.

8. The Ready to Install the Application page appears. Click Next.

9. The Management Service is installed. When the wizard has finished the installation, click Finish. The Install Opalis Integration Server splash screen appears.

What Is InstalledThe Management Server installation program installs the following items:• The Management Server service and all related library files.• The Database Configuration utility.• The License Manager utility.• The Deployment Manager.• The Self Monitoring components.• The Audit Trail components.

10. On the Install Opalis Integration Server splash screen, click Configure the Datastore. Continue with the Datastore configuration procedure.

Database ConfigurationThe Database Configuration utility prepares the database where Opalis Integration Server stores information about your Policies. This database is called the Datastore. You must configure the Datastore before you can use the product. You can also use the Database Configuration utility to make changes to the Datastore after you have installed Opalis Integration Server. The Database Configuration utility also creates the connection settings that will be used by either the Management Server or Action Server installed on the machine. It stores the settings in a file called settings.dat, which is an encrypted file. This file is also configured with ACL permissions so that only Local Administrators or the user who ran the Database Configuration utility on the machine can access it. If this file is missing or the permissions have been changed, the Management Server or the Action Server may report errors that a connection to the Datastore cannot be made.

If you have changed your database settings, i.e. port, user account access, or machine where it is installed, you will need to re-run the Database Configuration utility on the Management Server and all Action Servers.

Note: Management Servers and Action Servers that are installed on the same computer must be configured to use the same Datastore.

Configuring the Datastore to use Microsoft SQL ServerNote: You must be a member of the SQL Server SysAdmin role when you configure a SQL Server database to be used as the Datastore.

1. Click Configure the Datastore on the Install Opalis Integration Server splash screen.

2. On the Database Type page Type tab, select the Microsoft SQL Server option and click Next.

3. The Server Details page appears. In the Server field, type the name of the server that is running the SQL Server database that will host the Datastore.

Do not use 'localhost' or'127.0.0.1'. To specify the fully qualified database server name you must use type TCP:<server>\<instance>,<port> replacing <server>, <instance>, and <port> to match the details of your Microsoft SQL Server database.

Select the authentication method to use to connect to the SQL Server - This account must have rights to create, write, and own a database as well as create, update, and delete rows in the database. Click Next.

4. The Database Details tab appears. Select the action that you want to use to create the Datastore:

• Create a new database - Select this option to create a new Management Database and type a name for this database.

• Use an existing database - Select this option if you have already created a database in SQL Server that you will use as a the Datastore, and select the name of the database from the Name drop-down list. The authentication credentials that you specified onthe Server tab must have rights to create, write, and own a database as well as create, update, and delete rows in the database.

Note: Select Use an existing database if you are performing a manual deployment of an Action Server.

Click Finish

5. The Database Configuration utility creates the Datastore.

6. The Install Opalis Integration Server splash screen appears.

Click Install a License. The License Manager dialog appears.

You must enter both the license key and file

Opalis Integration Server 6.2.2 OpalisIntegrationServer_180DAY_EVAL.lic {B3DBAA89-0715-48E8-95AA-6DAF0C689944}Integration Pack for System Center Operations Manager 2007

Opalis Integration Pack for SCOM 180 DAY EVAL.lic {7146DE5F-13D1-4E8B-9320-130F7D059D52}

To install required software on the Operator Console computer1. Log on to the computer on which you will install the Operator Console as a member of the

Administrators group.

2. Download the Opalis Integration Server 6.2.2 Operator Console Installer Script.

3. Make a note of the location where you install the InstallOpConsole.ps1 file.

4. Download all of the Operator Console prerequisite binaries and third-party libraries listed in the “System Requirements” section of the Administrator Guide. We recommend that you put these files in a single folder, for example, C:\Libraries.

5. Install Java Development Kit 6 Update 4 by using the default settings.

6. Create (a New) JAVA_HOME system variable to the directory of the local Java Development Kit. By default, the location is C:\Program Files\Java\Jdk1.6.0_04.

7. Add (Edit Path) %JAVA_HOME%\bin to the Path Environment variable.

8. Extract the contents of the JBoss Application Server 4.2.3.GA to the folder where the JBoss Application Server will run. We recommend that you extract the contents to C:\JBoss.

9. At a command prompt, change to the \Libraries folder and run the command java -jar JAXWS2.1.2-20070917.jar. A license dialog box appears.

10. Accept the Sun Microsystems, Inc. License Terms. The JAXWS2.1.2-20070917.jar file will be unpackaged.

11. Confirm that the \Jaxws-ri\Lib folder was created.

12. Copy the OperatorConsole folder from the Opalis Integration Server 6.22_6.2.2.5229 folder to c:\Libraries

1. Click Start, click Programs, click Accessories, click the Windows PowerShell folder, and then click the Windows PowerShell item.

2. At the Windows PowerShell prompt, type set-executionpolicy RemoteSigned.

3. Type the full path to the location where you installed the InstallOpConsole.ps1 file. For example, C:\OpConsoleInstaller\installOpConsole.ps1.

Note As a security feature, Windows PowerShell does not run scripts when you double-click the script icon in Windows Explorer or when you type the script name without a full path, even when the script is in the current directory. For more information about running commands and scripts in Windows PowerShell, see "About Command Precedence" in the Windows PowerShell Help (http://go.microsoft.com/fwlink/?linkID=113214).

If the path to the InstallOpConsole.ps1 file contains spaces, at the Windows PowerShell prompt, type an ampersand, followed by a space, and then type the full path enclosed in single quotes. For example,

& ‘C:\Install Op Console\InstallOpConsole.ps1’4. Follow the on-screen prompts. You will be asked to provide configuration information, for

example:

a. The full path to the location of the \JBoss folder.

b. The full path to the location of the \OperatorConsole folder (c:\libraries\operatorconsole).

c. The full path to the location of the \Libraries folder.

d. The database type (Microsoft SQL Server or Oracle).

e. The name of the database server, for example, localhost.

f. The database authentication type (Windows authentication or SQL Server authentication). For SQL Server, provide the user name and password.

g. The name of the Opalis database.

h. The user authentication type (Stand-alone or Active Directory). For Active Directory, provide the Active Directory root DN, Domain Controller, Port, and SAM account name for the administrator group.

5. When the Operator Console installation complete message appears, click Close.

Start JBoss by executing the following command in the <JBOSS>\bin

folder:

run.bat -b 0.0.0.0

To install the Operator Console by using the Windows PowerShell installation script

Install Action ServerThe Action Server is where Policies run once they are started. You can deploy an Action Server to any computer that can communicate with the Datastore. Action Servers can be deployed automatically from a Management Server that is using the same Datastore or manually using the installer file and manually configuring the databse settings. It is recommended to use automatica deployment.

To deploy an Action Server automatically, you must use the Deployment Manager.

1. Open the Deployment Manager.

2. In the Management Server pane (on the left side), expand the Management Server item until the Action Servers item is visible.

3. Right-click the Action Server item and select Deploy new Action Server. The Action Server Selection wizard page appears.

4. In the Computer field, type the name of the computer where the new Action Server will be deployed, or click the ellipsis button (...) and browse for it. Note: Management Servers and Action Servers that are installed on the same computer must be configured to use the same Datastore.

In the Description field, type a brief description of theAction Server.

In the User name and Password fields, type the user name and password of the account that you will use to access the new Action Server.

7. Click Next. The Deploy Integration Pack or Hotfix Deployment page appears.

If you have previously registered Integration Packs or Hotfixes and you want to deploy them to the new Action Server, check the check box for each item that you want to deploy. Before you can deploy Integration Packs or Hotfixes, you must register them with a Management Server. Click Next

8.The Completing Action Server Deployment page appears. Click Finish

9.. The wizard deploys the new Action Server and any Integration Packs or Hotfixes that you selected.

Import Operations Manager 2007 Integration PackTo deploy Integration Packs and Hotfixes, you must use the Deployment Manager. There are two steps: registering the Integration Pack or Hotfix, then deploying it.

Registering an Integration Pack or Hotfix with a Management ServerBefore you can deploy Integration Packs or Hotfixes, you must register them with a Management Server.

1. Save the Opalis_IP_MicrosoftSystemCenterOperationsManager2007_553.oip file for the Integration Pack to the local hard drive of the Management Server.

2. Open the Deployment Manager. In the Management Server pane, expand theManagement Server item that you want to register the items on.

Right-click the Integration Packs item and select Register IP with the Management Server. The Integration Pack Registration wizard appears. Click Next.

3. The Integration Pack or Hotfix Selection page appears. Click Add. The Open dialog appears. Locate the .oip file, select it, and click Open. The Integration Pack or Hotfix appears in the list. Repeat steps 2 and 3 for each Integration Pack or Hotfix that you want to register. Click Next.

4. The Completing Integration Pack Registration Wizard page appears. Click Finish.

5. The End-User License Agreement dialog appears. Click Accept. The Integration Pack or Hotfix is registered on the Management Server.

Deploying an Integration Pack or Hotfix to an Action Server or ClientAfter you have registered an Integration Pack or Hotfix to a Management Server, you can deploy them to Action Servers or Clients.

1. In the Management Server pane, expand the Management Server item that you want to deploy to, right-click the Integration Packs item and select Deploy IP to Action Server or Client. The Integration Pack Deployment wizard appears. Click Next.

2. The Integration Pack or Hotfix Deployment dialog appears. In the list, select the check box for each Integration Pack or Hotfix that you want to deploy. Click Next.

3. The Computer Selection page appears. In the Computer field, type the name of the computer where the Integration Pack or Hotfix will be deployed, or click the ellipsis button (...) and browse for it. Click Add. The computer appears in the list. Repeat step 3 until you have finished adding computers that you want to deploy Integration Packs and Hotfixes to. Click Next.

4. The Installation Options page appears. To choose a time to deploy the Integration Packs or Hotfixes, check the Schedule installation check box and select the time and

date from the Perform installation spin box and drop-down list. For example, you could schedule the deployment for a time when demand for system resources is lowest.

Do one of the following:• To stop all running Policies before deploying the Integration Packs or Hotfixes, select the Stop all running Policies before installing the Integration Packs or Hotfixes option.

• To install the Integration Packs or Hotfixes without stopping any running Policies, select the Install the Integration Packs or Hotfixes without stopping the running Policies option.

Click Next.

5. The Completing Integration Pack Deployment Wizard page appears. Click Finish. If you did not configure a deployment schedule, the Integration Packs and Hotfixes are deployed to the Action Servers or Clients that you specified immediately. If you configured a deployment schedule, verify that the deployment occurred by checking the logs after the scheduled time has passed.

Using OpsMgr 2007 Integration Pack

Make sure you have the Operations Manager 2007 R2 Console installed on the Action Server

1. Open the Opalis Integration Server Client and go to Options, Microsoft Operations Manager 2007

15. Close all affected Clients and open them again.