Archive for June 2011
Adam Hall, Senior Technical Product Manager for Orchestrator, just posted new Orchestrator Integration Packs for the System Center 2007/2008/2010 releases and the Quick Integration Kit (QIK).
Quick Integration Kit (QIK):
1. System Center 2007/2008/2010 IPs direct download: http://download.microsoft.com/download/C/F/3/CF375506-F342-4974-B7B5-F06EFDEC159C/Opalis_SystemCenter_IntegrationPacks.EXE
That’s all for this first overview
Microsoft just released the beta of System Center Orchestrator 2012 (previously know as Opalis). http://blogs.technet.com/b/systemcenter/archive/2011/06/15/announcing-the-system-center-orchestrator-beta.aspx
This beta is public, could be downloaded and tested by everyone.
First, I invite you to read the Pre-requisites :
But also the Release Notes :
In these TechNet articles you will find useful information, like this one : Even if you are in a lab environment, don’t try to install System Center Orchestrator 2012 Beta on a Domain Controller, It will not pass the requirement check. (thank you to Adam and Ravi to notice that to me).
You will see that Microsoft did an awesome work on the installation process. It’s really easier than installing Opalis 6.3.
Basically, for installing this beta you will need a server with :
- Windows 2008 R2 Server (RTM or SP1, both supported)
- SQL 2008 R2
- .Net Framework 4
1. Download the System Center Orchestrator 2012 Beta file at the Microsoft Download Center : http://www.microsoft.com/download/en/details.aspx?id=26503
4. If you want to install all the features (Runbook Designer, Console/Web Service, Runbook server) on the same server, select Install Orchestrator. The installer also gives the possibility to install each features independently.
19. Orchestrator use a group (local group or Active Group) for authorizing access to the Run Book Designer. Go to your Active Directory console, create a new security group, add your user account and the service account created above as group member.
As you could see, Microsoft really did an awesome work on the installation process. Next post will present all the new features of System Center Orchestrator 2012 in details.
Today, another case that I had at one of my customer. The idea is simple, He wanted to generate an incident (Could be in SCSM, BMC Remedy) based on a SNMP Trap sent by a monitoring application. (SolarWinds, Tivoli, …)
The variables that we are interested in are Output – x – Value and we could use them in any of our activities. Here we will just display them, but we could imagine to use them for an incident creation :
We could now use information from SNMP Trap in any of our activities.
For one of my customer, I had to retrieve some information from an Oracle DB with System Center Opalis. The DB Query object included in Opalis supports MS SQL, Oracle, Odbc connection ….
For querying an Oracle DB with Opalis, there is some requirements, that I will explain step by step below :
1. Install the Oracle client on your Opalis server. Opalis requires the x86 release of the Oracle Client even if the Opalis server is in x64.
2. Oracle client is available at the following page : http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-win32soft-098987.html
3. Download this version : Oracle Database 11g Release 2 Client (126.96.36.199.0) for Microsoft Windows (32-bit).
win32_11gR2_client.zip (684,581,290 bytes)
4. When downloaded, and uncompressed, just execute the setup.exe file.
5. During the installation process, select Runtime as installation type, and continue the next /next setup.
6. Once the setup finished, we need new to edit the tnsnames.ora configuration file.
7. Go to InstallationFolderproduct11.2.0client_1networkadmin and edit the tnsnames.ora file.
8. ARSDVL is the name of the Oracle DB on which we want to connect, this name is used at two places in the file. line 4 as service name and also in the Connect_Data field. Host contqins is the name of the Oracle DB server.
9. Once the file edited and saved, for testing the connection, open a CMD prompt and type :
10. If the SQL> prompt appears, we now than everything is ok and we could go back to our Opalis policy.
12. Query Database object – Connection configuration : Add the name used in the tnsnames.ora file in the Service Name field, set the connection credentials.
13. Query Database object – Query : Here a simple Select query (Tips : Don’t add the ‘;’ at the end of the query or you will get an error message).
14. Send Platform Event – Configuration :
15. Run the policy.
16. Check the result