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:
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 NONINFRINGEMENT, 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.
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.
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.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to
change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
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.
If you are viewing this information soft copy, the photographs and color illustrations
may not appear.
Preface -
This white paper assumes you have a good understanding and know the
concepts of migration. If you are not sure, please review the general
concepts of migration at the below provided location –
SPECIAL NOTE: If you are using this guide on an operating system that is
different than the example documented, some allowances must be made to
convert commands and screens shown to your environment. This might
include changing executable script commands from batch files (.bat) to shell
scripts (.sh) or vice versa, or when using command-line utilities in place of
graphical interfaces that might be shown.
NOTE: Migrating to the empty portal 7 is not supported. Also private wires
doesn't get migrated
• When migrating from version 5.1 you must first migrate to WebSphere
Portal version 6.1. We recommend migrating to version 6.1.0.4 or later.
• Once you have migrated to WebSphere Portal version 6.1.0.4 or later,
you then migrate your data and portlets to version 7.0.
Important: Migration is supported only from the two latest fix pack levels for
any listed offering. For example, if you are using WebSphere Portal Version
6.1.0.1, and the two latest available fix packs are 6.1.0.4 and 6.1.0.5, you
must apply one of those fix packs before you can migrate to Version 7.0.
Important Note: You cannot upgrade the source portal with a fixpack after
migration if you intend to re-migrate the JCR. For example, if your source
portal is running Version 6.1.0.4 and you migrate the portal to Version 7.0,
you cannot then upgrade the source portal to Version 6.1.0.5 and migrate the
JCR again. This is not supported.
WebSphere Portal Version 7.0 does not support SUSE SLES 9. If your earlier
portal runs on SLES 9, you need to upgrade to SUSE SLES 10 before
migrating to WebSphere Portal Version 7.0.
If using a 32–bit database driver on a 64–bit machine, will need to use the 32–
bit WebSphere Application Server Network Deployment Version 7
Supplements Disc 2
If using a 64–bit database driver on a 64–bit machine, will need to use the 64–
bit WebSphere Application Server Network Deployment Version 7
Supplements Disc 2
General Note: Portlets and components in the source version are typically
not migrated if they are not available in the version to which you are migrating.
Examples include the MarketWatch portlets, Domino Document Manager
portlet, Inline QuickPlaces portlet, Microsoft Exchange 2000 portlets, and
portlets that were developed using WebSphere Portal Application Integrator
(WPAI).
Also, migrated elements are not automatically upgraded to use features that
are available in the new version. Taking advantage of new functionality that
was not available in the source portal requires additional attention after
migration is complete.
Chapter 1
Introduction
This White paper describes the steps and best practices for migrating an
existing Standalone WebSphere Portal 6.1.0.5 + WebSphere Application
Server (WAS) 6.1.x environment to Standalone WebSphere Portal V7. To
help illustrate the steps involved in this process, the migration of the yourCo
Financial’s (Figure 1-1) portal is described.
Here are the following assumptions taken into considerations in this case
study.
Both WebSphere Portal V.6.1.0.5 and V.7 servers are stand-alone servers.
Pre-migration tasks -
○ Migration is supported only from the two latest fix pack levels
for any listed offering. So if you don't have the latest fix pack
then install it so before moving forward.
ConfigEngine.bat validate-database-connection
-DtransferDomainList=release,jcr
Note - The users that are considered “dead users”, their artifacts will
not be migrated. This is how the migration scripts have been designed.
Hence, if you want the artifacts of the dead users to be migrated over,
administrator needs to re-enable the users that are marked as dead
users. This should be simple as administrator can just reactivate them
via LDAP.
2. If you are migrating from source portal server which have feature pack
installed (for instance, Version 6.1.5, 6.1.5.1, 6.1.5.2) , you must
manually update the getNlsStrings.js file in Web Content Management
to work correctly with the Version 7.0 portal.
a. On the source server, click Applications -> Content -> Web
Content Management.
b. In the authoring portlet, click Edit Shared Settings.
c. Add the blog library to the authoring portlet.
i. Click Library Selection.
ii. Select Blog Resources from the list of available libraries,
and click Add.
iii. Click OK.
d. Update the getNlsStrings.js file.
i. Download the new version of the getNlsStrings.js file from
the WebSphere Portal product documentation.
ii. Ensure that the Blog Resources library is selected in the
Library drop-down menu.
iii. Select Components.
iv. Select the check box for FILE - Get NLS Strings JS, and
click Edit.
v. In the File Resource Element section, click Browse and
navigate to the updated getNlsStrings.js file that you
downloaded.
vi. Click Save and read to update the file and verify your
changes.
Note: If you do not update the getNlsStrings.js file before migration, the
browser might display this error when displaying a blog or wiki page:
ibmPortalConfig is not defined. If the error occurs after you update the
getNlsStrings.js file, you might need to clear the browser's cache or
delete any temporary internet files to ensure that the latest version of
the file is loaded from the server.
● WebSphere Portal 7 -
○ Upgrade the target server to the latest fix pack level. Here is the link
to the list of recommended fix packs and interim fixes -- http://www-
01.ibm.com/support/docview.wss?rs=688&uid=swg27007603
Different factors can affect the transaction log file size that is
appropriate for your environment – for example, the amount of data
stored in the portal databases, or the number of primary and
secondary log files in use. To avoid having migration tasks fail
because the transaction log file is too small, see your DBMS
documentation to determine the best option for increasing the
transaction log size before you start migration.
Check out the following link –
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?
topic=/com.ibm.db2.udb.spatial.doc/cfgtranslog.html
As I am using db2, from the db2 control center I right click to the db
and selected configure database logging and changed the value as
suggested in above link.
Considerations -
Migration can take a while, and interruptions to your HTTP connection during
the export process or import process can cause migration to fail. To avoid this
problem, use the internal WAS HTTP server port. For instance, by default in
wkplc.properties -- WpsHostPort=10040. If you have changed to port 80,
then change it to 10040. Once the migration gets completed, one can change
it back.
Deprecated Portlets -
Some previously available portlets have been removed from WebSphere
Portal 7 because alternative or newer functionality is available that you can
use instead. If you migrate from an earlier WebSphere Portal installation that
used these portlets, the portlets are migrated to provide backward
compatibility, in some case they are treated as third-party portlets and may
get migrated forward. Users are encouraged to transition to other available
technology as appropriate.
URL Mappings -
If you have the urlmapping to the pages within the same WebSphere Portal
(not crossing the VP boundaries) then the URL mappings gets migrated. If
you have urlmapping to any admin pages, then it will not get migrated since
the admin pages do not get migrated.
Chapter 2
2.1 Make the Portlets applications available to migration tasks
One doesn't need to copy their custom portlet war files to installableApps
directory of WebSphere Portal 7 environment. Migration scripts would be able
to take care of your custom portlets.
2) If you are using Cooperative portlets (c2a – click to action - using IBM API)
then update your pbjportlet.jar file with the latest version of pbportlet.jar from
the WebSphere Portal 7 --
● In the WebSphere Portal 7 environment, locate pbportlet.jar in the
PortalServer_root/base/wp.propertybroker.legacy.impl/pb/lib
directory.
● Copy the pbportlet.jar files to the WEB-INF/lib directory of the
cooperative portlet application that you are migrating.
● Overwrite the JAR files if they already exist.
3) If you have struts portlet, then it should work as normal after completing the
migration process. If it does not then upgrade it with the latest struts
framework.
Before you install the fixes, make sure portal server and server1 is stopped.
Make sure to read the ReadMe.txt for ALL the fixes that one installs.
Before you install the fixes, make sure portal server and server1 is stopped.
Chapter 3
In this chapter we would be doing core migration of our resources from
WebSphere Portal 6.1.0.5 to 7. Remember I am doing the SAME Machine
Migration. As I did migrated from a stand-alone portal 6.1.0.5 to stand-alone
portal 7 I followed the section “Migrating a stand-alone portal that runs on a
V6.1 application server” in WebSphere Portal 7 Information Center.
If you want to migrate the clustered portal 6.1.0.5 to clustered portal 7 then
you need to follow the section “Migrating a V6.1.x clustered portal” in
WebSphere Portal 7 Information Center.
If the source portal and target portal are located on the same server, you can
migrate the source portal's application server profile by completing a set of
manual steps or by using the IBM® WebSphere® Application Server
Migration wizard to create the profile automatically for you.
To migrate the application server profile on i, use the manual steps provided
above; WebSphere Application Server does not provide a Migration wizard on
i.
Make sure it is successful. If you used Migration Wizard then you can jump to
Step 5. Otherwise follow the below mentioned manual steps.
I am using the manual steps to create the wp_profile on the target portal
server and migrating the wp_profile from the source portal server.
• source_node_name
Specifies the node name for the node that is created with the new
profile. Use a unique value within the cell or on the server.
• source_cell_name
Specifies the cell name of the source portal profile.
• host_name
Specifies the host name for the target server or deployment manager
where you are creating the profile.
Note: NodeName and CellName needs to be same. if not then there would
be problem with deploying the application later on.
Note: If you forgot to have the parameter profileName or mispelled it, then it
will create a profile named AppSrv01.
AboutThisProfile.txt file will show the location, node name, host name and
port information that got associated when the profile got created.
For instance, this is from my AboutThisProfile.txt --
Application server environment to create: Application server
Location: C:\wp7\wp_profile7
Disk space required: 200 MB
Profile name: wp_profile7
Make this profile the default: True
Node name: desire
Host name: desire.raleigh.ibm.com
Enable administrative security (recommended): False
Administrative console port: 9060
Administrative console secure port: 9043
HTTP transport port: 9080
HTTPS transport port: 9443
Bootstrap port: 2809
SOAP connector port: 8880
Run application server as a service: False
Create a Web server definition: False
Performance tuning setting: Standard
• backup_dir
Specifies the directory on the source portal where the WASPreUpgrade
command stores the exported profile data. If the directory does not
exist, the WASPreUpgrade command creates it.
• source_WasHome
Specifies the WebSphere Application Server installation directory on
the source server.
• wp_profile_name
Specifies the portal profile on the source server
Optional
• trace_spec
Specifies the trace information that you want to collect. To gather all
trace information, specify "*=all=enabled" (including the quotation
marks). If you include this parameter, you must also specify the
trace_file.
If you do not specify the -traceString or -traceFile parameter,
the command creates a trace file by default and places it in the
backupDir/logs directory. If you specify the -traceString
parameter but omit the -traceFile parameter, the command does
not generate a trace file.
• trace_file
Specifies the name of the output file where trace information is stored.
If you do not specify the -traceString or -traceFile parameter,
the command creates a trace file by default and places it in the
backupDirectory/logs directory. If you specify the
-traceString parameter but omit the -traceFile parameter, the
command does not generate a trace file.
NOTE: If the WASPreUpgrade task fails with out of memory error then you
can edit the WasPreUpugrade command file which is located at
<AppServer_root>\bin\WasPreUpgrade.bat/sh and update the -Xmx
parameter of the PERFJAVAOPTION variable to have a value of at least 1024
MB.
For instance:
set PERFJAVAOPTION=-Xms512m -Xmx1024m -Xj9 -Xquickstart
• backup_dir
Specifies the directory where the WASPreUpgrade command stores
the data that it exports from the source server, and from which the
WASPostUpgrade command reads and imports data.
• wp_profile_name
Specifies the new portal profile on the target server or node to which
the WasPostUpgrade command migrates the source portal profile.
• old_wp_profile_name
Specifies the source portal's profile name. The profile name must
already exist in the backup directory specified above.
• source_admin_user
Specifies the administrator ID for the source portal. Specify the login
form of the administrator ID rather than the fully qualified name; for
example, specify wpsadmin rather than uid=wpsadmin,
o=defaultWIMFileBasedRealm.
• source_admin_password
Specifies the administrator ID password for the source server.
Optional
• trace_spec
Specifies the trace information that you want to collect. To gather all
trace information, specify "*=all=enabled" (including the quotation
marks). If you include this parameter, you must also specify the
trace_file.
If you do not specify the -traceString or -traceFile parameter,
the command creates a trace file by default and places it in the
backupDir/logs directory. If you specify the -traceString
parameter but omit the -traceFile parameter, the command does
not generate a trace file.
• trace_file
Specifies the name of the output file where trace information is stored.
If you do not specify the -traceString or -traceFile parameter,
the command creates a trace file by default and places it in the
backupDirectory/logs directory. If you specify the
-traceString parameter but omit the -traceFile parameter, the
command does not generate a trace file.
Look at the logs and confirm the task got completed successfully.
You can ignore the following message if you see in the log file –
WASX7017E: Exception received while running file
"/C:/wp7/waspreupgradebk/install_WebDAV_for_WebSphere_Portal.ear.jy";
exception information:
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescri
ptorLoadException:
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.DeploymentDescri
ptorLoadException: dd_in_ear_load_EXC_
MIGR0340W: Application WebDAV_for_WebSphere_Portal.ear did not deploy
If any of the custom application failed to deploy during this task, then you
needs to investigate where it is failing. One of the common scenario it may
fail to deploy is because the custom application contains characters like
apostrophe or single quote. If this is the case, you can also look at the Jython
scripts for that custom application at
<backup_dir>\profiles\wp_profile\PortalApps. You should just fix the Jython
script instead of fixing in the source portal server and then try to run/deploy
that custom application individually using the wsadmin command.
For instance, if you want to execute Jython file – ex1.py then one can do the
following -
WasPassword=password
• profile_name
Specifies the name of the WebSphere Application Server V7 profile
that is the target of the upgrade.
• connection_type
Specifies the type of connection that should be established. Valid
connection types are SOAP and NONE.
• host_name
Specifies the host name of the application server (when migrating a
stand-alone server) or Deployment Manager (when migrating a
clustered environment).
• port_number
Specifies the port number of the application server (when migrating a
stand-alone server) or Deployment Manager (when migrating a
clustered environment). Use the value of WasSoapPort from the
wkplc.properties file.
• admin_name
Specifies the administrator user ID for the application server.
• admin_password
Specifies the password for the administrator user ID.
Note: Instead of just re-using JCR and Release domain, I copied ALL of the
domains including – feedback, likeminds, customization, community.
Here is the screenshot which show the backup and restore for JCR and
Release domain:
B) Configure your Portal 7.x envinorment by updating the following files to
reflect a connection to the ALL domain copy that you created in the previous
step:
jcr.DbName=bkjcr7
jcr.DbSchema=jcr (Needs to same schema value for <orig_db>)
jcr.DataSourceName=wpdbDS_bkjcr7
jcr.DbUrl=jdbc:db2://hostname:50000/bkjcr7:returnAlias=0;
ConfigEngine.bat list-server-ports-by-name
-DServerName=WebSphere_Portal -DWasPassword=password
Observe this will be the same ports which the wp_profile used from the
source environment.
Now as I have both source and target servers on the same machine, I can't
use the same ports between the source and target servers. If not then will
cause the port conflicts. For the target server I want to use the ports starting
from 16000, hence I executed the following tasks
2) ConfigEngine.bat modify-ports-by-startport
-DWasPassword=password -DModifyPortsServer=server1
-DStartPort=16000
D) Look in the serverindex.xml file and see what are the correct ports that got
associated with server1 and WebSphere Portal server.
For instance,
WasSoapPort=16040
WpsHostPort=16054
ConfigEngine.bat validate-database-connection
ConfigEngine.bat connect-database
Note: If you just copied the Release and JCR domain, then you want to use
the following commands :
ConfigEngine.bat validate-database-connection
-DTransferDomainList=release,jcr
Note: If the portal uses IBM® DB2 Universal Database™ for z/OS® as the
backend repository then check out the sections of “Updating the database
schemas” and “Updating the configured database driver for DB2 for z/OS” in
the WebSphere Portal 7 Information center.
In this step we will migrate properties files, upgrade database domains, and
apply other updates that are needed to bring the source profile to the V7 level
by running the upgrade-profile task.
Important: If you updated the database schemas manually, you must include
the parameter -DDbSafeMode=true. For example: ConfigEngine.bat
upgrade-profile -DWasPassword=WasAdminPwd
-DPortalAdminPwd=PortalAdminPwd -DDbSafeMode=true
Do not specify this parameter if you want the migration process to update the
database schemas for you.
● Start the WebSphere Portal 7 server and the hit the migrated portal
URL, which is in the following format/form:
http://host_name:port_number/original-context-root_migrated/portal
Chapter 3
3.1 WCM Migration -
To ensure that the portal can retrieve metadata information for resource
management on remote systems after migration, configure the Resource
Manager portlet with information about the remote system and the settings
used to handle communication with the system as mentioned in the section of
“Configuring resource management with site management” in WebSphere
Portal 7 Information Center.
As the context root has been changed for the custom themes and skins this
can cause problems if you have developed custom themes or skins that
contain hardcoded references to the portal's context root. (This is particularly
an issue after migration because the context root is modified during migration,
causing hardcoded references to break.) You can update your themes and
skins to remove the hardcoded references and instead use dynamic
references that work properly regardless of the context root as mentioned in
the section of “Updating custom themes and skins for hardcoded context root
references” in WebSphere Portal 7 Information Center.
Also the above section talks about how you can change the context root for
your custom themes and skins application so that you can use desired context
root.
You can change the context root for the Migrated Portal server by editing
wkplc.properties for WpsContextRoot and wkplc_comp.properties for
WpsDefaultHome and then executing modify-servlet-path configuration
task to modify the portal URI.
1. If the source portal server was installed using the content build (Portal +
WCM) and if the target server was installed only by using Portal server binary
code as WCM is not been used in source, then during the upgrade-profile task
the target portal server would not start cleanly. As a result the task will fail
with “Error 404: javax.servlet.UnavailableException: Initialization of one or
more services failed”
Also the systemout logs will show ClassNotFoundException during the “wps”
application startup as seen below :
2. One may see the following error in the systemout.log file while executing
upgrade-profile task ---
DataStoreCont E com.ibm.wps.datastore.impl.DataStoreContext
handleException EJPDB0001E:
Error occurred during database access. Last SQL statement is [SELECT
OID, CREATED, MODIFIED, RESOURCE_ROOT, IS_ACTIVE,
IS_DEFAULT, DEFAULT_LOCALE, TYPE, CONTEXT_ROOT,
THEME_SCOPE_OID FROM release.SKIN_DESC ].
com.ibm.wps.datastore.impl.DataBackendException: EJPDB0002E: Error
occurred during database access.
at
com.ibm.wps.datastore.impl.DataStoreContext.handleException(DataStoreCo
n
text.java:337)
at
com.ibm.wps.datastore.impl.ResourcePersister.findInternal2(ResourcePersi
ster.java:1150)
at
com.ibm.wps.datastore.impl.ResourcePersister.findInternal(ResourcePersis
ter.java:1050)
at
com.ibm.wps.datastore.impl.ResourcePersister.findAll(ResourcePersister.j
ava:1715)
...............
...............
Caused by: java.sql.SQLException: ORA-00904: "THEME_SCOPE_OID":
invalid identifier
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:11
2)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
The above error most likely points that one have missed out the steps on
database copy and connection task that needs to be executed on the portal
7x server.
3. One may see the following error in the systemout.log file while executing
upgrade-profile task ---
InternalGetSc E
com.ibm.wps.command.scheduler.internal.InternalGetSchedulerTaskComma
nd
AbstractCommand.throwCommandException EJPDD0009E: JNDI naming
lookup failed for name = [ejb/wpsSchedulerManager].
javax.naming.NameNotFoundException:
Context: <cell_name>/nodes/<node_name>/servers/WebSphere_Portal,
name:
ejb/wpsSchedulerManager: First component in name wpsSchedulerManager
not
found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at
com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNCont
extImpl.java:4365)
at
com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:17
94)
at
com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:17
49)
4. genRemMigPkg task will not get executed during portal 7x migration even if
you provide the correct name of the profile. This mostly happens on the Unix/
Linux/AIX environment
This has been resolved in PM24941 which have been already included in
Portal 7.0.0.1. Install the latest cumulative fix available for Portal 7 server
before migrating.
mig-stop-admin-server:
[echo] 'server1' seems being started.
[echo] Stopping 'server1' ...
mig-set-instance-properties:
mig-stop-server-helper:
[exec] ADMU0116I: Tool information is being logged in file
[exec]
C:\IBM\WebSphere\wp_profile\logs\server1\stopServer.log
[exec] ADMU0128I: Starting tool with the wp_profile profile
[exec] ADMU3101I: Using explicit host and port localhost:10005 for
server: server1
[exec] ADMU0111E: Program exiting with error:
javax.management.JMRuntimeException:
[exec] ADMN0022E: Access is denied for the stop
operation on Server MBean
[exec] because of insufficient or empty credentials.
[exec] ADMU4113E: Verify that username and password information is
correct. If
[exec] running tool from the command line, pass in the
correct -username
[exec] and -password. Alternatively, update the
<conntype>.client.props
[exec] file.
[exec] ADMU1211I: To obtain a full trace of the failure, use the
-trace option.
[exec] ADMU0211I: Error details may be seen in the file:
[exec]
C:\IBM\WebSphere\wp_profile\logs\server1\stopServer.log
BUILD FAILED
C:\IBM\WEBSPH~1\PORTAL~1\installer\wp.migration.framework\config\inclu
des\mig_cfg.xml:294: The following error occurred while executing this
line:
C:\IBM\WEBSPH~1\PORTAL~1\installer\wp.migration.framework\config\inclu
des\mig_cfg.xml:404: The following error occurred while executing this
line:
C:\IBM\WEBSPH~1\PORTAL~1\installer\wp.migration.framework\config\inclu
des\mig_cfg.xml:435: exec returned: -1
Most likely one used the incorrect port while executing upgradeConfigEngine
task. Try using the value of WasSoapPort from the wkplc.properties file for
the -port parameter.