Readme file for: IBM® FileNet® P8 Content Engine
Update name: 4.5.1.8-P8CE
Fix ID: 4.5.1.8-P8CE-IF001
Publication date: 14 August 2015
Last modified date: 14 August 2015
This interim fix provides resigned .jar certificates for a specific IBM FileNet P8 Content Engine release. The files provided in this interim fix are Content Engine built JAR files, but only need to be applied on the Application Server of Content Engine web based client applications, such as the Application Engine, and custom Java applications using the Content Engine Java client API. Verify that resigned JAR files from other engines (specifically, the Application Engine and Process Engine) are applied, based on the version of those products.
The new certificates are required with Java v1.7.0_051 and higher. Java v1.7.0_051 and newer produce an error, and older Java versions have a warning with expired certificates. If the certificates have expired, for Java releases prior to 1.7.0_051 a warning will occur which you can ignore and continue. For 1.7.0_051 and higher with expired certificates, an error occurs, and you can not continue.
This interim fix also updates the Content Engine "engine-xx.ear" file, where "xx" represents the Content Engine application server type (ws, wl, jb, or jbc).
This interim fix requires:
Click the following link to access the files for this Interim Fix server update: Fix Central for Interim Fix 4.5.1.8-P8CE-IF001. You need an IBM login and password to access this download location.
Support documentation
Before installing this interim fix, verify that you have access to the IBM FileNet P8 Knowledge Center at:http://www.ibm.com/support/knowledgecenter/SSNW2F_4.5.1/welcome.html. The P8 Knowledge Center contains additional information that you might need to perform the procedures included in this readme, such as stopping services and applications.
Installation of this software requires Administrator privileges.
There are three sections for installing this interim fix:
In environments where there is more than one Content Engine server running in the P8 domain, the Content Engine nodes might be set up in either a managed or non-managed configuration.
When you deploy Content Engine in a "managed" application server environment, this Content Engine fix pack is installed and configured on the administration server. The Configuration Manager uses the application server administration server tools to deploy the Content Engine EAR file to the managed servers. This is known as a "managed" deployment.
When you deploy Content Engine in a "non-managed" application server environment, this Content Engine fix pack is installed and configured on an initial server in the environment. After configuring the bootstrapped Content Engine EAR file on the initial server, you will be directed to copy the bootstrapped EAR file to each of the other servers and deploy the bootstrapped EAR file on all of the servers.
This interim fix updates the Content Engine "engine-xx.ear" file, where "xx" represents the Content Engine application server. Installing this interim fix on the Content Engine server consists of the following tasks:
Complete the following tasks to prepare the Content Engine server for this interim fix.
Important Failure to make a backup of the existing bootstrapped Content Engine EAR file can have serious repercussions on the operation of Content Engine if you accidentally delete or overwrite the existing bootstrapped Content Engine EAR file during the installation of this fix pack. A common symptom of a deleted or an overwritten bootstrapped EAR file is that system users cannot log on to Content Engine and they will not be able to log on until that file is restored. If this situation occurs, you will need a backup to recover.
You can determine the location of the existing bootstrapped EAR file for Content Engine by viewing the contents of the Servers.xml file, which is in the ce_install_path directory.
Complete the following tasks to install this interim fix.
Navigate to the temporary directory where you extracted the contents of this interim fix.
ce_install_path\lib
ce_install_path/lib
After you have installed the Content Engine server software, configure it using the steps in this section:
Removing a deployed Content Engine
Removing the application server cache directories
Completing Configuration Manager tasks
To help prevent errors when redeploying the updated version of Content Engine, remove the previously deployed copy of Content Engine from the application server before deploying the updated Content Engine. See the following topics for more information on specific application servers.
Use the administrative console to uninstall the "FileNetEngine" enterprise application. This action deletes the Engine-ws.ear file from IBM WebSphere Application Server.
Use the Change Center in the administrative console to delete the "FileNetEngine" application. This action deletes the Engine-wl.ear file from Oracle WebLogic Server.
Based on your "Standard or Cluster" deployment, remove the Engine-jb.ear file or Engine-jbc.ear file from one of the following directories, where jboss_install_directory is the JBoss installation directory and custom_name is the name of a user-defined directory.
jboss_install_directory\server\default\deploy
jboss_install_directory\server\custom_name\deploy
jboss_install_directory\server\all\deploy
To help prevent errors when redeploying the updated version of Content Engine, remove the application server cache as described in the following topics.
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\temp\node_name\server_name\FileNetEngine
Where:
C:\bea\user_projects\domains\mydomain\servers\AdminServer\tmp\_WL_user\FileNetEngine
C:\bea\user_projects\domains\mydomain\servers\AdminServer\cache\EJBCompilerCache
Where mydomain is the name of the Content Engine application server instance.
jboss_install_directory\server\default\tmp\deploy
jboss_install_directory\server\default\work\jboss.web\localhost\FileNet
jboss_install_directory\server\custom_name\tmp\deploy
jboss_install_directory\server\custom_name\work\jboss.web\localhost\FileNet
jboss_install_directory\server\all\tmp\deploy
jboss_install_directory\server\all\work\jboss.web\localhost\FileNet
You can use either the graphical user interface or the command line interface to bootstrap and deploy Content Engine. Choose one of the following links to complete the Configuration Manager tasks in this section.
Completing Configuration Manager tasks using the graphical user interface
Completing Configuration Manager tasks using the command line interface
Complete the following tasks in the order shown to set up and deploy the Content Engine from the graphical user interface.
Select Start > All Programs > IBM FileNet P8 Platform > FileNet Configuration Manager or run the following command: ce_install_path\tools\configure\configmgr.exe.
Run the following command from the command line: ce_install_path/tools/configure/configmgr.
Complete the following stpes to update or verify the Content Engine bootstrap information.
Important The default value is Configure New, but you must change it to Upgrade.
If your configuration uses Process Engine, complete the steps in this section, otherwise continue with the Configuring the Content Search Engine files on Content Engine section.
This step updates the recently bootstrapped Engine-xx.ear file with the Process Engine client.
Locate the Process Engine client installation program that correlates with the version of your Process Engine server and follow the directions associated with that version of the Process Engine client.
Tip Run the Process Engine installation program only once on the Content Engine server because the Process Engine client installation program detects all EAR files and updates them all at one time.
If your configuration uses Content Search Engine, complete the steps in this section, otherwise continue with the Copying the bootstrapped Content Engine EAR file to the remaining application servers section.
Complete the following procedure to install the latest Content Search Engine client files into the updated Engine-xx.ear file.
NETWORK NOTE If Content Engine uses a central application server (which might manage other application servers), install the latest Content Search Engine client files on only the central application server. If Content Engine uses multiple non-managed stand-alone application servers, install the latest Content Search Engine client files on only one application server. (You will be directed to copy this information to the other application servers later in this readme.)
MULTIPLE FILENET P8 DOMAINS NOTE Complete this task only once on each Content Engine server because the Content Search Engine client installation program detects all EAR files and updates them all at one time.
(Multiple non-managed stand-alone application servers only) Copy the bootstrapped Content Engine EAR file into the profiles directory (where 4.5.1.7-P8CE was originally bootstrapped) on each of the remaining Content Engine application servers in your P8 domain. For example:
ce_install_path\tools\configure\profiles\myprofile\ear
(JBoss Application server only) Based on your "Standard or Cluster" deployment, remove the Engine-jb.ear file or Engine-jbc.ear file from one of the following directories, where jboss_install_directory is the JBoss installation directory and custom_name is the name of a user-defined directory.
Standard deployment
jboss_install_directory\server\default\deploy
jboss_install_directory\server\custom_name\deploy
Cluster deployment
jboss_install_directory\server\all\deploy
The location where you copy the bootstrapped Content Engine EAR file is referred to as the "bootstrapped EAR path." You must enter this path when you deploy the Content Engine EAR file on the remaining application servers.
Stop and restart all servers and clusters where the Content Engine EAR file has been deployed.
Start all servers and clusters where the Content Engine EAR file has been deployed.
Installation of the Content Engine interim fix is now complete. Continue with Verifying the deployment of the updated Content Engine EAR file.
Complete the following procedure to specify setup information and deploy Content Engine from the command line interface.
configmgr_cl listServers
configmgr_cl generateupgrade [-appserver app_server_type] -server server_name [-deploy deploy_type] -profile myprofile [-silent] [-force] [-help]
If a message indicates that a profile already exists, record the profile name. Use this profile name in places where this readme references myprofile.
The following table lists the descriptions for the configmgr_cl generateupgrade command parameters:
| Parameter | Description |
|---|---|
| -appserver appserver_type | Required only if the ce_install_path/Servers.xml file does not exist or does not contain any servers. This parameter specifies the type of application server and must be one of the following values: WebSphere, WebLogic, or JBoss. |
| -server server_name | Indicates the server for which the upgrade profile is being created. Run the configmgr_cl listServers command to display a list of valid server name values before you run the generateupgrade command. |
| -deploy deploy_type | Type of deployment.
Required if the Servers.xml file does not exist or does not contain a deployment type for the selected server. If the Servers.xml file already has a deployment type for the selected server, then the value from the Servers.xml file is used instead of the value you specify on the command line.
|
| -profile myprofile | The myprofile value can be one of the following items:
If the path includes a directory name with spaces, enclose the entire path in quotation marks. For example, enter "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfgp". |
| -silent | When -silent is specified, no prompts or informational messages display in the console, but errors are written to the log. Failure messages and validation error messages display as needed, such as messages about missing passwords or invalid port numbers.
If you run the execute command to run all the tasks in a profile, and you specify the -silent parameter, you must also specify the -force parameter. The -silent parameter is optional. |
| -force | When -force is specified, the command is forced to continue running while in silent mode. Requires -silent. |
| -help | When -help is specified, a brief message describing the command syntax displays; the command does not run. |
<propertyname="ApplicationServerAdminUsername">
<value>administrator_user_name</value>
</property>
<property name="ApplicationServerInstallationFolder">
<value>/opt/IBM/WebSphere/AppServer</value>
<description>Enter the absolute path to the directory where the WebSphere Application Server is installed.</description>
<displayName>Application server installation directory</displayName>
</property>
<property name="ApplicationServerProfileFolder">
<value>/opt/IBM/profiles/AppSrv01</value>
<description>Enter the absolute path to the directory where the WebSphere Application Server profile for Content Engine is stored. If you are installing Content Engine on a node in a cluster or on a managed server node and Deployment Manager is remote from Configuration Manager, use the directory for the WebSphere profile that is on the node. </description>
<displayName>Application server profile directory</displayName>
</property>
configmgr_cl storepasswords -profile myprofile
configmgr_cl generateConfig -task configurebootstrap -profile myprofile -bootstrap upgrade -appserver appserver_type
The -appserver appserver_type parameter specifies the application server type. Valid values are: WebSphere, WebLogic, or JBoss.
The -profile myprofile parameter specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.
The bootstrap information is stored in the configurebootstrap.xml and the deployapplication.xml files. Each time the bootstrap information is generated, the system saves a unique version of the file. The initial file name is configurebootstrap.xml; subsequent file names are configurebootstrap.n.xml where "n" starts with 1 and represents the version number of each file.
configmgr_cl execute -task configurebootstrap -profile myprofile
Status messages display in the console.
JBoss example: <configuration class="com.ibm.ecm.configmgr.product.ce.task.UpgradeJBBootstrap">
configmgr_cl execute -task configurebootstrap -profile myprofile -taskfile configurebootstrap.2.xml
Status messages display in the console.
configmgr_cl checkStatus -task configurebootstrap -profile myprofile -taskfile configurebootstrap.n.xml
where:
-profile myprofile specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.
-taskfile configurebootstrap.n.xml specifies the version of the file to use. Omit this parameter if only one version of the task file exists.
ce_install_path\tools\configure\profiles\myprofile\ear
The location you select is referred to as the "bootstrapped EAR path." You must enter this path when you deploy the Content Engine EAR file on the remaining application servers.
configmgr_cl execute -task deployapplication -profile myprofile
where:
-profile myprofile specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.
configmgr_cl checkstatus -task deployapplication -profile myprofile
where:
-profile myprofile specifies the profile name. If a profile already exists, use the name that you recorded earlier in this procedure.
Complete the following procedure to verify that Content Engine deployed successfully:
http://server:port/FileNet/Engine
where:
server is the host name of the machine where Content Engine is deployed.
port is the HTTP port used by the Web application server on the machine where Content Engine is deployed.
The defaults for the application server HTTP port number are as listed:
Install the .JAR files in two locations on the Application Engine Server: the download directory and the installation directory.
WebSphere 6.0.x, 6.1.x, 7.0.x
WebLogic 9.0.x, 10.0.x
JBoss
WebSphere 6.0.x, 6.1.x, 7.0.x
WebLogic 9.0.x, 10.0.x
JBoss
IMPORTANT Rebooting the FileNet P8 system or restarting the FileNet P8 services without applying the required FileNet P8 fixes on all machines might cause the system to become out of synch with the other FileNet P8 machines. Having an unsynchronized FileNet P8 environment can cause problems because FileNet P8 processes might automatically restart before the complete FileNet P8 environment has been updated.
Tip Do not install the resigned jars on the Process Engine. This is not necessary and can cause a communication issue between Process Engine and Content Engine.
After installing this interim fix, if you need to restore Application Engine and/or any specific custom application changes to their previous condition, use the backed up copy of the .jar files.
The following table lists the product fixes this interim fix.
| APAR |
Description |
|---|---|
PJ43032 |
PSIRT 1220 (CVE-2013-5452) - XML External Entity (XXE) injection vulnerabilities. See techdoc 1699588 |
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.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
| Date |
Description |
|---|---|
| 14 August 2015 |
Initial release of interim fix. |