Manuals / IBM / Marine Equipment / Marine Radio

IBM SG24-6320-00 manual WebSphere\VAJ40

Models: SG24-6320-00

1 306

Download 306 pages 3.81 Kb

Page 106

6320ch_DEV_installation.fm

Draft Document for Review July 28, 2004 7:33 pm

Note: VisualAge for Java V3.5.3 and VisualAge for Java V4.0 cannot coexist on the same system. As such, you must install VisualAge for Java V4.0 on a separate system, remote from your VisualAge for Java V3.5.3 installation.

Alternatively, if your access to additional systems is limited, you could perform the steps in the following order:

1.Follow the instructions in 6.2.4, “Export code from VisualAge for Java V3.5.3” on page 100 to export your custom Java code.

2.Follow the instructions in 7.5.2, “Export the EJB project from VisualAge for Java V3.5.3” on page 120 to export your EJBs from VisualAge for Java V3.5.3.

3.Uninstall VisualAge for Java V3.5.3.

4.Install and configure VisualAge for Java V4.0 per the instructions in this section.

5.Complete the migration steps in the remaining chapters of this part, skipping the export steps that you have already performed.

1.Insert the VisualAge for Java CD into your CD-ROM drive. If the VisualAge for Java launchpad does not open, it can be started by running the setup.exe file from the root of the installation CD.

2.The VisualAge for Java launchpad will open. Click Install Products. and click Install VisualAge for Java.

3.After a while the language selection window for the main installation program will appear. Select your language and click OK. We selected English.

4.The InstallShield wizard starts up and the welcome window will appear. Click Next.

5.Read the license agreement, select I accept the terms in the license agreement and click Next.

6.The installation program will prompt for the installation type. Select Complete and click Next.

7.The Edit Features window appears which will allow you to change the destination path folder. Click Change...

8.Enter the desired destination paths for the components being installed and click OK.

We used the following value:

D:\WebSphere\VAJ40

9. Click Next.

88Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Image 106

$IBM SG24-6320-00 manual WebSphere\VAJ40$

Contents

