Opalis Integration Server Deployment Overview

Microsoft Corporation Published: February 2010

Feedback
Send suggestions and comments about this document to momdocs@microsoft.com.

Copyright
This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes. 2010 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveSync, Internet Explorer, JScript, SharePoint, SQL Server, Visio, Visual Basic, Visual Studio, Win32, Windows, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Revision History
Release Date Changes

February 2010

Initial version of document

Contents
Opalis Integration Server Deployment Overview .......................................................................... 4 System Prerequisites for Opalis Integration Server ................................................................... 5 Configuration Requirements for Opalis Integration Server ........................................................ 7 How to Install the Opalis Management Server .......................................................................... 9 How to Configure the Opalis Integration Server Datastore ...................................................... 10 How to Import a License into the Opalis Management Server ................................................. 11 How to Install the Opalis Integration Server Client .................................................................. 11 How to Install the Action Server .............................................................................................. 12 How to Install the Opalis Operator Console ............................................................................ 12

Opalis Integration Server Deployment Overview

This document covers the system requirements and steps required to install and configure Opalis Integration Server. In this example, the Opalis Integration Server system is configured to run with Microsoft Active Directory directory service integration and a Microsoft SQL Server database configured with Windows Integrated Security. For more configuration options, see the Opalis Integration Server Administrators Guide.

In This Section
System Prerequisites for Opalis Integration Server
Describes the hardware and software requirements for Opalis Integration Server.

Configuration Requirements for Opalis Integration Server

Describes configuration tasks required before installing Opalis Integration Server.

How to Install the Opalis Management Server

Describes how to install the Opalis Integration Server.

How to Configure the Opalis Integration Server Datastore

Describes how to configure the Opalis Integration Server Datastore.

How to Import a License into the Opalis Management Server

Describes how to import a license.

How to Install the Opalis Integration Server Client

Describes how to install the Opalis Integration Server Client.

How to Install the Action Server

Describes how to install an Action Server.

How to Install the Opalis Operator Console

Describes how to install an Opalis Operator Console.

System Prerequisites for Opalis Integration Server

This topic covers the minimum hardware and software requirements for Opalis Integration Server. Management Server, Operator Console, and Action Server System Requirements
Component Minimum Requirement

Processor

2.1 GHz dual-core Intel Xeon 3000 series or equivalent 2 GB Management Server and Operator Console 100 MB (installation) Operator Console - 200 MB (including JBoss) Action Server 50 MB Opalis policies might use more space when moving files or processing data. Add an appropriate amount of space for the Opalis policies that you create.

Memory Hard Disk

Operating System

Windows Server 2003 with Service Pack 1 or 2 (32-bit) Windows Installer 3.1 .msi file Microsoft .NET Framework 2.0 Microsoft SQL Server 2005 or SQL Server 2008 Microsoft Internet Explorer 7, Internet Explorer 8 (Internet Explorer 7 compatibility mode), or Mozilla Firefox 3 JavaScript must be enabled in the browser.

Additional Software

Download the following components prior to installing the Operator console. Operator Console Java and JBoss Requirements
Requirement Description/Location

Java Development Kit 6 Update 4 JBoss Application Server 4.2.3.GA

http://go.microsoft.com/fwlink/?LinkId=182348 http://go.microsoft.com/fwlink/?LinkId=182349 5

Requirement

Description/Location

Hibernate Validator 3.0.0.GA

http://go.microsoft.com/fwlink/?LinkId=182350 Important For the MD5 hashes for all files that need to be downloaded, see MD5 Hashes for Operator Console Lib Files.

Hibernate Commons Annotations 3.3.0.GA Richfaces-API 3.3.1.GA Richfaces-UI 3.3.1.GA Richfaces-Implementation 3.3.1.GA JBoss-EL 2.0.1.GA JSF-Facelets 1.1.14 Java Native Access 3.0.9 JAX-WS RI JBoss Seam-Core 2.0.2_SP1 JBoss Seam-Remoting 2.0.2_SP1 JBoss Seam-UI 2.0.2_SP1 JBoss Seam-Debug 2.0.2_SP1 JBoss Seam-Mail 2.0.2_SP1

