WARNING: This POST IS A LONG EXHAUSTIVE ONE AND YOU HAVE BEEN FOREWARNED
The recent release has created many waves throughout the entire System Center community and I wanted to share some of my experiences throughout my journey exploring Opalis since it joined the System Center familiy. And I would like to start my sharing with some postings on the installation steps for Opalis from 6.2.2 –> SP1 –> 6.3
Now in Part I, I will commence with the installation of Opalis 6.2.2, the very first version of Opalis since it joined the good old System Center family
- To kickstart things, my Opalis server runs on Windows 2008 R2 (x64) and has been installed with MS SQL Server 2008 SP1 (x64)
- You will also need Windows PowerShell 2.0 installed (to automate Operator Console installation)
- Once that is done, extract your installation resources
- The installation version would be \Opalis Integration Server 6.22_18.104.22.16829 as depicted in the picture below
- Kickstart Installation by executing the Setup.exe
- Click on Install Opalis Integration Server
- On the next screen, click on Install the Management Server
- Accept the Licensing Agreement and goes Next
- Proceed with defaults until you reach the Logon Information step. In this step, you need to provide a valid user account that will be used by the Opalis Management Service (basically that is your Service Account). Enter a valid user and proceed to commence installation of the Management Server.
- The next thing you need to do is to configure the datastore (which simply means configure the Opalis DB). Simply click Configure Datastore to commence the process
- The next screen will need your input the select which database will host the Opalis DB and since we LOVE Microsoft so much … I will choose MS SQL Server and proceed
- Now in the Server details, enter the DB server and the authentication method and proceed (In this case, my SQL is the same as the Opalis server and I have set to use Windows Authentication during the installation of SQL Server)
- Give the name for the Opalis DB and proceed to let installer do the rest.
- The next step is to import a license for Opalis. In the License Manager, click on Import. When prompted to Import license, enter the license key and the corresponding license file made available for you either as a customer or an evaluator. Once you are don, click Close
- The next thing that you want to do is to Install the client
- Accept the license terms and accept defaults and let the rest roll by itself.
AND YOU THOUGHT IT’S ALL DONE SO EASILY ??? THINK AGAIN … YOU HAVE JUST GONE THROUGH THE EASY PART.
- When I first started to install Opalis, I dreaded the way they forced us to install the Operator Console because unlike the always easy Microsoft Wizard based approach, we are tasked to “install” the Operator Console by a series of copy & paste of java object which is SIMPLY PAINFUL
- Even preparing the installation for Operator Console is a bitch simply because you need to manually prepare the pre-requisites which would be:
- Download JDK 6 Update 4 from http://java.sun.com/products/archive/
- Download JBoss Application Server 4.2.3.GA from http://jboss.org/jbossas/downloads/
- Then you have a very long list of Pre-Requisites of Java Objects that is scattered all over the internet which I am kind enough to download and made available for you at my SKYDRIVE folder at http://cid-8b468d6e5c4e0782.office.live.com/browse.aspx/Opalis%20Pre-Req
- Well, apparently things have changed when SP1 was rolled out where our lives are made abit easier where Microsoft provides us with an installation script to automate the installation steps.
- Extract the Installation Resources for the following \Opalis 6.2.2\Opalis Operator Console Installer Script 1.0_1.0.0.0001
- Run the OpalisOperatorConsoleInstaller.msi file
- Create a new folder C:\Libraries
Copy all the pre-requisites file that you have downloaded from my skydrive into this folder
- Install Java Development Kit 6 Update 4 by using the default settings.
- Set the JAVA_HOME system variable to the directory of the local Java Development Kit. By default, the location is C:\Program Files\Java(x86)\Jdk1.6.0_04.
- Add %JAVA_HOME%\bin to the Path Environment variable.
- Extract the contents of the JBoss Application Server 4.2.3.GA to the folder where the JBoss Application Server will run. Eg C:\JBoss.
- Launch the command prompt, change to the C:\Libraries folder and run the command
java -jar JAXWS2.1.2-20070917.jar.
- A license dialog box appears.Accept the Sun Microsystems, Inc. License Terms. The JAXWS2.1.2-20070917.jar file will be unpackaged.
- Confirm that the \Jaxws-ri\Lib folder was created.
- Click Start, click Programs, click Accessories, click the Windows PowerShell folder, and then click the Windows PowerShell item.
- At the Windows PowerShell prompt, type
- Type the full path to the location where you installed the InstallOpConsole.ps1 file. For example, C:\OpConsoleInstaller\installOpConsole.ps1
- 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. 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.
- 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
Ladies and Gentleman, you will know that the Operators Console installation is successful when you see the following:
Now I will end the rather exhaustive post on this Part I and will continue with the next Part where I will share how do you patch Opalis to SP1.
Note: I will only deploy my Action Servers & Integration Pack once I am done with the installation up to version 6.3
Till then …. STAY TUNED.