Before you start migrating your application from BTT version 5.1
to BTT version 5.2, you need to prepare the development environment for the
migration:
- For the application without BPEL, you need to install Rational® Application
Developer v6.0.1 or above
- For the application with BPEL, you need to install WebSphere® Integration Developer v6.0.1
or above
- Import your BTT version 5.1 application
- Replace BTT version 5.1 CHA projects and the related jar files
by those of BTT version 5.2. Here we take BTTHTMLSample migration as an example.
- Migrate your Enterprise Application from J2EE 1.3 to J2EE 1.4
- Remove the CHA related projects from the workspace, including
BTTCHAEJB and BTTCHAWEB
- Import BTT version 5.2 CHA EJB JAR file into the workspace.
The file name is BTTCHAEJB. The EAR project should be the project of the BTT
version 5.1 application, for example, BTTHTMLSample.
- Copy com.ibm.btt.cs.invoker.base.BeanInvokerRegistryMapper.properties from bttinvoker.jar in
the JavaSource folder of BTTHTMLSampleWeb project, because the properties
file doesn't contain any invoker information for this sample in bttinvoker.jar of
the BTT version 5.2 package.
- Replace BTT version 5.1 jar files in the Enterprise Application
project and the Web project by BTT version 5.2 jar files.
Note: bttfmt.jar and bttsvcinfra.jar are
not needed in the BTT version 5.2 package. You can remove them.
- Add bttbase.jar and bttOpStepAdaptor.jar in
the build path of BTTCHAEJB project
- Create a new database for BTT version 5.2 CHA, because the table
schema of CHA in BTT version 5.2 is changed.
- Turn on the services of startup bean and the workarea from the
administration console, because by default, these two services are disabled
in WebSphere Application
Server v6.x and WebSphere Process
Server 6.x.
You may encounter some compilation error in the projects – BTTHTMLSampleEJB
and BTTHTMLSampleWeb. They will be solved in
Migrate application codeNow
you can start the migration.