http://go.microsoft.com/fwlink/?LinkId=182351 http://go.microsoft.com/fwlink/?LinkId=182352 http://go.microsoft.com/fwlink/?LinkId=182353 http://go.microsoft.com/fwlink/?LinkId=182354 http://go.microsoft.com/fwlink/?LinkId=182355 http://go.microsoft.com/fwlink/?LinkId=182356 http://go.microsoft.com/fwlink/?LinkId=182357 http://go.microsoft.com/fwlink/?LinkId=182358 http://go.microsoft.com/fwlink/?LinkId=182359 http://go.microsoft.com/fwlink/?LinkId=182360 http://go.microsoft.com/fwlink/?LinkId=182361 http://go.microsoft.com/fwlink/?LinkId=182362 http://go.microsoft.com/fwlink/?LinkId=182363

MD5 Hashes for Operator Console Lib Files

File Name Hash Value

jdk-6u4-windows-i586-p.exe jboss-4.2.3.GA.zip hibernate-validator-3.0.0.ga.jar hibernate-commons-annotations-3.3.0.ga.jar richfaces-api-3.3.1.GA.jar richfaces-ui-3.3.1.GA.jar richfaces-impl-3.3.1.GA.jar

78a79a3efc4aeee31edd33f361dd4ac0 d1ded1cc876733fec96b5e2934c81220 e4b13b8a07c51d6d532b5d6a861d65b5 1ccefbe43fedffc16835ceb1a777d199 1d1ac9492d6b8e371d542731cb9a8fcd d76c5f8d830620304168b9abe1b9eee8 2f220f23ebf3f8a7ced85d2bdf60c557 6

File Name

Hash Value

jboss-el-2.0.1.GA.jar jsf-facelets-1.1.14.jar jna-3.0.9.jar JAXWS2.1.2-20070917.jar jboss-seam-2.0.2.SP1_TWM2.jar jboss-seam-remoting-2.0.2.SP1.jar jboss-seam-ui-2.0.2.SP1.jar jboss-seam-debug-2.0.2.SP1.jar jboss-seam-mail-2.0.2.SP1.jar

8c9cd1dd32c5e607f63b005c26f76de5 9a35730b032c22040db8f77ace0a6118 074e388212fdb098cf55177a7f42540e 53f1cb11511ece56aabe9ff01bf8d16a 1d470f1e426161af29b778c1acb25efb f1361e9873d14420398033cb6b9fc094 d55e4bc758b9d6d9bb4885d4a1c0b6eb 581f679ecf648a77f9d602765b23d5c4 a16e22d3ba79b4cb095a5df2a4291f97

Configuration Requirements for Opalis Integration Server

Perform the following tasks before you install Opalis Integration Server to ensure that the installation is successful.

Preparing the Action Server and Management Server Computers

