IBM FileNet P8 Process Engine 4.5.1.4-P8PE-FP004 Fix Pack Readme
© Copyright IBM Corporation 2013.

Readme file for: IBM® FileNet® P8 Process Engine
Update name: 4.5.1.4
Fix ID: 4.5.1.4-P8PE-FP004
Publication date: 22 May 2013
Last modified date: 22 May 2013

Contents

About this fix pack

Download location

Prerequisites

New in this fix pack

Compatibility

Known issues

Fix pack installation

Removing this fix pack

Redeploy the BPM Websphere Business Monitor application

Fix list (APARs)

Notices

Trademarks

Document change history

About this fix pack

The FileNet P8 Process Engine 4.5.1.4-P8PE-FP004 fix pack updates an existing Process Engine 4.5.1 system. Process Engine fix packs are cumulative and include fixes from all previously released fix packs since the base 4.5.1 release. You can safely install this fix pack even if you have virus protection software running in the background.

Download location

Click the following link to access the files for this fix pack server update: Fix Central for Fix Pack 4.5.1.4-P8PE-FP004. You need an IBM login and password to access this download location.

Prerequisites

This fix pack requires:

• P8PE 4.5.1

New in this fix pack

• Updates the Process Engine private JRE to IBM version 1.6.0 SR12 for fixes associated with an Oracle Critical Patch Update.
• Support for Mozilla Firefox version 17

Compatibility

For additional FileNet P8 compatibility information, see:

• IBM FileNet P8 Hardware and Software Requirements
• IBM FileNet P8 Fix Pack Compatibility Matrix

Introduced in Process Engine fix pack: 4.5.1.3-P8PE-FP003

• Provides a trusted version of signed client .jar files in order to support newer Java security requirements.
• The certificates used to sign the Process Engine jar files are renewed until February 19th, 2015.
• Provides ability to specify Adaptor Credentials for multiple Component Manager instances. See tech note 7022417.
• Provides support for WebSphere Business Monitor 7.5.1. However, the Alphablox-based Dimensions and Reports widget that is used for the dashboard is deprecated in IBM Business Monitor 7.5.1. To configure Alphablox with the Business Monitor, the service must be deployed according to the details in the Deploying Alphablox topic in the IBM Business Monitor Information Center.
• Provides support for Firefox 10.
• Updates the Process Engine private JRE to IBM version 1.6.0 SR10 to address a known Java "Denial of Service" security exposure. See Flash (Alert) 1472585
• Provides a security-related fix to the Process Engine search APIs.
• Process Engine REST enhancements for Process Engine 4.5.1. For additional details, see the technote 1460838.
• Jiglue module has been updated to fix APAR PJ39079. Refer to APAR (PJ39079) for details.
• A new optional parameter is available for the Process Task Manager (vworbbroker.ORBSvcConfDirective). This parameter was added to correct a known defect. See APAR (PJ38728) for details on how to enable the parameter.

Introduced in Process Engine fix pack: 4.5.1.2-P8PE-FP002

• Support for DB2 on zOS
• Beginning with this fix pack, a new vwlog parameter is provided to remove unnecessary system event records. Display details of the new parameter by typing "vwlog -h" in a command prompt. Refer to APAR (PJ38128) for details.
• Process Engine REST enhancements for Process Engine 4.5.1. For additional details, see the documentation: http://www.ibm.com/support/docview.wss?uid=swg21460838.
• Provides ability to specify Adaptor Credentials for multiple Component Manager instances See tech note 7022417.

Introduced in Process Engine fix pack: 4.5.1.1-P8PE-FP001

