Follow the installation procedure appropriate for your operating system to use Oracle as the backend database for BMC ProactiveNet.
Notes
Before you begin
Ensure that port 7 is opened between the BMC ProctiveNet Server and Oracle database system.
For more information about creating an Oracle database instance for the BMC ProactiveNet Server, see Creating an Oracle database instance for the BMC ProactiveNet Server.
To install BMC ProactiveNet Server with Oracle as database
Access the installation program by using one of these methods:
On the Configuring Firewall Rules page, perform one of the following tasks, and click Next. You must configure firewall rules to allow BMC ProactiveNet processes to communicate through the firewall.
Note
If you turn on the firewall when Remote Desktop Protocol is running, the Remote Desktop Protocol session may get disconnected if Remote Desktop Protocol is blocked by the firewall.
To automatically configure the Windows Firewall rules, select Automatically configure Windows Firewall Rules.
The Windows Firewall inbound rules are configured. An error message appears if you have not started the Windows Firewall.
Note
Ensure that you start the Windows Firewall before you configure the Windows Firewall rules. For more information about starting the Windows Firewall, see To start Windows Firewall.
(Cluster environment only) On the Cluster Group Configuration page, select the type of the cluster group in which to install the BMC ProactiveNet Server, Default cluster group or Custom cluster group. Note BMC recommends you to install the BMC ProactiveNet Server using a custom cluster group. Ensure that the custom cluster group is already created and the cluster is working in the specified group. The custom cluster group name must be same as the custom cluster name.
On the Directory Selection page, retain the default directory (\Program Files\BMC Software\ProactiveNet), or click Browse to select a different directory, and click Next.
Warning
Select the tasks that you want to configure with BMC ProactiveNet, and click Next. The following figure displays the default tasks that are selected. If you decide not to configure ports or cell details and have not selected either Server Ports - Change defaults, Cell - Change defaults, or both the options under System Configuration Tasks in the Configuration task selection page, the Confirm Defaults page is displayed with the default cell or port details. Otherwise, the Configure Server Ports page is displayed.
Configuration task selection
On the Confirm Defaults page, click Next.
If you have selected Server Ports - Change defaults under System Configuration Tasks in the Configuration task selection page, on the Configure Server Ports page, update the following port numbers, and click Next.Port name Description Apache Port Used by the BMC ProactiveNet Operations Console and web services. The default port number is 80. Apache SSL Port Used by the BMC ProactiveNet Operations Console for secure channel access. The default port number is 443. AgentController Port Used by the Agent Controller. The default port number is 12123. BMC Impact Admin Server Port Used by BMC Impact Admin Server clients to communicate with BMC Impact Admin Server. The default port number is 3084. Remote Method Invocation Port Used by the BMC ProactiveNet Operations Console. The default port is 1099. BMC Remedy Service Desk Port Used by the Integration for BMC Remedy Service Desk service if BMC Atrium CMDB integration is enabled. The default port number is 3115.
On the Configuring BMC ProactiveNet environment deployment information page, select any one of the following options based on your BMC ProactiveNet environment.
Single Server Environment Installation
Installing BMC ProactiveNet Server with Central Monitoring Administration
Multiple Server Environment Installation
Installing BMC ProactiveNet Central Server with Central Monitoring Administration
OR
Installing BMC ProactiveNet Child Server
Configuring BMC ProactiveNet environment deployment information
If you have selected Disaster Recovery Mode - Enable under System Configuration Tasks in the Configuration task selection page , on the Configuring Disaster Recovery page, enter a valid host name alias to configure disaster recovery, and click Next. The default host name alias is pronet.
If you have selected Cell - Change defaults under System Configuration Tasks in the Configuration task selection page, on the Configuring Cell page, enter the following details, and click Next.Field Description BMC ProactiveNet cell details Instance Name Name of the cell instance. The default is pncell_hostname.
If you are configuring BMC ProactiveNet for disaster recovery, do not change the default cell name.Port Port number in the range of 1024 to 65535. The default port for the cell is 1828. Encryption Key Encryption key for the cell. The default is mc. No special characters are allowed. Admin cell details Port Port number for the Admin cell. The default is 1827. Encryption Key Encryption key for the Admin cell. The default is mc.
If you have selected Administrator e-mail from BMC ProactiveNet - Change defaults under System Configuration Tasks in the Configuration task selection page, on the Administrator Information page, enter the following details to receive e-mail notifications from the BMC ProactiveNet Server, and click Next.Field Description Sender E-mail ID Email address that you specify as the sender of any notification e-mail messages. The format for the e-mail address must be hostName@company.com The administrator receiving the email message will know which host is having disk space problems or other issues that send notifications. The default value is blank. Administrator E-Mail ID Fully qualified e-mail address of the administrator of the BMC ProactiveNet Server. The format for the e-mail address must be user@company.com. The default value is blank. Name or IP Address of SMTP Server Name or IP address of the SMTP server. The default value is blank.
On the Configure Database page, provide the following details, and click Next.
Field | Description |
---|---|
Database | |
Standalone or RAC |
Notes When you provide the RAC SCAN host name, the pw dbconfig list displays the node count as 1 and node 1 is the SCAN host. |
Tablespace and Users | |
Use Existing User or Create New User |
|
Username | User name of the database instance for the BMC ProactiveNet user. Do not use the terms "sys" or "system." The default user name is proact. |
Password | Password of the database instance for the BMC ProactiveNet user |
Confirm Password | Password of the database instance for the BMC ProactiveNet user |
On the Configure Oracle Report User page, provide the following details, and click Next.
Field | Description |
---|---|
User Name | User name of the database instance that will view the default views and create reports in Oracle. |
Password | Password for this Oracle user |
If you have selected Create New User in the Configure Database page, on the Tablespaces and Users Settings page, provide the following details, and click Next:
Note
Before you create a tablespace, see Manual steps to set up an Oracle database.
Note
Only one data file is added to the tablespace created by the script. However, if required, you can add additional data files to the same tablespace before the tablespace is filled up. For information about adding additional data files, see Extending the tablespace.
Field | Description |
---|---|
Oracle DBA Username | Oracle database user name. The user must have SYSDBA privileges. |
Oracle DBA Password | Password for the Oracle DBA user name |
Deployment Type | Type of BMC ProactiveNet deployment. The size of the tablespace is determined by the type of deployment. The supported values are as follows:
|
Main Table Space Name | Name of the main tablespace to be created |
Temporary Tablespace Name | Name of the temporary tablespace to be created |
Main Tablespace Data File Name | Data file name with the absolute path for the main tablespace |
Temporary Tablespace Data File Name | Data file name with the absolute path for the temporary tablespace |
If you have selected Atrium CMDB - Enable and Configure under Integration Configuration Tasks in the Configuration task selection page, on the Integrating with CMDB page, provide the following details, and click Next. Warning Before you configure BMC Atrium CMDB, ensure that BMC ProactiveNet CMDB Extensions and modules are installed on the computer where the BMC Atrium CMDB is installed. If necessary, you can stop this installation, install the extensions, and then restart the BMC ProactiveNet Server installation. For information about installing the BMC ProactiveNet CMDB Extensions, see Preparing for installation Note Configuring the BMC ProactiveNet Server for integration with BMC Atrium CMDB is recommended, but not mandatory, during installation. If you do not configure the BMC ProactiveNet Server for CMDB integration during installation, you can manually configure BMC Atrium CMDB integration any time after the installation is complete. For instructions, see Configuring BMC Atrium CMDB integration. Note The UDDI parameters are optional and used only for enabling the cross-launch to other BMC products such as Atrium AE and BMC Atrium Service Context. If you integrate with BMC Atrium CMDB in the AR Server Group, you must manually configure the pserver.conf file. Edit the Field Description CMDB Host Host name of the AR Server. When integrating with the AR Server group, host name of the Load Balancer or Integration Server. CMDB Port BMC Atrium CMDB or AR System Server port number. The default is 0. If the AR System is configured with a Portmapper, enter port 0. CMDB User User name required to log on to the AR System Server. The default is Demo. This user requires the AR Server Administration rights. CMDB Password Password required to log on to the AR System server UDDI Host Host name of the UDDI registry for BMC Atrium CMDB UDDI Port Port number of the UDDI registry for CMDB. The default is 8080. UDDI User UDDI registry user name. The default is admin. UDDI Password Password for the specified UDDI user name. The default is admin. ARSGroupMembers
in the pserver.conf file and set to all AR Servers of the group that have reconciliation function enabled. See also Configuring the Publishing Server to integrate with an AR Server group.
If you have selected BMC Server Automation - Enable and configure under Integration Configuration Tasks in the Configuration task selection page, on the Connecting to BMC Server Automation page, provide the following details, and click Next. These inputs will be used for both cross-launch and BMC Server Automation integration.Field Description User User name for the BMC Server Automation server Password Password for the BMC Server Automation server Role Role that is defined to grant permissions to the BMC Server Automation user. The default is BLAdmins. Using UDDI Server By default, the Using UDDI Server check box is selected. If you have provided the UDDI details on the Integrating with CMDB page, the UDDI details are automatically populated. If you do not use the UDDI server, clear Using UDDI Server. UDDI Host Host name of the UDDI registry UDDI Port Port number of the UDDI registry. The default is 8080. UDDI User UDDI registry user name. The default is admin. UDDI Password Password for the specified UDDI user name. The default is admin. Application server BMC Server Automation application server name. The field is applicable only when you have cleared Using UDDI Server. Web service port Web service port number required to connect to the BMC Server Automation server. The default web service port number is 9843. The field is applicable only when you have cleared Using UDDI Server.
If you have selected Single Sign On (SSO) - Enable and Configure under Integration Configuration Tasks in the Configuration task selection page, on the Atrium SSO Information page, provide the following details, and click Next. Note The BMC ProactiveNet Server installer prompts for details that are already defined in BMC Atrium SSO. For more information about installing and configuring BMC Atrium SSO, see Configuring Single Sign-On. Note BMC ProactiveNet Single Sign-On (SSO) integration can also be configured post installation in one of two ways:Field Description Atrium SSO Server FQDN Fully qualified name of the SSO Server ProactiveNet Server FQDN Fully qualified host name of the server where BMC ProactiveNet Server is installed. By default, the host name of the server on which the BMC ProactiveNet Server is installed is displayed. Atrium SSO HTTPS Port BMC Atrium SSO secure port number. The default port number is 8443. Searcher ID Username created in the SSO Server and to which the 'BmcSearchAdmin' group is assigned. It is used to search all user names and groups available in the SSO Server for authentication. Searcher Password Password of the Searcher ID user that you entered in the above field. Atrium SSO AmAdmin Password BMC Atrium SSO Server AmAdmin password that you have entered while installing BMC Atrium SSO.
On the Installation Preview page, click Install. The Preview page displays the Installation Mode as Standalone in a case of regular installation and High-Availability (Cluster) if you installing in the high availability mode. The BMC ProactiveNet Server installation process takes a while to complete. After a successful installation, a command line prompt is displayed with a list of the pw server processes that started running.
On the Installation Summary window, select View Logs to open the installation logs, or click Done to complete the installation. Note If the DNS configurations are not correct in a computer, a warning message, No DNS Entry Found, is displayed. You can either correct the DNS configuration and restart the installation, or if you want to continue with the installation, provide the IP address instead of the host name when you are required to enter the host name.
For more information about creating and setting up the Oracle database, see Steps to run the BMC provided script set_system_parameter_oracle_pnet.sql.
netsh advfirewall set allprofiles state on
netsh firewall set opmode mode = ENABLE
netsh advfirewall set allprofiles state on
netsh firewall set opmode mode = ENABLE
Configuring multiple BMC ProactiveNet Child Servers to connect to the same Oracle database
1 Comment
Julien Flamez