Upgrading projects to work in session-independent mode

0
votes

As we know, when I deploy a WAR file that has been built using WL 6.2 to MFP7.1, the server migrate the WAR file from 6.2 to 7.1 automatically using its own worklight-jee-library.jar file, making the runtime to function as WAR 7.1 (Please correct me if I’m wrong). However, based on the note mentioned in the URL:

https://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/t_upgrading_projects_session_depend.html

Note: Clients that were created using a version of IBM MobileFirst Platform Foundation earlier than V7.1.0 do not work with a MobileFirst Server that is operating in the new session-independent mode. So, to serve users who are using the session-independent mode, as well as existing users who are using session-dependent mode, you must deploy the new V7.1.0 WAR with its V7.1.0 artifacts, but WITHOUT removing the old WAR.

What does it mean "WITHOUT removing the old WAR.”? There won’t be old WAR as the WAR version now is V7.1! which has been communicated to us that we can't deploy old WAR without doing the migration.

During the WAR deployment, we get this:

[configureapplicationserver] INFO: FWLST2017I: The project WAR file was successfully migrated from version 6.2.0.01.20150329-1923 to version 7.1.0.00.20160401-2103. The migrated project WAR file is located in '/tmp/wla5601747575/MobileBanking.war'.
[configureapplicationserver] ** Created migrated war file

What is the WAR deployed now? is it version 7.1 or still 6.2?

Edit:

  1. Project is built and complied using WL 6.2
  2. artifacts created are WAR - WLAPP and adapters using WL 6.2 ant tasks.
  3. Need to deploy all those artifacts to MFP 7.1 as it is. No Migration done to those artifacts as to serve my live clients.
  4. I'm taking all those artifacts to MFP server and start the deployment.
  5. The WAR file is being migrated to 7.1 during the deployment (Deployment is done using MFP Ant task).
  6. After the runtime is created. I'm deploying the 6.2 WLAPP and 6.2 Adapters inside the runtime.

When MFP server deploy the WAR file which is built from 6.2, what is the WAR version after the deployment?

If the WAR is still 6.2, why do I see "mfp.session.independent" property inside my runtime?

If the server is migrating the WAR by itself and making it 7.1, then how can I deploy an old WAR to MFP7.1 without any modification on it?

1
ibm-mobilefirst

1 Answers

0
votes

When building your project with the v7.1 Studio or the 7.1 Ant tasks, this will create the 7.1 war file.

You can still deploy your old war from 6.2 along side your 7.1 war file. It implies you're supposed to back it up.