Upgrade P8 FileNet Platform to 5.2.1 FP5

Here is how to upgrade P8 FileNet Platform 5.2.1 to 5.2.1 FP5 silently. This upgrades both the server and the client.

You need FileNet 5.2.1 to upgrade to 5.2.1 FP 5. Here is a way to install FileNet 5.2.1.

You can execute this in the same directory you copied and

# WebSphere profile path
export was=/opt/IBM/WebSphere/AppServer/profiles/AppSrv01
# WebSphere node
export wasNode=P8Node01
# WebSphere server
export wasServer=server1
# WebSphere Admin's username
# WebSphere Admin's password

# Install de CPE Fix Pack
tar -xzf -C
sed -i "s/LICENSE_ACCEPTED=false/LICENSE_ACCEPTED=true/g" ce_silent_install.txt
./ -f ce_silent_install.txt -i silent
cd ..

# Install de Client Fix Pack
tar -xzf -C
sed -i "s/LICENSE_ACCEPTED=false/LICENSE_ACCEPTED=true/g" ceclient_silent_install.txt
# Disable all components
sed -i "s/UPDATE_\([A-Z0-9]\+\)=1/UPDATE_\1=0/g" ceclient_silent_install.txt
# Enable ICN, you can activate toehr the same way here if you need
sed -i "s/UPDATE_CN=0/UPDATE_CN=1/" ceclient_silent_install.txt
./ -f ceclient_silent_install.txt -i silent
cd ..

# Uninstall FileNetEngine so we can redeploy it 
cat <<EOF > uninstall_jenkins.jython

$was/../../bin/wsadmin.sh -lang jython -conntype SOAP -username $wasUsername -password $wasPassword -f uninstall_jenkins.jython
rm -rf uninstall_jenkins.jython

# Delete WAS cache for FileNetEngine
rm -rf $was/temp/$wasNode/$wasServer/FileNetEngine

# Then redo the configuration tasks to redeploy the upgraded FileNetEngine
/opt/IBM/FileNet/ContentEngine/tools/configure/configmgr_cl generateupgrade -deploy Standard -server DeployCE -profile /opt/IBM/cpit/install-scripts/profiles/DeployCE -silent -force
# I don't think we need to set the license again when deploying but keeping it here just in case
#configmgr_cl generateconfig -appserver WebSphere -task task_type -license "PVU Non-Production" -profile /opt/IBM/cpit/install-scripts/profiles/DeployCE

/opt/IBM/FileNet/ContentEngine/tools/configure/configmgr_cl execute -task configurebootstrap -profile /opt/IBM/cpit/install-scripts/profiles/DeployCE

# This is required to switch to standard mode instead of network, because the deployment script acts for
# network deployment strangly like if it was a cluster development, looking for DEPLOYMENT_MANAGER server
# and that fails since of course we have only a APPLICATION_SERVER
# Generating the profile with -deploy Standard does not fix the problem I tried as well
sed -i 's/implementorid="nd"/implementorid="standard"/' /opt/IBM/cpit/install-scripts/profiles/DeployCE/deployapplication.xml

/opt/IBM/FileNet/ContentEngine/tools/configure/configmgr_cl execute -task deployapplication -profile /opt/IBM/cpit/install-scripts/profiles/DeployCE

# Restarting WAS
$was/bin/stopServer.sh $wasServer -username $wasUsername -password $wasPassword
$was/bin/startServer.sh $wasServer

Leave a Reply