IBM SG24-6320-00 ユーザーズマニュアル
6320ch_DEV_migration.fm
Draft Document for Review July 28, 2004 7:33 pm
112
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
7.1 Current development environment
This is a high level overview of the development environment as was installed for
WebSphere Commerce Suite V5.1 development.
WebSphere Commerce Suite V5.1 development.
Our WebSphere Commerce Suite V5.1 development environment consisted of a
single-tier installation of WebSphere Commerce running on DB2 Universal
Database V7.2.5. We had a single instance called demo created for our store.
Payment Manager was not installed as the store utilized an external payment
provider’s API. A library JAR file provided by Verisign was extracted and imported
into the VisualAge workspace.
single-tier installation of WebSphere Commerce running on DB2 Universal
Database V7.2.5. We had a single instance called demo created for our store.
Payment Manager was not installed as the store utilized an external payment
provider’s API. A library JAR file provided by Verisign was extracted and imported
into the VisualAge workspace.
The development tools consisted on VisualAge for Java and WebSphere
Commerce Studio. The WebSphere Test Environment was configured in
VisualAge.
Commerce Studio. The WebSphere Test Environment was configured in
VisualAge.
7.2 Development environment migrated
Figure 7-1 shows an overview of the development environment as it will be after
the migration. As the figure shows, both environments will be functional after the
migration is completed. The EJB Migration Node, shown in Figure 7-1 in a
dashed box, is an optional node used only if you choose to migrate your custom
EJBs using the process described in this book. As noted in 7.5, “Migrating
custom EJBs” on page 118, the migration process is not straightforward and is
not recommended unless you have a large number of custom EJBs.
the migration. As the figure shows, both environments will be functional after the
migration is completed. The EJB Migration Node, shown in Figure 7-1 in a
dashed box, is an optional node used only if you choose to migrate your custom
EJBs using the process described in this book. As noted in 7.5, “Migrating
custom EJBs” on page 118, the migration process is not straightforward and is
not recommended unless you have a large number of custom EJBs.
Figure 7-1 Schematic overview of the migrated development environment
EJB Migration Node
VisualAge for Java V4.0
Migrated Development Node
VisualAge for Java V3.5.3
WebSphere Test
Environment 3.5.3
PNS
WebSphere
Commerce Suite
5.1
MALL
WebSphere Studio
Application Developer V5.1.1
WebSphere Test
Environment 5.0.2
WebSphere
Commerce 5.6
Toolkit
DEVMALL