Predeployment Considerations
Mis à jour: octobre 2009
S'applique à: Operations Manager 2007 R2
For a successful deployment, your systems must meet each of the following requirements:
Computer Running Operations Manager
Windows Server 2003 with SP1 or Windows Server 2008
System Center Operations Manager 2007 R2
Microsoft SQL Server 2005 SP3
Microsoft .NET Framework 3.0 SP1
Microsoft Visual C++ 2008 Redistributable Package, English version
WS-Management 1.1
Windows-Based IBM Tivoli Enterprise Console Computers
Windows Server 2003 with SP1
Microsoft Visual C++ 2008 Redistributable Package, English version
WS-Management 1.1
Notes
You must install the Interop Provider on the primary management server, before you install the Connector Service.
UNIX-Based IBM Tivoli Enterprise Console Computers
The following tables describe the required UNIX operating systems and package dependencies.
IBM AIX 5L 5.3
| Required Package | Description | Minimum Version |
|---|---|---|
OS version |
Version of the operating system |
AIX 5.3, Technology Level 6, Service Pack 5 |
xlC.rte |
XL C/C++ Runtime |
9.0.0.2 |
openssl.base |
OpenSSL Libraries; Secure Network Communications Protocol |
0.9.8.4 |
Solaris 10 SPARC
| Required Package | Description | Minimum Version |
|---|---|---|
Required OS patch |
PAM memory leak |
117463-05 |
SUNWlibC |
Sun Workshop Compilers Bundled libC (sparc) |
5.10, REV=2004.12.22 |
SUNWlibms |
Math & Microtasking Libraries (Usr) (sparc) |
5.10, REV=2004.11.23 |
SUNWlibmsr |
Math & Microtasking Libraries (Root) (sparc) |
5.10, REV=2004.11.23 |
SUNWcslr |
Core Solaris Libraries (Root) (sparc) |
11.10.0, REV=2005.01.21.15.53 |
SUNWcsl |
Core Solaris Libraries (Root) (sparc) |
11.10.0, REV=2005.01.21.15.53 |
OpenSSL |
SUNopenssl-librararies (Usr) Sun provides the OpenSSL libraries for Solaris 10 SPARC. They are bundled with the operating system. |
11.10.0,REV=2005.01.21.15.53 |
PAM |
Pluggable Authentication Modules SUNWcsr, Core Solaris, (Root) (sparc) |
11.10.0, REV=2005.01.21.15.53 |
When you forward alerts to a TEC Server that is running on the Windows operating system, you must set the TEC Server Port on the Connector Configuration UI to the specific port on which TEC is listening. The connector is set up to work with UNIX-based or Linux-based TEC Servers that use the UNIX PortMapper to determine TEC’s port. A TEC Server that is running on Windows uses a hard-coded port, which, by default, is set to 5529. You must set the TEC Server port to the specific port on which TEC is listening and then restart the Connector Service.
Setting a Server Listening Port
Configuring the server listening port is necessary for a successful operation.
To set server listening port
In the Operations Manager Console, click the Administration pane.
Under Product Connectors, click IBM Tivoli Enterprise Console Connector.
Right-click the connector name, and then click Properties.
In the Properties dialog box popup window, click the TEC Server Settings tab.
In the Server listening Port box, enter 5529 (or the port TEC is listening on if not the default), and then click OK.
You must restart the Connector for the update to take effect.
To restart the IBM Tivoli Enterprise Console Connector
Click the Start button, point to Administrative Tools, and then click Services.
Select Operations Manager for IBM Tivoli Enterprise Console Connector and click Restart the service.
Click Done.
Installation Overview
For a successful installation, you must follow these steps.
Ensure that your systems meet all of the prerequisites for the Interop Provider, the Connector Service, and the Connector Configuration user interface (UI).
Install the Interop Provider.
Perform the required setup and configuration on the remote Enterprise Management System (EMS).
Configure the IBM Tivoli Enterprise Console.
Install the Connector Service and the Connector Configuration UI.
Notes
If your systems meet all prerequisites, and all connector components are configured correctly, the connector should be fully functional.
Modify the connector configuration to meet the needs of your enterprise by using the Connector Configuration UI.