Page tree

Skip to end of metadata
Go to start of metadata

This section provides instructions for installing the BMC ProactiveNet Server on Microsoft Windows with Sybase as database. If you are upgrading from an earlier version, see Upgrading BMC ProactiveNet Server. 

Before you begin

  • Ensure that there are no BMC ProactiveNet Integration Services installed on the computer where the BMC ProactiveNet Server will be installed. If any BMC ProactiveNet Integration Services are installed on this computer, the BMC ProactiveNet Server installation fails.
  • Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in System requirements and product compatibility.
  • Ensure that the computer on which you are installing the product adheres to the requirements described in Preparing for your installation.
  • If you are using the Remote Desktop Connection (RDC) to install the product, then the RDC must be in console mode.
  • Ensure that .NET Framework version 3.0 is installed. If you are using Windows 2008, use the Role Management tool. For more information about how to install the .NET Framework, see the Microsoft website.

To install the BMC ProactiveNet Server with Sybase as database

  1. Access the installation program by using one of these methods:

  2. Extract the contents of the zipped distribution file to an appropriate directory on the computer where the BMC ProactiveNet Server is upgraded.
  3. Open the install.cmd file with the Run as administrator option.
  4. On the Welcome page, click Next.

  5. On the license agreement page, select I agree to the terms of the license agreement, and click Next.

  6. 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.

      • To manually configure the firewall rules, select I will manually configure Windows Firewall Rules now before proceeding further
        • For more information about creating Windows Firewall inbound rules, see To manually configure Windows Firewall inbound rules.
        • If you prefer to use a third party firewall application, which is installed on your computer, ensure that you manually create the firewall inbound rules. For more information about creating firewall inbound rules, refer to the documentation of the third party firewall application.
  7. (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.

  8. 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

    • Do not install BMC ProactiveNet Server in a root directory (for example C: or D: ), on a shared drive, or in the Documents and Settings folder.
    • While installing BMC ProactiveNet Server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.
  9. Select the tasks that you want to configure with BMC ProactiveNet, and click Next. The following figure displays the default tasks that are selected.


    Configuration task selection


    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.

  10. On the Confirm Defaults page, click Next.

  11. 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 nameDescription
    Apache PortUsed 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 PortUsed by the Agent Controller. The default port number is 12123.
    BMC Impact Admin Server PortUsed by BMC Impact Admin Server clients to communicate with BMC Impact Admin Server. The default port number is 3084.
    Remote Method Invocation PortUsed by the BMC ProactiveNet Operations Console. The default port is 1099.
    BMC Remedy Service Desk PortUsed by the Integration for BMC Remedy Service Desk service if BMC Atrium CMDB integration is enabled. The default port number is 3115.

  12. 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

  13. 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.
  14. 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.

    FieldDescription
    BMC ProactiveNet cell details
    Instance NameName 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.
    PortPort number in the range of 1024 to 65535. The default port for the cell is 1828.
    Encryption KeyEncryption key for the cell. The default is mc. No special characters are allowed.
    Admin cell details
    PortPort number for the Admin cell. The default is 1827.
    Encryption KeyEncryption key for the Admin cell. The default is mc.
  15. 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.

    FieldDescription
    Sender E-mail IDEmail 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 IDFully 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.
  16. If you have selected Configure to use an Oracle database (Separately Installed) under Database in the Configuration task selection page, see Installing BMC ProactiveNet Server with Oracle as the database. Otherwise, Sybase will be configured, which is integrated with BMC ProactiveNet.

     

     

    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.

    FieldDescription
    CMDB HostHost name of the AR Server. When integrating with the AR Server group, host name of the Load Balancer or Integration Server. 
    CMDB PortBMC 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 UserUser name required to log on to the AR System Server. The default is Demo. This user requires the AR Server Administration rights.
    CMDB PasswordPassword required to log on to the AR System server
    UDDI HostHost name of the UDDI registry for BMC Atrium CMDB
    UDDI PortPort number of the UDDI registry for CMDB. The default is 8080.
    UDDI UserUDDI registry user name. The default is admin.
    UDDI PasswordPassword for the specified UDDI user name. The default is admin.

    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 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.

  17. 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.

    FieldDescription
    UserUser name for the BMC Server Automation server
    PasswordPassword for the BMC Server Automation server
    RoleRole that is defined to grant permissions to the BMC Server Automation user. The default is BLAdmins.
    Using UDDI ServerBy 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 HostHost name of the UDDI registry
    UDDI PortPort number of the UDDI registry. The default is 8080.
    UDDI UserUDDI registry user name. The default is admin.
    UDDI PasswordPassword for the specified UDDI user name. The default is admin.
    Application serverBMC Server Automation application server name. The field is applicable only when you have cleared Using UDDI Server.
    Web service portWeb 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.
  18. 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.

    FieldDescription
    Atrium SSO Server FQDNFully qualified name of the SSO Server
    ProactiveNet Server FQDNFully 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 PortBMC Atrium SSO secure port number. The default port number is 8443.
    Searcher IDUsername 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 PasswordPassword of the Searcher ID user that you entered in the above field.
    Atrium SSO AmAdmin PasswordBMC Atrium SSO Server AmAdmin password that you have entered while installing BMC Atrium SSO.

    Note

    BMC ProactiveNet Single Sign-On (SSO) integration can also be configured post installation in one of two ways:

  19. 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.

  20. 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.

 

To start the Windows Firewall

  1. Start the Windows Firewall service from services.msc.
  2. Run the following commands to turn on the firewall:
    • (Microsoft Windows 2008 R2) netsh advfirewall set allprofiles state on
    • (Microsoft Windows 2008) netsh firewall set opmode mode = ENABLE
    • (Microsoft Windows 2012 R2) netsh advfirewall set allprofiles state on
    • (Microsoft Windows 2012) netsh firewall set opmode mode = ENABLE

To manually configure Windows Firewall inbound rules

  1. Start the Windows Firewall, as described in To start Windows Firewall.
  2. Configure the Windows Firewall inbound rules for the following pw processes. For more information about configuring Windows Firewall inbound rules, see To create an inbound firewall rule for a program or service from the Microsoft Technet Library:
    • pw/jre/bin/java_jboss.exe
    • pw/apache/bin/httpd.exe
    • pw/jre/bin/java_jsrv.exe
    • pw/jre/bin/java_agent.exe
    • pw/jre/bin/java_cntl.exe
    • pw/jre/bin/java_tunnel.exe
    • pw/jre/bin/java_rate.exe
    • pw/jre/bin/java_ps.exe
    • pw/Sybase/bin64/dbsrv16.exe
    • pw/server/bin/mcell.exe
    • pw/pronto/bin/ProactiveNetService.exe
    • pw/pronto/bin/ProNetAgent.exe
  • No labels