• A workflow dispatcher is now available for the WSRequest queue, which is enabled by default. To disable the workflow dispatcher for the WSRequest queue, pass in the following parameter into the Component Manager JRE using the Process Task Manager "Advanced" tab:
  -Dfilenet.pe.cm.adaptor.single.dispatcher.WSRequest=false
  (See APAR PJ37950. For additional details, see PJ37950 on the IBM web site at: http://www.ibm.com/support/docview.wss?uid=swg1PJ37950
• Updates the Process Engine client private JRE to version 1.6.0_SR08a
• Support for WebSphere Business Monitor 7.0
• This fix pack has been modified to enable handling of null user-defined fields in the event logs. An optional Java property can be set on the monitor server to prevent any null user-defined field from being included in CBE events.
  To set the optional Java property:
  1. In the administrative console menu, select Servers > Application Servers > server > Server Infrastructure > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties
     
  2. Click New to add the following property:
     
     • In the Name field enter: com.ibm.p8.bpm.cbe.adaptor.dropNullUDFValues.
       
     • In the Value field enter: true.

Known issues

• Beginning with fix pack 4.5.1.1-P8PE-FP001, work items in the CE_Operations queue that have invalid expressions log errors into the Windows Event Viewer or the IS elog, instead of preventing the CE_Operations queue from processing other items (PJ37964). Consequently, if not handled, the errors can fill the log. The entries look similar to this:
  

  VW (Region=700): Param Error IN Wob#: E91EDD7FBE68914B9E011655862DADFD, WC class#: 17, ISid#: -2, WOId#:23, setStringProperty, destDocument [[Err=d52d03fa] subscript out of range]

  These invalid work items must be removed from the system by an administrator.

• Two fixes require the use of vwtool to enable server tracing:
  • APAR PJ37731 addresses an error message which might occur when trying to expose a field to the roster.
  • APAR PJ40853 addresses a transfer failure when using the "import overwrite" feature of Process Configuration Console (PCC) to add and remove the exposed fields to a Queue and Event log.

  To enable these fixes, use vwtool to enable server tracing:
  

  1. From a command line, run vwtool.
  2. In vwtool, run trace to enable tracing. Save the results to a log file.
  3. Enable tracing for 'Transfer' only.
  4. After tracing is enabled, retry the transfer from the Process Configuration Console in order to add the exposed data field.
  5. After the transfer is complete and successful, disable the tracing using vwtool.
     Enabling the transfer trace also turns on extra error detection and processing code, which assists in correcting the problem. Once corrected, the problem should not occur on subsequent transfers.

Fix pack installation

Prepare for the installation

Before installing this fix pack, create a full backup of Process Engine using your normal backup procedures.

Stop all running software

Before installing this fix pack, you must stop all running software, including software on other servers that might be communicating with Process Engine or the Process Engine database.

1. Determine the Process Engine user name. When Process Engine was installed, either the default fnsw user name was used or an alias was assigned. You will need this user name in order to stop and start the Process Engine software.
2. Log on as a user with the appropriate stop privileges for the components listed in step 3. For more information about user logons, see the tasks for Installing Process Engine on various platforms in the FileNet P8 Platform 4.5.x Installation and Upgrade Guide.
3. Stop the following components if they are running:
• Process Simulator
• Process Analyzer
• Component Manager
• Content Engine
• Process Service
• Process Task Manager

For more information on stopping the IBM FileNet P8 4.5 software, see the IBM FileNet P8 help topic in FileNet P8 Administration > Enterprise-wide Administration > Shutdown and Startup.

4. Close any active windows that display the log files.
5. After you have stopped all FileNet P8 software, open a command prompt and type the following:

Windows killfnsw -D -y -S

UNIX killfnsw -DAyS or killfnsw -D -A -y -S

6. (AIX only) Type the following:

slibclean

7. (UNIX only) Type the following command to locate any Java processes that are still running:

   ps -ef | grep /fnsw/java

8. Stop any FileNet P8 Java processes.
9. If you are installing Process Engine server files in a clustered configuration, disable the replication before installing the fix pack.
10. Proceed to Update Process Engine server files.

Update Process Engine server files

Install the fix pack on the Process Engine as follows:

1. Verify that there is a current backup, as directed in Prepare for the installation.
2. Log on to the server as the root user (UNIX) or a user with administrator privileges (Windows).
3. Unzip or untar the fix pack file for your system:
   • 4.5.1.4-P8PE-FP004-AIX.tar.gz (AIX)
   • 4.5.1.4-P8PE-FP004-HPUX.tar.gz (HP-UX PA-RISC)
   • 4.5.1.4-P8PE-FP004-HPXI.tar.gz (HP-UX Integrity)
   • 4.5.1.4-P8PE-FP004-SOL.tar.gz (Solaris)
   • 4.5.1.4-P8PE-FP004-WIN.zip (Windows)
4. Install the 4.5.1.4-P8PE-FP004 fix pack server files interactively or silently as follows:
   • To install the fix pack interactively
     1. Run 4.5.1.4-P8PE-FP004 and follow the wizard screens.
     2. Click Install when prompted.
   • To install the fix pack server files silently
   1. Edit the PE_silent_install.txt response file to reflect the entries for your installation.
   2. Save the edited response file to a temporary directory.
   3. Navigate to the directory where you downloaded the fix pack and run the following command:

      4.5.1.4-P8PE-Operating System-FP004 .bin or .exe -silent -options PE_silent_install.txt

   4. If you are prompted to do so, restart the computer.
5. Log on as fnsw (or fnsw alias if an alias was used when you installed Process Engine) and enter the following command to restart the Process Engine software:

   initfnsw -y restart

6. If this was the last Process Engine node to be updated in a clustered configuration, re-enable replication for the cluster.
7. Proceed to Run the Process Engine client installer.

Run the Process Engine client installer

Run the Process Engine client installer that is shipped with this fix pack to synchronize the version of Process Engine files on all other servers where Process Engine client software is installed. Do not update Process Engine client files to this fix pack level if you have not already updated Process Engine server.

You must run the installer once on each of the other servers. Perform one or more of the following procedures, depending on which applications run in your environment.

• Run the Process Engine client installer on the Content Engine server
• Run the Process Engine client installer on the Application Engine, Workplace XT, or Records Manager servers
• Run the Process Engine client installer on Process Simulator
• Run the Process Engine client installer on Process Analyzer
• Run the Process Engine client installer on other application servers
• Run the Process Engine client installer for JiGlue

In some cases, multiple applications will reside on the same server. An example of this would be if Records Manager were collocated with Application Engine. To update multiple applications at the same time, select all collocated applications on the Product Selection screen.

Run the Process Engine client installer on the Content Engine server

To install the Process Engine client files, perform the following steps on all Content Engine servers. Except where noted, the steps apply to WebSphere, WebLogic, and JBoss.

1. Log on to the Content Engine server as a user who has permission to install software.
2. Perform standard back up procedures to back up the system.
3. Select the TAR or ZIP file that is appropriate for your operating system and download it to Content Engine server. Unzip or untar the fix pack file for your system to a local directory:
   • 4.5.1.4-P8PE-Client-FP004-AIX.tar.gz (AIX)
   • 4.5.1.4-P8PE-Client-FP004-HPUX.tar.gz (HP-UX PA-RISC)
   • 4.5.1.4-P8PE-Client-FP004-HPXI.tar.gz (HP-UX Integrity)
   • 4.5.1.4-P8PE-Client-FP004-LINUX.tar.gz (Linux)
   • 4.5.1.4-P8PE-Client-FP004-SOL.tar.gz (Solaris)
   • 4.5.1.4-P8PE-Client-FP004-WIN.zip (Windows)
   • 4.5.1.4-P8PE-Client-FP004-ZLINUX.tar.gz (Linux on zSeries)
4. Close all instances of Enterprise Manager and any other Content Engine client applications, such as Application Engine. From the application server administrative console:
   • WebSphere Stop and uninstall the FileNet Content Engine Application (Engine-ws.ear).
   • WebLogic Stop and un-deploy the FileNet Content Engine Application (Engine-wl.ear).
   • JBoss Execute the shutdown command (it is not necessary to undeploy).
5. (WebLogic only) Delete the application server cache directories shown in the following tables, substituting your domain name and machine name in place of mydomain and myserver, respectively:

   Operating system	Cache directories to delete
   UNIX	/opt/bea/user_projects/domains/mydomain/servers/AdminServer/tmp/_WL_user\Engine-wl /opt/bea/user_projects/domains/mydomain/servers/AdminServer/cache/EJBCompilerCache
   Windows	C:\bea\user_projects\domains\mydomain\servers\AdminServer\tmp\_WL_user\Engine-wl C:\bea\user_projects\domains\mydomain\servers\AdminServer\cache\EJBCompilerCache

   
   
6. Run the Process Engine client installer interactively or silently. To run silently, see Run the Process Engine client installer silently section. After running silently, continue to Step 8 to complete the update on the Content Engine server.
7. Complete the Installer screens as follows:

   In this screen...	Perform this action...
   Products to Update	Select Content Engine
   Stop Running Software	If prompted, stop all running software components
   Installation Summary	Validate that the information displayed is correct and that there is enough space to complete the installation.
   Software Components	Select the software components to automatically start after the installation is complete.

   
   
8. Redeploy the Content Engine application. Refer to the latest version of the FileNet P8 4.5.x Platform Installation and Upgrade Guide for specifics on deploying the Content Engine on specific application server types.
9. Proceed to update the Process Engine client files on other applicable servers.

Run the Process Engine client installer on the Application Engine, Workplace XT, or Records Manager servers

To install the Process Engine client files, perform the following steps on all servers that apply, including application servers where Records Manager applications (such as the Sweep and File Plan Import and Export tools), are installed. Except where noted, the steps apply to WebSphere, WebLogic, and JBoss.

1. Log on to the server as a user with permission to install software.
2. Back up the deployed web application directory for Application Engine, Workplace XT, or Records Manager applications.
3. Select the TAR or ZIP file that is appropriate for your operating system and download it to Content Engine server. Unzip or untar the fix pack file for your system to a local directory:
   • 4.5.1.4-P8PE-Client-FP004-AIX.tar.gz (AIX)
   • 4.5.1.4-P8PE-Client-FP004-HPUX.tar.gz (HP-UX PA-RISC)
   • 4.5.1.4-P8PE-Client-FP004-HPXI.tar.gz (HP-UX Integrity)
   • 4.5.1.4-P8PE-Client-FP004-LINUX.tar.gz (Linux)
   • 4.5.1.4-P8PE-Client-FP004-SOL.tar.gz (Solaris)
   • 4.5.1.4-P8PE-Client-FP004-WIN.zip (Windows)
   • 4.5.1.4-P8PE-Client-FP004-ZLINUX.tar.gz (Linux on zSeries)
4. If Component Manager is running, go to the Process Task Manager application to stop it, then close Process Task Manager.
5. (Windows only) From the Windows Services Console, stop the Process Application Engine Services Manager Service (for Application Engine) or the Process WP XT Services Manager (for Workplace XT).
6. To retain your existing configurations, copy the following configuration files from the backup copy of your deployed Application Engine, Workplace XT, or Records Manager application to the /WEB-INF directory in the installed directory on your application server, overwriting the existing installed files. You must do this before you apply the fix pack to the existing Application Engine, Workplace XT, or Records Manager installation. Copy the existing configuration files as follows:
   
   • Application Engine
     Copy the WcmApiConfig.properties and the web.xml files from the /WEB-INF folder in the backed-up Workplace directory created in Step 2 to the following directory: AE_install_path/Workplace/WEB-INF/
     
   • Workplace XT
     Copy the WcmApiConfig.properties and the web.xml files from the /WEB-INF folder in the backed-up Workplace XT directory created in Step 2 to the following directory: WPXT_install_path/WorkplaceXT/WEB-INF/
     
   • Records Manager
     Copy the WcmApiConfig.properties and the web.xml files from the /WEB-INF folder in the backed-up Records Manager directory created in Step 2 to the following directory: RM_install_path/RecordsManager/WEB-INF/
     
     The backup of these files is to ensure that the files are still available in case there is any reason to revert to the previous versions. When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.
     

7. (WebSphere and WebLogic Only) Stop and undeploy any instances of Application Engine, Workplace XT, or Records Manager.
8. (JBoss Only) Execute the shutdown command.
9. Delete the Workplace temp directory. The following paths are examples.

   WebSphere 6.0.x, 6.1.x, 7.0.x

      <WebSphere_HOME>/profiles/<ProfileName>/temp/<node_name>/<server>/<instance>/<Workplace_application_name>

   JBoss

      <JBoss_home>/server/server_name/tmp/deploy
      <JBoss_home>/server/server_name/work/jboss.web/localhost

   WebLogic 9.0.x, 10.0.x

      <BEA_HOME>/user_projects/domains/<Domain_Name>/servers/AdminServer/tmp/_WL_user/<Workplace_application_name>

10. Run the appropriate Process Engine client installer either interactively or silently. To run silently, see Run the Process Engine client installer silently. After running silently, continue at Step 12 here to complete the update on these servers.
11. Complete the Installer screens as follows:

    In this screen...	Perform this action...
    Products to Update	Select the appropriate software to update. For example: Application Engine, WPXT, or Records Manager.
    Stop Running Software	If prompted, stop all running software components.
    Installation Summary	Validate that the information displayed is correct and that there is enough disk space to complete the installation.
    Software Components	Select the software components to automatically start after the installation is complete.

    
    
12. Redeploy the appropriate applications. For instructions, refer to the latest version of the documentation that applies to your application.

    Application	Documentation
    Application Engine	FileNet P8 Platform Installation and Upgrade Guide
    Workplace XT	IBM FileNet Workplace XT Installation Guide
    Records Manager	FileNet Records Manager Installation and Upgrade Guide

    
    
13. (Windows only) From the Windows Services Console, restart the Process Application Engine Services Manager Service (for Application Engine) or the Process Workplace XT Services Manager (for Workplace XT). Restart Process Task Manager and Component Manager.
14. If necessary, restart Component Manager from Process Task Manager, and then exit the Process Task Manager application.
15. Repeat this procedure on other servers that are running Application Engine, Workplace XT, or Records Manager applications.
16. Proceed to update the Process Engine client files on other applicable servers.

Run the Process Engine client installer on Process Simulator:

1. Stop Process Simulator.
2. Close the Process Task Manager.
3. Stop the Process Simulator Services Manager services.
4. Unzip the 4.5.1.4-P8PE-Client-FP004-WIN.zip file and run the 4.5.1.4-P8PE-Client-WIN-FP004.exe file.
5. When prompted, enter the location for the Process Engine client installer (for example: C:\Program Files\FileNet\PEClient).
6. Select Process Simulator as the product to update, then click Next.
7. When the installation is complete click Next, then Finish.

           After the installation:

1. Start Process Simulator Services Manager service.
2. Start the Process Simulator.

Run the Process Engine client installer on Process Analyzer:

1. Stop Process Analyzer.
2. Close the Process Task Manager.
3. Stop the Process Analyzer Services Manager services.
4. Unzip the 4.5.1.4-P8PE-Client-FP004-WIN.zip file and run the 4.5.1.4-P8PE-Client-WIN-FP004.exe file.
5. When prompted, enter the location for the Process Engine client installer.
6. Select Process Analyzer as the product to update, then click Next.
7. When the installation is complete click Next, then Finish.

           After the installation:

1. Start Process Analyzer Services Manager service.
2. Start the Process Analyzer.

Run the Process Engine client installer on other application servers

By selecting the 'Other' option in the Process Engine client installer Product Selection screen you can specify where to copy all of the new Process Engine client files. You can then manually update the appropriate files in any installed and deployed locations for other servers where Process Engine client software is installed. You can use this option can if the Process Engine client installer does not recognize that a supported product is installed.

Use the following steps to update other servers where Process Engine client software is installed, including Business Process Framework and any custom applications:

1. Log on to the server as a user with permission to install software.
2. Back up the system using your normal backup procedures.
3. Select the TAR or ZIP file that is appropriate for your operating system and download it to Content Engine server. Unzip or untar the fix pack file for your system to a local directory:
   • 4.5.1.4-P8PE-Client-FP004-AIX.tar.gz (AIX)
   • 4.5.1.4-P8PE-Client-FP004-HPUX.tar.gz (HP-UX PA-RISC)
   • 4.5.1.4-P8PE-Client-FP004-HPXI.tar.gz (HP-UX Integrity)
   • 4.5.1.4-P8PE-Client-FP004-LINUX.tar.gz (Linux)
   • 4.5.1.4-P8PE-Client-FP004-SOL.tar.gz (Solaris)
   • 4.5.1.4-P8PE-Client-FP004-WIN.zip (Windows)
   • 4.5.1.4-P8PE-Client-FP004-ZLINUX.tar.gz (Linux on zSeries)
4. From Process Task Manager, stop Component Manager, if running, and then close the Process Task Manager application.
5. (Windows only) From the Windows Services Console, stop the Process Application Engine Services Manager Service (for Application Engine) or the Process WP XT Services Manager (for Workplace XT).
6. (WebSphere and WebLogic Only) Stop and undeploy any instances of Application Engine, Workplace XT, or Records Manager.
7. (JBoss Only) Stop the JBoss server.
8. Delete the web application temporary directories associated with these applications.
9. Run the Process Engine client installer either interactively or silently. To run silently, see Run the Process Engine client installer silently. After running silently, continue from Step 11 to complete the update on these servers.
10. Complete the Setup screens as follows:
    

    In this screen...	Perform this action...
    Products to Update	Select Other.
    Installation Directory	Specify the directory to which the Process Engine client files will be copied.
    Stop Running Software	If prompted, stop all running software components.
    Installation Summary	Validate that the information displayed is correct and that there is enough space to complete the installation.
    Software Components	Select the software components to automatically start after the installation is complete.

    
    
11. Update all Process Engine client files in the existing product installation and deployed directories.

    Note Replace files inside any EAR and WAR files that are used by the applications.

12. Redeploy the product. Refer to the applicable installation guide for each product.
13. Proceed to update the Process Engine client files on other applicable servers.

Run the Process Engine client installer for JiGlue

Complete the following steps to update the version of JiGlue.

1. Shut down all client applications using JiGlue.
2. Backup the existing jiglue.dll and jiglue.tlb files currently deployed on the system.
3. Download and unzip 4.5.1.4-P8PE-Client-FP004-WIN.zip and run the 4.5.1.4-P8PE-CLIENT-WIN-FP004.EXE file.
4. When prompted, enter the location for the Process Engine client installer (for example: C:\Program Files\IBM\FileNet\BPMClient).
5. Select "Other" as the product to update, and specify a folder location for the files to be copied to. This copies all of the Process Engine client files. Only the jiglue.dll and the jiglue.tlb files are used.
6. Unregister the existing jiglue.dll by running: regsvr32 /u jiglue.dll.
7. Copy the new jiglue.dll and jiglue.tlb from the above location (Step 5) to where the existing jiglue.dll and jiglue.tlb were deployed.
8. Register the new jiglue.dll by running: regsvr32 jiglue.dll.

Run the Process Engine client installer silently

1. Follow the instructions in the PEClient_silent_install.txt file to modify the input information for the component on which you want to install the Process Engine client files.
2. Run the Process Engine Client installer with the following arguments:

   UNIX 4.5.1.4-P8PE-CLIENT-operating system-FP004.BIN -silent -options path/PEClient_silent_install.txt

   Windows 4.5.1.4-P8PE-CLIENT-WIN-FP004.exe -silent -options path\PEClient_silent_install.txt

Debug memory segmentation violations (Optional)

After a migration from P8 3.5 to P8 4.5.1, Process Engine might experience outages due to memory segmentation violations. A debug module, libvwalloc.dbg, is now provided that resolves the problem.

1. Verify that the libvwalloc.dbg exists in the \fnsw\lib\shobj folder.
2. Back up the libvwalloc.so file in the \fnsw\lib\shobj folder.
3. Stop FileNet P8 software on Process Engine and other FileNet P8 components.
   1. Stop all process routers running on FileNet P8 components and close any Workplace applications.
   2. Log on to Process Engine as the fnsw user (UNIX).
   3. Start Process Task Manager, if it is not already running:

      UNIX Enter vwtaskman from the command prompt.

   4. Stop the Process Service by selecting the appropriate node and clicking Stop.
   5. Close Process Task Manager.
   6. Run the following commands to fully stop Image Services:

      initfnsw -y stop
      killfnsw -DASy

   7. AIX As the root user, run slibclean.
4. In the \fnsw\lib\shobj folder, replace the libvwalloc.so module with the corresponding module libvwalloc.dbg

   UNIX As the fnsw user, run fn_setup -d / to reset permissions on the new modules.

5. Restart the Process Service on the Process Engine server.
   1. Start Process Task Manager.
   2. Select the Process Service node and click Start.

Removing this fix pack

This fix pack does not have an uninstall option.

Redeploy the BPM Websphere Business Monitor application

The following procedure provides instructions to redeploy the CBE adaptor and monitor model provided in this fix pack. The procedure to recreate the monitor model using the BPMMonitoring.zip provided in this fix pack can be found in the System Administration > Process Engine Administration > Workflow administration tasks > Analyze workflows > WebSphere Business Monitor integration section of the IBM P8 Online Documentation section.

If necessary, regenerate the CBE data on the Process Engine server using the steps provided in the Process Engine installation section of this readme.

Uninstallation of the existing applications on the WebSphere Business Monitor Server

To uninstall the Common Based Events (CBE) application with the administrative console:

1. In the administrative console menu, select Applications > Enterprise Applications.
2. Select the check box for the application 'P8 BPM CBE Adaptor'.
3. Stop the application.
4. Save the configuration.
5. Select the check box for the application 'P8 BPM CBE Adaptor'.
6. Click Uninstall.
7. Save the configuration.

To uninstall the monitor model, follow the section "Removing monitor models and data" from this link:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.btools.help.monitor.admin.doc/admin/admin_deploy.html

Installation of the applications on the WebSphere Business Monitor Server

To install the CBE application with the administrative console, follow these steps:

1. In the administrative console menu, select Applications > Enterprise Applications.
2. Click Install.
3. Browse to location of the new P8BPMCBEAdaptor.ear.
4. Accept the defaults for the installation.
5. Click Finish.
6. Click Save directly to Master Configuration.

If application security is enabled, complete the following steps to grant the CBE Adaptor access to the CEI Event service

1. Choose a user account for the CBE Adaptor to use to access the event service.
2. Grant the CBE Adaptor user account access to all of the event service security roles.
   1. Navigate to the CEI Event service. Select Service Integration > Common Event Infrastructure > Event Service > Security role to user/group mapping.
   2. Ensure that the CBE Adaptor user account is mapped to the event service security roles.
3. Configure Security role to user/group mapping for the CBE Adaptor.
   1. In the administrative console menu, select Applications > Enterprise Applications > P8 BPM CBE Adaptor.
   2. Click Security role to user/group mapping.
   3. Map the CBE Adaptor user account to CBEAdaptorSecurityRole.
   4. Click OK.
   5. Save the configuration
4. Configure the User RunAs roles for the CBE Adaptor.
   
   1. In the administrative console menu, select Applications > Enterprise Applications > P8 BPM CBE Adaptor.
   2. Click User RunAs roles.
   3. Enter a username and password for the CBE Adaptor user account.
   4. Select CBEAdaptorSecurityRole.
   5. Click Apply.
   6. Click OK.
   7. Click Save directly to the Master Configuration.

   To install the newly created monitor model, follow the section "Installing a monitor model" from this link:
   http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.btools.help.monitor.admin.doc/admin/admin_deploy.html

Fix list (APARs)

The following tables list the product fixes in this Process Engine server fix pack update.

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
J74/G4
555 Bailey Avenue
San Jose, CA 95141
U.S.A.  

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan  

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
U.S.A.  

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.

Document change history