Opalis Integration Server automates tasks across the entire server architecture. This type of automation requires high levels of access permissions. It is imperative to restrict access to the Action Server and Management Server computers such that only authorized administrators can change the settings on these computers. To prepare the computers that will host these services, we recommend the following: 1. Restrict interactive logon access to the local Administrators group only. 2. Add only the minimum necessary user accounts or groups to the local Administrators group. For more information about configuring user permissions, user rights, and security policies, see Access Control Best Practices (http://go.microsoft.com/fwlink/?LinkId=181208) on Microsoft TechNet.

Define the service account

Identify a service account to access system resources for the Management Server service and Action Server service on each computer where these services are installed. The account on the computer where the Management Server service or Action Server service is installed must have access to network resources. The account should be a member of the Administrators group on

the computer where the Management Server service and Action Server service are installed. The service account does not have to be a domain administrator.

Grant authentication to the service user account

Because Opalis Integration Server uses services to operate, the account that you identify for use by the Management Server service and Action Server service must have the Log on as a service user right assigned to it. To assign Log on as a service permissions to an account 1. Click Start, click Run, and then type GPEDIT.MSC and press ENTER. 2. In the Local Group Policy Editor, in the navigation pane, click Local Computer Policy, click Computer Configuration, and then click Windows Settings. 3. Click Security Settings, click Local Policies, and then click User Rights Assignment. 4. Under Policy, right-click Log on as a service, and then click Properties. 5. Click Add User or Group. 6. Enter the name of the service account in the provided box. 7. Click OK, and click OK. 8. In the Local Group Policy Editor, in the navigation pane, click Local Computer Policy , click Computer Configuration, and then click Windows Settings. 9. Click Security Settings, click Local Policies, and then click User Rights Assignment. 10. Under Policy, click Deny logon as a service. 11. Verify that the service account is NOT included in Deny logon as a service. 12. In the Local Group Policy Editor, in the navigation pane, click Local Computer Policy, click Computer Configuration, and then click Windows Settings. 13. Click Security Settings, click Local Policies, click User Rights Assignment, and then click Act as part of the operating system. 14. Verify that the service account is NOT included in Act as part of the operating system. 15. Close the Local Group Policy Editor.

Grant authorization to the Action Server Service Account

Any remote computers that the Action Server service performs operations on must allow the service account access information about the remote computer. Verify that the server account that you have assigned to the Action Server service has permission on the remote computer to perform read and write operations. Some Opalis objects in Opalis Integration Server enable you to use impersonated credentials for performing operations on remote computers. In the Properties dialog box of objects that use impersonated credentials, you will be asked to provide the credentials for the remote computer. These credentials will be supplied to the remote computer when the Opalis object runs. 8

How to Install the Opalis Management Server

The following components are installed during the Opalis Management Server Installation: Management Server service and all related library files Database Configuration tool License Manager tool Deployment Manager Self-Monitoring components Audit Trail components To begin the Opalis Integration Server installation 1. Extract the files in the compressed archive to a temporary folder. 2. In the temporary folder, double-click the Setup.exe file. 3. In the Opalis Installation window, click the Install Opalis Integration Server option. The Install Opalis Integration Server splash screen opens. To install the Opalis Management Server 1. On the Opalis Integration Server Install splash screen, click Install Opalis Integration Server 2. The Management Server Installation Wizard opens, click Next. 3. In the License Agreement window, select the Accept license agreement option, and click Next. 4. On the User Information page, type your name in the Full Name box and your organizations name in the Organization box. 5. Select the computer users who will have access to the application. 6. Click Next. 7. On the Destination Folder page, click Next to accept the default settings. 8. On the Logon Information page, enter the service account credentials used by the Management Server service and Operator console service. Important If you are using Windows authentication on your computer running Microsoft SQL Server, then the user assigned to the Management Server and the Action Server services requires appropriate access permissions to read and write data to the SQL Server. 9. Click Next. 10. When the Ready to Install the Application page appears, click Next. 11. When the wizard has finished the installation, click Finish.

The Opalis Management Service is now installed.

How to Configure the Opalis Integration Server Datastore

This topic describes how to configure the Datastore for the Opalis Integration Server installation. The Datastore resides in a Microsoft SQL Server database system. The Database Configuration tool prepares the database where Opalis Integration Server stores information about your Opalis 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 tool to make changes to the Datastore after you have installed Opalis Integration Server. The Database Configuration tool also creates the connection settings that will be used by either the Management Server or Action Server installed on the computer. 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 tool on the computer can access it. If this file is missing or the permissions have been changed, the Management Server or the Action Server might report errors that a connection to the Datastore cannot be made. If you have changed your database settings, that is, port, user account access, or computer where it is installed, you have to re-run the Database Configuration tool on the Management Server and all Action Servers. Note Opalis Integration Server supports Microsoft SQL Server 2005 or SQL Server 2008. Microsoft SQL Server Express Edition is not supported. Note You must use the roles Database Creators and Setup Administrators on SQL Server when you configure a SQL Server database to be used as the data store. To configure the Opalis Integration Server Datastore 1. On the Install Opalis Integration Server splash screen, click Configure the Datastore. 2. In the Database Configuration wizard, click the Type tab. Select the Microsoft SQL Server option. 3. Click Next. 4. On the Server Details tab, in the Server box, type localhost, or the fully qualified name of the server that is running the SQL Server database that will host the data store. 5. Select Windows Authentication as the authentication credentials. 6. Click Next. 7. The Database Details tab appears. Select Create a new database and enter Opalis as the name for this database. 10

8. Click Finish. 9. In the Success dialog box, click OK. The Opalis Integration Server Datastore is now configured.

How to Import a License into the Opalis Management Server

This topic describes how to import a license into the Opalis Management Server. To import a license 1. On the Install Opalis Integration Server splash screen, click Import a License. 2. After the License Manager tool opens, click Import. 3. The Import License dialog box opens. In the Key box, type or paste the key provided to you by Opalis Software Inc. 4. In the License file box, type the path of the license file provided to you by Opalis Software Inc. 5. Click OK. The license is imported into the database. 6. In the License file successfully imported dialog box, click OK. 7. Click Close. The license is now installed.

How to Install the Opalis Integration Server Client

This topic describes how to install the Opalis Integration Server Client. To install the Integration Server Client 1. On the Install Opalis Integration Server splash screen, click Install the Client. 2. On Integration Server Client Install Wizard Welcome screen, click Next. 3. On the Licensing agreement dialog box, agree to the Microsoft Software License Terms. 4. Click Next. 5. On the Destination folder dialog box, click Next. 6. On the Ready to Install the Application dialog box, click Next. 7. When the wizard is completed, click Finish. The Opalis Integration Server Client and the Foundation Library of Opalis objects are now 11

installed. After the Integration Server Client has been installed, you can build and test Opalis policies on the Opalis Integration Server system.

How to Install the Action Server

This topic describes how to install the Action Server. To install the Action Server 1. On the taskbar, click Start, click All Programs, and then click Opalis Integration Server Deployment Manager Utility. 2. In the Opalis Integration Server Deployment Manager utility, right-click the Action Servers node. 3. Click Deploy Action Server. 4. On the Action Server Deployment Wizard Welcome page, click Next. 5. On the Service Selection page, in the Computer box, type localhost. 6. In the Description box, type First Action Server. 7. Enter the credentials that will be used to run the Action Server service. Important Use a user account that has the appropriate administrative credentials to connect to the database if you are using Windows Authentication. This account should also have rights to create impersonation tokens so that it can target remote Windows-based computers for remote tasks. 8. On the Deploy Integration Pack or Hotfix page, click Next. 9. On the Completing Action Server Deployment page, click Finish. 10. The wizard deploys the new Action Server and any integration packs or hotfixes that you selected. The Action Server and the foundation library are now installed on the target computer.

How to Install the Opalis Operator Console

The Operator Console provides a Web-based view into the runtime of the Opalis Integration Server system. To install the Operator Console, you have to download and install JBoss, Java, and specific Java libraries. For more information about pre-installation requirements, see System Prerequisites for Opalis Integration Server and Configuration Requirements for Opalis Integration Server.

12

Installing the Operator Console

To install JBoss on your computer 1. Install JDK 6 Update 4 with default settings. 2. Set the JAVA_HOME system variable to the directory of your local JDK installation. 3. Extract the contents of the JBoss Application Server 4.2.3.GA .zip file to a folder on your computer. 4. Copy the contents of the OperatorConsole folder, located on the Opalis Integration Server CD, into the <JBOSS> folder. If you are prompted to overwrite files or folders, click Yes to all. 5. Copy the Server folder from <JBOSS>\offline\datastore\sqlserver to the <JBOSS> folder for your datastore. 6. If you are prompted to overwrite files or folders, click Yes to all. 7. Copy the Server folder from <JBOSS>\offline\authentication\ActiveDirectory to the <JBOSS> folder for your datastore. If you are prompted to overwrite files or folders, click Yes to all. To install the Java .jar libraries to the Operator Console location on your computer 1. Open a command prompt. 2. Browse to the folder where you downloaded JAX-WS. 3. At the command prompt, enter java -jar JAXWS2.1.2-20070917.jar. A license dialog box appears. 4. Accept the license. This JAX-WS .jar file is created in jaxws-ri\lib. Note If the JDK \Bin folder location is not included in the computers PATH environment variable, you have to specify the path to java.exe. 5. Copy the following .jar files to the destination folder <JBOSS>\Server\Default\Deploy\OpConsoleApp-1.0.ear. Hibernate-commons-annotations-3.3.0.ga.jar Hibernate -validator-3.0.0.ga.jar JBoss-el-2.0.1.GA.jar JBoss- seam-2.0.2.SP1_TWM2.jar JSF-facelets-1.1.14.jar Richfaces-api-3.3.1.GA.jar Richfaces-impl-3.3.1.GA.jar Richfaces-ui-3.3.1.GA.jar

6. Copy the following .jar file to the destination folder 13

<JBOSS>\Server\Default\Deploy\OpConsoleAuditTrailLog-1.0.sar\lib. jna-3.0.9.jar 7. Copy the following .jar files to the destination folder <JBOSS>\Server\Default\deploy\OpConsoleWebServiceBridge-1.0.war\WEB-INF\lib. jaxws-ri\lib\jsr250-api.jar jaxws-ri\lib\saaj-api.jar jaxws-ri\lib\saaj-impl.jar jaxws-ri\lib\stax-ex.jar jaxws-ri\lib\streambuffer.jar jaxws-ri\lib\ sjsxp.jar jaxws-ri\lib\jaxws-api.jar jaxws-ri\lib\jaxws-rt.jar jaxws-ri\lib\jaxws-tools.jar jaxws-ri\lib\jaxb-api.jar jaxws-ri\lib\jaxb-impl.jar jaxws-ri\lib\jaxb-xjc.jar

8. Copy the following .jar files to the destination folder <JBOSS>\server\default\deploy\OpConsoleApp-1.0.ear\OpConsoleWeb1.0.war\WEB-INF\lib. jboss-seam-remoting-2.0.2.SP1.jar jboss-seam-ui-2.0.2.SP1.jar jboss-seam-mail-2.0.2.SP1.jar jboss-seam-debug-2.0.2.SP1.jar <JBOSS>\server\default\lib\jboss-jaxrpc.jar <JBOSS>\server\default\lib\jboss-saaj.jar

9. Copy the following .jar files to the destination folder <JBOSS>\lib\endorsed.

To configure the database 1. Open the file <JBOSS>\server\default\deploy\Opalis-ds.xml. 2. Edit the <connection-url> attribute to match the following syntax: jdbc:sqlserver://<SERVER>:<PORT>;database=<DATABASE>;integratedSecurity=t rue;, where <SERVER> and <PORT> are the Server and Port used to connect to the database server, and <DATABASE> is the name of the database that you created. 3. Delete the <user-name> tag. 4. Delete the <password> tag. 5. We recommend that you secure your SQL Server authentication passwords. For more information, see Encrypting datasource passwords 14

(http://go.microsoft.com/fwlink/?LinkId=182901). Important We also recommend that you secure the JBoss JMX and Web console. For more information about securing those consoles, see Securing the JMX Console and Web Console (http://go.microsoft.com/fwlink/?LinkId=182903). To run the Opalis Integration Server Operator Console 1. Configure Secure Sockets Layer (SSL) support. For more information about configuring SSL for the Operator Console, see Securing the Operator Console Installation in the Administrator Guide. 2. Edit run.bat in the <JBOSS>\bin folder. 3. Find the line in the file that sets the memory options for Java. Change it to appear like the following code example.
rem JVM memory allocation pool parameters. Modify as appropriate. set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=128m

Save the file and close it. Note For more information about achieving the optimal performance of your JBoss environment, see Parameters passed to the JBoss Run Scripts (http://go.microsoft.com/fwlink/?LinkId=182904). 4. Start JBoss by running the following command in the <JBOSS>\Bin folder:
run.bat -b 0.0.0.0

Note You can create a Windows Service to automatically run JBoss when the computer starts up by using the Java Service Wrapper provided by Tanuki Software. For more information about the Service Wrapper, see Java Service Wrapper (http://go.microsoft.com/fwlink/?LinkId=182905).

15