Integrations/bmc/bmc.pnet pimB

This page documents the enPortal integration for BMC ProactiveNet.

• Vendor: BMC Software
• Product: ProactiveNet Performance Management (BPPM)
• Supported Version(s): 8.6 - 9.5
• Name of enPortal Integration Package: bmc.pnet_pimB
• Required enPortal Version: 4.6.1 and above

The following section documents supported platforms, installation, and configuration of the ProactiveNet Product Integration Module on enPortal versions 5.0 and above.

Support Matrix

The following Operating System, Database, and Web Browser platforms are supported:

Operating System

Please see the list of supported Operating Systems on the System Requirements page.

Database

A special database is not required to implement this integration module. The AppBoard/enPortal database is used to store all configurations related to this integration module.

Web Browser

Please see the list of supported Web Browsers on the System Requirements page.

Installation

Perform the following steps to install the ProactiveNet PIM:

1. Install AppBoard/enPortal as detailed in the Installation documentation
2. Download the file bmc.pnet_pimB.jar
3. Start enPortal and login as an administrator
   1. User Name: administrator
   2. Password: administrator
   3. Domain: System
4. Under the Advanced tab, select PIMImport
5. Click the Browse... button
6. Locate the ProactiveNet PIM JAR file in the Open dialog
7. Click the Start button to extract the files from the PIM .jar archive
8. Under the Advanced tab, select XMLImport
9. Click the Start button to load the PIM into the system
10. Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_bmc.pnet_pimB.txt"
11. Re-start appboard to allow loading of java class for JNLP application
12. Under the Advanced tab, select Explore System
13. Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
14. Right-click on the “Manage Proxy” channel and select Open to launch the channel
15. In the Manage Proxy tool, click “Reset All”
16. Refresh the browser

Integration Details

The following sections provide special details for configuring the integration module after installation.

Channel Types

• Home - Channel that displays the default Home page for the logged in user, including full navigation controls (no custom configuration required)

• Proxy - Channel that is used by the system to display ProactiveNet channels (no custom configuration required)

• ManagementConsole - Channel that displays the SLO Management Console (HTML client)

• OperationConsole - Channel that displays the Operation Console (Flex client)

Configuration

After installing the ProactiveNet PIM, perform the following steps to configure access to the host ProactiveNet server:

1. Click on the Applications tab
2. Right-click on the name "sample" in the row for BMC ProactiveNet and select "Modify"
3. Fill in the items in the Modify Application Wizard dialog:
   1. Select the protocol used to access your ProactiveNet server (http or https)
   2. Change the host name from "changeme" to the hostname or ip address that will resolve to your ProactiveNet server
   3. Change the port to the port number of your ProactiveNet server
   4. Click "Save" to keep your changes
4. Click on the Integrations tab
5. In the Explorer, under Packages, expand the bmc.pnet_pimB tree and click on the Sample target. Confirm that the information you entered is displayed for your ProactiveNet server
6. Under the Sample target, click on the Home channel. A login prompt should be displayed.
7. Log in using the same credentials you would use for accessing the ProactiveNet application in a browser. Confirm that the ProactiveNet Home page is displayed.

Create Channels

After installing the ProactiveNet PIM and configuring access to the host ProactiveNet server, perform the following steps to create channels to display ProactiveNet content:

1. Click on the Applications tab
2. Right-click on the name "sample" in the row for BMC ProactiveNet and select a channel type
3. In the "Channel Name" box, enter the name you want to give to the new channel
4. For "Channel Type", select "3rd Party Pims"
5. Click Next
6. Click Finish
7. Click on the Integrations tab
8. In the Explorer, under Packages, expand the bmc.pnet_pimB tree and click on the Sample target. Confirm that the new channel is listed along with the other sample channels.

Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.

Known Issues

The following known issues are associated with this PIM:

• "Operational Console" is a flex application. The URLs are hard-coded by this flex application and enPortal is not able to modify its content or encode its URLs. For this Flex application, the "Change Console" and "Log Out" actions on the top menu are disabled by the PIM using a Javascript warning message. If the "Change Console" action is not disabled, its action will cause the BMC ProactiveNet content to pop out of enPortal's frame. If the "Log Out" action is not disabled, it will make enPortal unable to manage the Single Sign-on (SSO) session with the BMC ProactiveNet application.

• To access two different consoles in BMC ProactiveNet in enPortal, you can use the pre-built channels; one is "Operational Console" and the other is "Management Console". You will assign these two channels to an enPortal user (via his or her role). Then, the enPortal user will be able to access the same functionality as in the native application.

License Usage

In order for the AppBoard/enPortal administrator to configure the bmc.pnet_pimB PIM, the AppBoard/enPortal license.properties file must include licensing for at least one bmc.pnet_pimB server. The administrator can create one additional host ("target") in AppBoard/enPortal for each server license included in the license file.

Each AppBoard/enPortal user maintains one user session with the ProactiveNet server. The ProactiveNet application must be licensed to support the number of users that will be accessing the application through AppBoard/enPortal.

Version Support

The following matrix details the supported ProactiveNet and compatible AppBoard/enPortal versions:

Version Support

Package Name	enPortal Version	ProactiveNet Supported Versions
bmc.pnet_pimB	4.6.1+	8.6 - 9.5

To see the current enPortal version, run the portal version command from the [AppBoard_Home]/server/bin directory.

ProactiveNet Upgrades

Upgrading from an older version of ProactiveNet

Older versions of ProactiveNet are not supported by this PIM, so this upgrade path is not supported. It is recommended that you validate the PIM in your ProactiveNet environment to confirm that it supports the required functionalities.

Upgrading ProactiveNet to a newer version

Perform the following steps when the ProactiveNet server is upgraded to a newer version of ProactiveNet:

1. Check the AppBoard/enPortal PIM online documentation to see if the new ProactiveNet version is supported by the existing bmc.pnet_pimB PIM.
   1. To test if the new ProactiveNet version is supported by the existing PIM that you have installed, perform the following steps:
      1. Click on the Applications tab
      2. Right-click on the row for the old ProactiveNet server and select "Modify"
      3. Update the protocol, host, and port to reference the server where the new version of ProactiveNet is running
   2. If the new ProactiveNet version is not supported by the existing PIM that you have installed, perform the following steps to upgrade the PIM:
      1. Download the new PIM version from the PIM download site
      2. Follow the steps in the Installation section above to install and configure the new PIM version
      3. Re-create all ProactiveNet channels to reference the new PIM
      4. [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system

Uninstall

Uninstalling the bmc.pnet_pimB PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.

Perform the following steps to uninstall the bmc.pnet_pimB PIM:

1. Click on the Integrations tab
2. In the Explorer, under Packages, locate the bmc.pnet_pimB integration
3. Right click on the integration name, and select "Delete"
4. Click "Ok" to confirm that you want to delete the integration package