I just thought of sharing my experience recently had on SCOM Remedy Integration...
SCOM Integration with 3rd Party Product (BMC Remedy ARS 6.3)… using connectors.
The environment I've used is officially not tested by Microsoft ...
My environment consist of SCOM 2007 R2 running on Windows 2008 R2 SP1, ARS 6.3. I’ve tested both on SQL DB 2005 & SQL 2008 DB
ü Operations Manager 2007 R2 Connectors provide Operations Manager 2007 R2 alert forwarding to remote systems, such as an Enterprise Management System (EMS) or a service desk system. After Operations Manager 2007 R2 forwards an alert to a remote system, that alert data is synchronized throughout the lifetime of the alert. The result of that data synchronization is a robust and seamless systems management environment.
ü Following are the minimum requirement for SCOM Remedy Integration. As part of integration two components gets installed
§ Provider, runs on remedy environment
§ Connector, runs on SCOM environment
ü Tool can be downloaded from below Microsoft url. The SCInterop_R2_RTM.exe has ref guide and connector & provider for all supported 3rd party systems.
Pre-requisite for Provider & Connector components:
• A server with Remedy User application (v6.3 or higher) at least (don’t need Remedy Server specifically). Minimum OS Windows 2003 + SP2 (for provider)
• The English version of Microsoft Visual C++ 2008 Redistributable Package (x86) if Visual C++ 2008 is not installed. (for both connector and provider)
• WS-Management 1.1 (for both connector and provider)
• Local admin permission for Domain account on the given Remedy server
• A User in Remedy with administrative privileges
• .NET Framework 3.0 SP1 or a later version (connector)
• Server running SCOM console at least and DB Instance running on SQL 2005 minimum. OS Windows 2003 + SP2 minimum
Installation order:
i. First install provider on a windows 2003 server. For that execute SciProviderSetup.exe and click next to begin Installation.
ii. Select BMC Remedy ARS 6.3 Provider, click next next and finish the installation.
iii. Reboot the server after provider installation.
iv. Install connector on the server by executing SciConnectorSetup_x64.exe.
v. select BMC Remedy connector service and connector configuration option and click next.
vi. On SQL server configuration wizard specify your Database server. Database Name would remain default as (SCInterop) with default SQL Server port (1433) and click next.
vii. On next screen specify connector login service name and password click next and complete the installation.
viii. Now opsmgr configuration wizard comes up here specify the configuration for Remedy server, version and ws-man server credentials. Click next and complete the configuration.
ix. on next screen click next for connector certificate installation. Reboot the server after successful installation.
x. Provider and connector are installed now. It’s time to import Interface Forms, Filters, and Data Files
on Remedy server. The .xml file that contains these forms and filters are copied to the Interop Provider installation folder.
The files are SCIOpsMgr2007Interface-63.xml and SCIStateTransitions.xml. For import of files please follow step by step process on the below link:
xi. Once definition files are imported on the Remedy server you can check forwarding alerts to the Remedy server.
xii. Now remedy dll file need to be updated on the server running provider component. ScInteropRemedy63.dll file needs to be updated (if running ARS 6.3 only). For updating the dll file stop WMI service à go to %windows%\system32\wbem and replace the ScInteropRemedy63.dll. Reboot the server after overriding the file.
xiv. Check forwarding alerts to the Remedy server by right clicking on any alert in SCOM console à right click à forward to à opsmgr connector for BMC Remedy.
xvi. Check the status in Remedy for the ticket created against the alert.
xvii. Install SCOM 2007 R2 connector hotfix OM2007R2Connectors-KB2274165 on both provider and connector to stay updated.
Thanks,
Varun Kaura
No comments:
Post a Comment