Keeping Commerce Applications Updated Page International Technical Support Organization First Edition July Contents 6320TOC.fm Part 2. Development environment Part 3. Production environment 6320TOC.fm Part 4. Appendixes Abbreviations and acronyms Index6320TOC.fm 6320spec.fm Trademarks IBMPreface Team that wrote this redbook6320pref.fm Become a published author Comments welcomeRedbook@us.ibm.com Part 1 Introduction to WebSphere Commerce 6320p01.fm Introduction Structure of the book OverviewPart 1, Introduction to WebSphere Commerce Part 4, Appendixes Part 2, Development environmentPart 3, Production environment Commerce Application used during the migration6320chintro.fm WebSphere Commerce V5.6 Overview Product overview WebSphere Commerce V5.6 Overview WebSphere Commerce software components WebSphere Application ServerWeb server WebSphere Application ServerDatabase Server WebSphere Commerce ServerWebSphere Commerce enablement software Enablement softwareWebSphere Commerce Payments Server WebSphere enablement software Member subsystem WebSphere Commerce Server subsystemsUser registration methods User registration and update methods Member security services 6320chsumofchanges.fm Catalog subsystem Single sign-onMerchandising subsystem Trading subsystemOrder subsystem Marketing subsystemMessaging subsystem Configuration ManagerWebSphere Commerce Tools WebSphere Commerce AcceleratorPassword Manager Organization Administration ConsoleAdministration Console WebSphere Commerce Business modelsDirect Sales Consumer directB2B direct Value ChainDemand chain Supply chain Hosting Ex-SitesHosting WebSphere Commerce Development Environment What’s new in WebSphere CommerceEx-Site WebSphere Commerce Payments Configuration ManagerPassword Manager Loader PackageAdaptor for CrossWorld Catalog and product managementSKU generation Accounts Business EditionCollaboration Access ControlBusiness Models Product Management toolingCampaigns and Promotions Order and inventory ManagementAnalytics SecurityCaching DynacacheHttps//hostname8002/cachemonitor Product Advisor 6320chsumofchanges.fm Migration Strategy and Planning Take advantage of DynaCache Migration Strategy considerationsAdd or replace functionality OptimizationHow does custom code impact the process? External product and user managementPrepare a detailed Plan Migration Planning Skill requirementsHardware and software prerequisites Production EnvironmentSoftware prerequisites Development Environment Hardware prerequisites for development environmentProduct versions mapping, production environment Product versions mappingMigration approach for development environment Product versions mapping, development environmentMigration approaches for runtime environment Switch-Over migration scenario Firewall Co-existence migration scenario In-place migration scenarioApproach used for this migration Detailed overview of development migration steps Detailed overview of production environment migration 6320chplanning.fm 6320chplanning.fm 6320chplanning.fm Commerce Application used during the migration Application environment Hardware ConfigurationCommerce application Application Server TierDatabase Server Tier Commerce customizationShopping flow Account CreationOffline Orders Payment ProcessingBilling/Shipping Selection InFashion default shopping flow Commands Customized shopping flow1provides a summary of the custom commands used with ApplicationCatalog Database tablesDatabase 6320chapplicationused.fm Part 2 Development environment 6320p03.fm Installing WebSphere Commerce Development Environment Pre-installation requirements Development environment overviewPre-installation steps Installing WebSphere Studio Application DeveloperVisualAge for Java V4.0 prerequisites Installing WebSphere Studio Application Developer Apply fixes to the test environment Prepare for fixpack installation Install WebSphere Application Server V5.0.2 cumulative fixSelect Install fixpacks and click Next Click NextInstall interim fixes CD-ROM drive\BASE\fixesInstalling WebSphere Commerce V5.6 Toolkit Installing WebSphere Commerce V5.6 Toolkit Installation verificationInstalling DB2 Universal Database Backup development databasesInstallation requirements Preparing a Windows user for DB2 Select Action New UserInstalling DB2 Universal Database Output from this command should be as follows6320chDEVinstallation.fm 6320chDEVinstallation.fm Installing DB2 Universal Database fixpack 6320chDEVinstallation.fm Our example, we entered the following commands Configuring the development environment for DB2Migrate databases to DB2 Universal Database V8.1 level Wctoolkithome\bin Installing VisualAge for Java Installing VisualAge for JavaTime spent installing and configuring VisualAge for Java \WebSphere\VAJ40 Install features and fixes for VisualAge for Java Configuring VisualAge for JavaSelect Administrator and click OK Install the DeployTool fix Install IBM WebSphere Test Environment fix Click FinishPrepare the VisualAge for Java V4.0 workspace Packages to delete from workspaceImport WebSphere Commerce Studio V5.1 repository Select Local repository6320chDEVinstallation.fm Pre-migration steps Preparation overview Updating the product information file Instance preparationTo the following directory Example 6-1 Example product.xml file Choosing the value for editionnameChoosing the value for mod Prepare resourcesChoosing the value for fixpack Merge EJB groups Export code from VisualAge for JavaOverview Exporting the Java codeUpdate database configuration values Database preparationDB2 configuration set by the updateDBConfiguration script Our example we called the as followsOrder status Change the order status to X CancelledUnsent messages CatalogProduct-item relationship MembersMaster catalog Organizational structureProfile types Refer to WebSphere Commerce AdministratorsRole changes Roles that are not included in WebSphere CommerceCustom message types Add Store Administrator as role for our usersDropping foreign key references Erroneous data in encrypted fields Tables and fields to check for erroneous leading spaces6320chDEVbeforemigration.fm Migrating the development environment Current development environment Development environment migratedMigrating the development instance OverviewRun the Wcim tool as follows Running the toolOur example, we used the following directory Example 7-1 Sample output from the Wcim toolFile name of the log will be in the following format Migrating unencrypted data Migrating the development databaseRun the migration script as follows For example, we used We used the following commandMigrating encrypted data Run the script as followsMigrating custom EJBs Summary119 Export the EJB project from VisualAge for Java Process for converting from EJBs from version 1.0 toImport the EJB projects into VisualAge for Java Regenerate the deployed code for the EJBs Export EJBs as EJB 1.1 JAR filesImport the EJBs into WebSphere Studio Application Developer 6320chDEVmigration.fm Post-migration steps Setting up aliases Lightweight test environmentExample 8-1 Excerpt from the looseconfig.xmi file Example 8-2 Excerpt from the deployment.xml fileExample 8-3 Excerpt from the application.xml file Migrating custom code Command parameter validation User registration Calculation usage framework Logon commandBackground Mapping between WebSphere Commerce commands Migration Example 8-4 Sample MyApplyShippingCmd Example 8-5 Sample MyApplyShippingCmdImpl6320chDEVpostmigration.fm 137 Example 8-6 Registering calculation method WebSphere Commerce V5.6 command interfaces Interface changesApplyOrderAdjustmentsCmd contain the following methods WebSphere Commerce Suite V5.1 interfaces for the commandsRefer to Example 8-5 on page 135 for an sample of this Accessing the order items Accessing OrderItemAccessBean Accessing Item Then this could be migrated into the following line143 Configuration and code changes for migrated EJBs Access bean string converters145 Change the access isolation level Example 8-7 Example ibm-ejb-access-bean.xmi file147 Add the WCSecurity role Ensure that ejbCreate returns primary key object Change the container transaction typeRemove serialVersionUID constants Delete this line and save your source by pressing Ctrl + SRemove java.rmi.RemoteException from remote methods Remove FinderHelper interface Match ejbPostCreate and ejbCreate methodsFollowing method would be added to the home interface 7 J2EE Connector Architecture Regenerating the deploy codePricing New task commandsChanged price task commands New data bean methodsPackage name change Changes to myAccount.jsp Rule server administration commandsJSP and property file changes Our exampleExample 8-8 The content of the modified myAccount.jsp file Changes to Register.jspExample 8-9 The content of the modified register.jsp file @ include file=getResource.jsp%Example 8-11 Error texts for file myAccount.jsp Example 8-10 Error texts for file Register.jspChanges to property files 159 6320chDEVpostmigration.fm Part 3 Production environment 6320p02.fm Installing WebSphere Commerce Hardware Single-node runtime overviewSoftware Installation Install WebSphere Commerce IBM Http Server D\WebSphere\HTTPServer Enabling for SSL Configuring IBM Http ServerEnabling Cache accelerator Verify installation log files Verifying the installationWebSphere Commerce installation logs WebSphere Application Server installation logs DB2 Universal Database installation logsExamine the following log files Washome\logs\WASFixPack.log IBM Http Server installation logs Create test instance Create a WebSphere Commerce instanceWeb server restart prompt for commerce instance creation Create a WebSphere Commerce Payments instance Commerce instance creation confirmation6320chinstall56.fm Removing test instances Removing WebSphere Commerce instanceRmCommerceServer instancename Removing WebSphere Commerce Payments instance Example 9-1 Sample rmPaymentServer.bat script 6320chinstall56.fm Draft Document for Review July 28, 2004 733 pm 6320chbeforemigration.fm Preparation overview 185 Example 10-1 product.xml file content WebSphere Commerce Suite Choosing the value for fixpack Our example the product.xml file looked like thisExample 10-2 Our product.xml file Disable security on WebSphere Application Server 189 Copying the database from Commerce V5.1 to Commerce Restore the configuration values to the original values Migrate the databaseUpdating database configuration values Script is invoked as followsChanges are done by executing the following SQL commands Orders statusExample of a master catalog Create catalog description Update keys for catalogUpdate keys for category Create category catalog groupMembers Update the users profile type Our example this command retrieved 6 records 199 Erroneous data in encrypted fields Migrating WebSphere Commerce components Migrating commerce instance configuration Migration overviewMigrating the instance Unpack backupwcim.zip This will generate the following fileFrom the following directory Running the above command will produce the following fileEnter the previous IBM Http Server home directory Wc56home\temp Migrating commerce database Enter the new IBM Http Server home directoryMigrating the database Script receives the following parametersMandatory migration script parameters Parameter name Parameter valueOur example Example 11-2 a small extract of the migration log file Error SQL0601N Error SQL0605WSample of this error in the log Example 11-3 The content of the modified choosemc.sql file Choosing the master catalogMigrating the encrypted data Merchant key and encrypted dataOptional parameters are Script must have the following mandatory parametersEncrypted data migration script parameters Parameter Encrypted data migration script parameters and behaviorMigrating Payment Manager Install Fixpack for WebSphere Payment Manager Ensure that none of these files contain any error messages Install WebSphere Commerce Payments remote nodeOur example, we used Next Package and transfer the Wcim tool Backup the WebSphere Payment Manager instance Backup the WebSphere Payment Manager database Backup the payment databaseMigrate the WebSphere Payment Manager instance Restore WebSphere Payment Manager databaseTransfer assets to WebSphere Commerce Payments node Our example we typedClick on OK Click Apply Click OK on the following confirmation window Restart the Web serverDisconnect from the commerce database Migrate the WebSphere Payment Manager databaseDelete the obsolete payment methods Disconnect from the payments databaseThis concludes the payments database migration 6320chpostmigration.fm Post migration steps for IBM Http Server Migrating static contentUpdating configuration Document root is added as described belowDeploying EJBs DeployingExample 12-1 WebSphere Commerce section of httpd.conf Configure and export the JAR file Applying the JAR file to the production environmentDeploying commands and databeans Export the JAR fileExporting store assets Deploying store assetsTo export store assets perform the following steps Applying the store assets to the production environment Select Create directory structure for files6320chpostmigration.fm Part 4 Appendixes 6320p04.fm Appendix A. Managing WebSphere Commerce components Checking instance status Run the following command from the washome\bin directoryWebSphere Commerce instance management Starting the instanceWebSphere Commerce Payments instance management Stopping the instanceStart the Configuration Manager Follow these steps to start the Configuration ManagerDb2start Modifying trace strings for a running server Output should be similar to what is shown in Example A-1Restarting IBM Http Server Example A-1 Restarting the IBM Http ServerOur example, we issued the following command Resulting in the following messagesQuit Tracing for Lightweight WebSphere Test Environment Tracing with WebSphere Commerce V5.6 ToolkitTracing for Full WebSphere Test Environment Example A-2 Excerpt from Logging.properties fileCreate wcspassword script Create missing password scriptsCreate wcspmpassword script 6320ax04.fm Appendix B. Backup WebSphere Commerce Suite File system Default directoriesCustom directories Database backup Db2 backup database dbname to backupdirectory Appendix C. Migration scripts Migratedb.bat behavior Here is an excerpt of the configuration fileWebSphere Commerce V5.6 migration scripts behavior Example C-1 Excerpt of DataMigrationPlan51.xml fileMigrateEncryptedInfo.bat behavior Wcim.bat behavior Tables used by migrateEncryptedInfo script file6320ax02.fm Custom database migration scripts behavior Sequence diagram of the batch files Database preparation batch scriptExample C-2 Content of the pre.migration.bat file Example C-3 Content of the pre.migration.sql file Database preparation SQL scriptDatabase migration batch script Create NEW Master CatalogueExample C-4 Content of the migration.bat file Database post migration batch scriptExample C-5 Content of post.migration.sql file Database post migration SQL scriptAppendix D. Moving from single to multi-node environment Single-node environment Installing and configuring the database nodeCreate a Windows user for DB2 Installing DB2 Moving the database Connecting to the remote databaseBackup the current production database Stop all connections to the databaseVerify connectivity Create a local alias for the remote database6320ax01.fm Using the Web material Locating the Web materialZipped containing the rmPaymentsServer.bat script and a How to use the Web materialCopy of the product.xml.51.sample file Abbreviations and acronyms 6320abrv.fm Other publications IBM RedbooksOnline resources IBM Support and downloads IBM Global Services How to get IBM RedbooksHelp from IBM Index EJB Migration scenario in-place 6320IX.fm 6320IX.fm Security Keeping Commerce Applications Updated Keeping Commerce Applications Updated WebSphere Commerce Page Keeping Commerce Applications Updated WebSphere Commerce