Re-creating the Servers.xml file

In an upgrade scenario, the Servers.xml file is required to establish the relationship between your Content Platform Engine deployments and the configuration profiles. If the file is missing, you can create a new Servers.xml with your existing configuration information to complete the creation of an upgrade profile.

Symptoms

During an upgrade, when you try to create an upgrade profile from an existing profile, you discover that your Servers.xml file cannot be found. This prevents you from upgrading your existing profile.

If you cannot upgrade your existing profile, you must re-create the required configuration settings in a new profile. You are prevented from reusing your existing profile.

Resolving the problem

You can create a new Servers.xml that establishes the relationship between your Content Platform Engine deployments and your configuration profile.
  1. Use the appropriate sample to create an XML file.
  2. Add the details for your existing environment. You can find the settings for your Servers.xml file in the applicationserver.xml file in the profile that you want to use for the upgrade.

    WebSphere® Application Server

    The following table shows the properties that you must provide in the new Servers.xml file:
    Property in Servers.xml Notes
    profilePath= Fully qualified path to the configmgr profile that will be used to upgrade the deployment.
    ear= Fully qualified path to the location of the Engine-ws.ear file within the configmgr profile.
    version= Previously deployed major version of the Content Platform Engine. As examples (not a complete list): 5.2.1.0 or 5.2.1.7 or 5.5.0.0 or 5.5.2.0 or 5.5.4.0
    deployment= Valid values are: Standard, Cluster or Network
    <ws_server_name> Name of the Websphere 'target' that will host the FileNetEngine application deployment. Can be a single Websphere server instance or the name of a cluster (group of Websphere servers). ExamplesStandard: <ws_server_name>P8Node01Cell/P8Node01/server1</ws_server_name>Cluster: <ws_server_name>BackEnd1Cell02/CPEcluster</ws_server_name>Network: ws_server_name>BackEnd1Cell02/BackEnd1Node02/cpe1</ws_server_name>

    Samples

    Use the sample that fits your environment, and update the sample values to match the values from your environment:

    WebSphere Application Server, cluster deployment:
    <CEServers>
<server application="FileNetEngine" deployment="Cluster" ear="C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\CEConfig_WAScluster\ear\Engine-ws.ear" name="WS/CEConfig_WAScluster" profilePath="C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\CEConfig_WAScluster\CEConfig_WAScluster.cfgp" version="5.2.1.7">
        <ws_version>8.5</ws_version>
        <ws_install_root>C:\Program Files (x86)\IBM\WebSphere\AppServer</ws_install_root>
        <ws_user_install_root>C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\Dmgr01</ws_user_install_root>
        <ws_soap_port>8886</ws_soap_port>
        <ws_server_name>ywsBackEnd1Cell02/CPEcluster</ws_server_name>
    </server>
</CEServers>
    WebSphere Application Server, standard deployment:
    <?xml version="1.0" encoding="UTF-8"?>
<CEServers>
<server application="FileNetEngine" deployment="Standard" ear="C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\CEDeploy_WAS90_Standalone\ear\Engine-ws.ear" name="WS/CEDeploy_WAS90_Standalone" profilePath="C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\CEDeploy_WAS90_Standalone\CEDeploy_WAS90_Standalone.cfgp" version="5.5.5.0">
        <ws_version>9.0</ws_version>
        <ws_install_root>C:\Program Files\IBM\WebSphere\AppServer90</ws_install_root>
        <ws_user_install_root>C:\Program Files\IBM\WebSphere\AppServer90\profiles\Standalone01</ws_user_install_root>
        <ws_soap_port>8892</ws_soap_port>
        <ws_server_name>ywsBackEnd1Node02Cell/ywsBackEnd1Node03/STDCPE1</ws_server_name>
    </server>
</CEServers>

    WebLogic

    The following table shows the properties that you must provide in the new Servers.xml file:
    Property in Servers.xml Notes
    profilePath= Fully qualified path to the configmgr profile that will be used to upgrade the deployment. This is also where the WebLogic deployment plan.xml will be created by the configmgr.
    ear= Fully qualified path to the location of the Engine-wl.ear file within the configmgr profile.
    version= Previously deployed major version of the Content Platform Engine. For example: 5.2.1.0 or 5.5.0.0 or 5.5.2.0 or 5.5.4.0
    <ws_server_name> wl_server_name is the WebLogic 'target'. Can be a single WebLogic server instance or the name of a cluster (group of WebLogic servers). Examples:<wl_server_name>afire1.mylan.acme.com</wl_server_name> or<wl_server_name>CPEcluster</wl_server_name>or<wl_server_name>AdminServer</wl_server_name>

    Sample

    WebLogic, standard deployment:
    <?xml version="1.0" encoding="UTF-8"?>
<CEServers>
<server application="FileNetEngine" deployment="NA" ear="/opt/IBM/FileNet/ContentEngine/tools/configure/profiles/myProfile/ear/Engine-wl.ear" name="WL/myProfile" profilePath="/opt/IBM/FileNet/ContentEngine/tools/configure/profiles/myProfile/myProfile.cfgp" version="5.5.4.0">        
	<wl_version>12cR2(12.2.x)</wl_version>       
	<wl_system_install_root>/opt/app/oracle/product/FMW/Oracle_Home</wl_system_install_root>        
       <wl_domain_root>/opt/app/oracle/product/FMW/Oracle_Home/user_projects/domains/FNCM_domain</wl_domain_root>        
	<wl_soap_port>7001</wl_soap_port>        
	<wl_host_name>localhost</wl_host_name> 
	<wl_server_name>CPEcluster</wl_server_name>          
   </server>
</CEServers>