Integrations/hp/hp.bac.bpm pimB: Difference between revisions

imported>Cmace
(copied from internal)
 
imported>Jason.nicholls
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
This page documents the enPortal integration for HP Business Process Monitor (BPM).
{{DISPLAYTITLE:HP Business Process Monitor (BPM) for Business Availability Center (BAC)pimB}}
[[Category:Integrations]]
This page documents the enPortal integration for HP Business Process Monitor (BPM) [Business Availability Center (BAC)].


* <b>Vendor</b>: HP
* <b>Vendor</b>: HP
* <b>Product</b>: HP Business Process Monitor (BPM)
* <b>Product</b>: Business Process Monitor (BPM) [Business Availability Center (BAC)]
* <b>Supported Version(s)</b>: 9.10.450, Build 360  
* <b>Supported Version(s)</b>: 9.10.450, Build 360  
* <b>Name of enPortal Integration Package</b>: hp.bac.bpm_pimB.jar
* <b>Name of enPortal Integration Package</b>: hp.bac.bpm_pimB.jar
Line 46: Line 48:
# Click the <b>Start</b> button to load the PIM into the system
# Click the <b>Start</b> button to load the PIM into the system
# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_hp.bac.bpm_pimB.txt"
# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_hp.bac.bpm_pimB.txt"
 
# Under the <b>Advanced</b> tab, select <b>Explore System</b>
# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel
# In the Manage Proxy tool, click “Reset All”
# Refresh the browser


== Post Installation and Site specific customization ==
== Post Installation and Site specific customization ==

Latest revision as of 05:08, 25 July 2014

This page documents the enPortal integration for HP Business Process Monitor (BPM) [Business Availability Center (BAC)].

  • Vendor: HP
  • Product: Business Process Monitor (BPM) [Business Availability Center (BAC)]
  • Supported Version(s): 9.10.450, Build 360
  • Name of enPortal Integration Package: hp.bac.bpm_pimB.jar
  • Required enPortal Version: 4.5.2-20070711.0230 and above


The following section documents supported platforms, installation, and configuration of the HP BPM 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

Template-note.png
Due to the special nature of the BPM application, implementation of this PIM requires direct Edge access to the customer's instance of it for configuration. While this is not labor intensive, it requires either remote VPN access (preferred) or an onsite visit by Edge to the customer's location.

Perform the following steps to install the HP BPM PIM:

  1. Install AppBoard/enPortal as detailed in the Installation documentation
  2. Download the file hp.bac.bpm_pimB.jar
  3. Start AppBoard
  4. Log in to AppBoard as an administrator
    1. User Name: administrator
    2. Password: administrator
    3. Domain: System
  5. Under the Advanced tab, select PIMImport
  6. Click the Choose File button
  7. Locate the hp.bac.bpm_pimB.jar file in the Open dialog
  8. Click the Start button to extract the files from the PIM .jar archive
  9. Under the Advanced tab, select XMLImport
  10. Click the Start button to load the PIM into the system
  11. Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_hp.bac.bpm_pimB.txt"
  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

Post Installation and Site specific customization

Due to the Flash object used in this application, a few resources can not be handled automatically by enPortal CRS rules. The following tasks need to be performed in order for icons in the flash applications ("360 degree View", "EUM Application Support 360 by BPM", and "EUM Application Status" views) to show up correctly.

Without the following manual modification steps, an ActionScript Error popup box might show up and tree navigation icons will not be displayed when a user accesses "360 degree View", "EUM Application Support 360 by BPM", and "EUM Application Status" views.

The following customizations are site-specific and require some customization work.


  • Create a blank.html file in the /enportal context
    • Use a text editor to create a file named blank.html in ${ApplicationHome}/server/enportal directory with the following content:
<html>
<head>
<title>blank html</title>
</head>
<body>
</body>
</html>
  • Modify the runtime handler rule with the BPM's host and port and AppBoard's host and port:
    • Identify the exact fully-qualified URLs for the following four images. This can be done by using an HTTP protocol analyzer, such as Fiddler or Wireshark, to capture the AMF messaging when accessing the "360 degree View", "EUM Application Support 360 by BPM", and "EUM Application Status" views.
      • <ApplicationProtocol>://<ApplicationHost>:<ApplicationPort>/odb/icons/logical_application/logical_application_16.gif
        e.g. http://myservername.com:80/odb/icons/logical_application/logical_application_16.gif
      • <ApplicationProtocol>://<ApplicationHost>:<ApplicationPort>/odb/icons/business_transaction_flow/business_transaction_flow_16.gif
      • <ApplicationProtocol>://<ApplicationHost>:<ApplicationPort>/odb/icons/business_transaction/business_transaction_16.gif
      • <ApplicationProtocol>://<ApplicationHost>:<ApplicationPort>/odb/icons/logical_group/logical_group_16.gif
    • Identify AppBoard's protocol, host, and port information.
    • Use a text editor to open handlers.xml in the ${ApplicationHome}/server/enportal/webapps/enportal/WEB-INF/xmlroot/server/crs/runtimehandlers/hp/bac/bpm_pimB directory.
    • Locate the <ContentProcess id="adjustAMFStream"> rule block in the file.
    • Replace the four CRS stream replacement rules in the <ContentProcess id="adjustAMFStream"> rule block with the obtained information in the previous steps. Adjust the padding 'x' character to make the replaceValue's string length match exactly the matchText's string length.


Integration Details

This sections provides special details for configuring the integration module after installation.


Channel Types

  • Home - Channel that displays the entry page for BPM
  • Proxy - Channel that is used by the system to display BPM channels

Configuration

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

  1. Click on the Applications tab
  2. Right-click on the name "sample" in the row labeled "hp.bac.bpm_pimB" and select "Modify"
  3. Fill in the items in the Modify Application Wizard dialog:
    1. Select the protocol used to access your BPM server (http or https)
    2. Change the host name from "changeme" to the hostname or ip address that will resolve to your BPM server
    3. Change the port from "80" to the port number of your BPM server
    4. Click "Save"
  4. Click on the Integrations tab
    1. Confirm target information: In the Explorer, under Packages, expand the hp.bac.bpm_pimB tree and click on the Sample target. Confirm that the information you entered is displayed for your HP BPM server
  5. Launching the Home channel.
    1. Under the Sample target, click on the Home channel. A login prompt should be displayed.
    2. In the login prompt, enter the username and password along with the correct appRoot and clientType information. clientType should be consistent with the Home channel's web client type.
    3. Click on "OK" or the <enter> key.
  6. Confirm that the HP BPM Home page of the specified client type is displayed.

Create Channels

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

  1. Click on the Applications tab
  2. Right-click on the name "sample" in the row labeled "hp.bac.bpm_pimB" 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 hp.bac.bpm_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. Also follow the above "Configure Home channel" section to configure the newly created channel. Select a different Channel Type in step 2 to create a different type of channel.


Custom Channel Settings

There are no custom channel settings for the HP BPM PIM.


Known Issues

Apart from requiring to do site specific customization, there are no known issues associated with this PIM.

License Usage

In order for the AppBoard/enPortal administrator to configure the hp.bac.bpm_pimB PIM, the AppBoard/enPortal license.properties file must include licensing for at least one hp.bac.bpm_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 BPM server. The BPM 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 HP BPM and compatible AppBoard/enPortal versions:

Version Support
Package Name enPortal Version HP BPM Version
hp.bac.bpm_pimB 5.0+ HP Business Process Monitor version 9.10.450, Build 360
Template-tip.png
To see the current enPortal version, run the portal version command from the [Install_Home]/server/bin directory.

HP BPM Upgrades

Upgrading from an older version of BPM to BPM 9.10.450, Build 360

Older versions of HP BPM are not supported by this PIM, so this upgrade path is not supported.

Upgrading from HP BPM 9.10.450, Build 360 to a newer version of HP Business Process Monitor

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

  1. Check the AppBoard/enPortal PIM online documentation to see if the new BPM version is supported by the existing hp.bac.bpm_pimB PIM
    1. If the new BPM 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 HP Business Process Monitor server and select "Modify"
      3. Update the protocol, host, and port to reference the server where the new version of BPM is running
    2. If the new BPM 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 BPM 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

Template-warning.png
Uninstalling the hp.bac.bpm_pimB PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.

Perform the following steps to uninstall the hp.bac.bpm_pimB PIM:

  1. Click on the Integrations tab
  2. In the Explorer, under Packages, locate the hp.bac.bpm_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
  5. Manually delete default_handlers.xml in ${ApplicationHome}/webapps/enportal/WEB-INF/xmlroot/server/crs/defaulthandlers/hp/bac/bpm_pimB* directory