Manuals / IBM / Marine Equipment / Marine Radio

IBM SG24-6320-00 manual Firewall

Models: SG24-6320-00

1 306

Download 306 pages 3.81 Kb

Page 65

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

6320ch_planning.fm

FIREWALL
Network Address Translation (NAT)
DMZ
WebSphere	WebSphere
Commerce	Commerce
Suite V5.1	V5.6
DB2 UDB V7.2	DB2 UDB V8.1.5
WebSphere Commerce Suite V5.1	WebSphere Commerce V5.6
runtime environment	runtime environment

Figure 3-1 Switch-Over migration scenario

The following is a general ordered list of tasks that are required to complete a Switch-Over migration:

Complete migration of a development environment, as discussed in the

In-place migration section.

Complete pre-migration steps required on production server

Backup production system

Perform pre-migration actions

Install WebSphere Commerce V5.6 components on the test server

Migrate instance

Backup database from the production server

Restore database to the test server

Run scripts to migrate database

Deploy migrated code from deployment machine

Complete required migration tasks on the test server

Test migrated instance

Take the WebSphere Commerce Suite V5.1 production server offline

Backup database from the production server

Restore database to the test server

Run scripts to migrate database

Chapter 3. Migration Strategy and Planning 47

Image 65

IBM SG24-6320-00 manual Firewall

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 Index Abbreviations and acronyms6320TOC.fm 6320spec.fm IBM TrademarksTeam that wrote this redbook Preface6320pref.fm Comments welcome Become a published authorRedbook@us.ibm.com Part 1 Introduction to WebSphere Commerce 6320p01.fm Introduction Part 1, Introduction to WebSphere Commerce OverviewStructure of the book Part 3, Production environment Part 2, Development environmentPart 4, Appendixes Commerce Application used during the migration6320chintro.fm WebSphere Commerce V5.6 Overview Product overview WebSphere Commerce V5.6 Overview WebSphere Application Server WebSphere Commerce software componentsWebSphere Application Server Web serverWebSphere Commerce Server Database ServerWebSphere Commerce Payments Server Enablement softwareWebSphere Commerce enablement software WebSphere enablement software User registration methods WebSphere Commerce Server subsystemsMember subsystem User registration and update methods Member security services 6320chsumofchanges.fm Single sign-on Catalog subsystemOrder subsystem Trading subsystemMerchandising subsystem Marketing subsystemWebSphere Commerce Tools Configuration ManagerMessaging subsystem WebSphere Commerce AcceleratorAdministration Console Organization Administration ConsolePassword Manager WebSphere Commerce Business modelsConsumer direct Direct SalesDemand chain Value ChainB2B direct Hosting Hosting Ex-SitesSupply chain Ex-Site What’s new in WebSphere CommerceWebSphere Commerce Development Environment Password Manager Configuration ManagerWebSphere Commerce Payments Loader PackageCatalog and product management Adaptor for CrossWorldAccounts Business Edition SKU generationBusiness Models Access ControlCollaboration Product Management toolingOrder and inventory Management Campaigns and PromotionsSecurity AnalyticsDynacache CachingHttps//hostname8002/cachemonitor Product Advisor 6320chsumofchanges.fm Migration Strategy and Planning Add or replace functionality Migration Strategy considerationsTake advantage of DynaCache OptimizationPrepare a detailed Plan External product and user managementHow does custom code impact the process? Skill requirements Migration PlanningProduction Environment Hardware and software prerequisitesSoftware prerequisites Hardware prerequisites for development environment Development EnvironmentMigration approach for development environment Product versions mappingProduct versions mapping, production environment Product versions mapping, development environmentMigration approaches for runtime environment Switch-Over migration scenario Firewall In-place migration scenario Co-existence 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 Commerce application Hardware ConfigurationApplication environment Application Server TierShopping flow Commerce customizationDatabase Server Tier Account CreationBilling/Shipping Selection Payment ProcessingOffline Orders InFashion default shopping flow Customized shopping flow CommandsApplication 1provides a summary of the custom commands used withDatabase tables CatalogDatabase 6320chapplicationused.fm Part 2 Development environment 6320p03.fm Installing WebSphere Commerce Development Environment Development environment overview Pre-installation requirementsVisualAge for Java V4.0 prerequisites Installing WebSphere Studio Application DeveloperPre-installation steps Installing WebSphere Studio Application Developer Apply fixes to the test environment Install WebSphere Application Server V5.0.2 cumulative fix Prepare for fixpack installationClick Next Select Install fixpacks and click NextCD-ROM drive\BASE\fixes Install interim fixesInstalling WebSphere Commerce V5.6 Toolkit Installation verification Installing WebSphere Commerce V5.6 ToolkitBackup development databases Installing DB2 Universal DatabaseInstallation requirements Select Action New User Preparing a Windows user for DB2Output from this command should be as follows Installing DB2 Universal Database6320chDEVinstallation.fm 6320chDEVinstallation.fm Installing DB2 Universal Database fixpack 6320chDEVinstallation.fm Migrate databases to DB2 Universal Database V8.1 level Configuring the development environment for DB2Our example, we entered the following commands Wctoolkithome\bin Time spent installing and configuring VisualAge for Java Installing VisualAge for JavaInstalling VisualAge for Java \WebSphere\VAJ40 Select Administrator and click OK Configuring VisualAge for JavaInstall features and fixes for VisualAge for Java Install the DeployTool fix Click Finish Install IBM WebSphere Test Environment fixPackages to delete from workspace Prepare the VisualAge for Java V4.0 workspaceSelect Local repository Import WebSphere Commerce Studio V5.1 repository6320chDEVinstallation.fm Pre-migration steps Preparation overview To the following directory Instance preparationUpdating the product information file Choosing the value for editionname Example 6-1 Example product.xml fileChoosing the value for fixpack Prepare resourcesChoosing the value for mod Export code from VisualAge for Java Merge EJB groupsExporting the Java code OverviewDatabase preparation Update database configuration valuesOur example we called the as follows DB2 configuration set by the updateDBConfiguration scriptUnsent messages Change the order status to X CancelledOrder status CatalogMaster catalog MembersProduct-item relationship Organizational structureProfile types Role changes AdministratorsRefer to WebSphere Commerce Roles that are not included in WebSphere CommerceDropping foreign key references Add Store Administrator as role for our usersCustom message types Tables and fields to check for erroneous leading spaces Erroneous data in encrypted fields6320chDEVbeforemigration.fm Migrating the development environment Development environment migrated Current development environmentOverview Migrating the development instanceOur example, we used the following directory Running the toolRun the Wcim tool as follows Example 7-1 Sample output from the Wcim toolFile name of the log will be in the following format Run the migration script as follows Migrating the development databaseMigrating unencrypted data Migrating encrypted data We used the following commandFor example, we used Run the script as followsSummary Migrating custom EJBs119 Process for converting from EJBs from version 1.0 to Export the EJB project from VisualAge for JavaImport the EJB projects into VisualAge for Java Export EJBs as EJB 1.1 JAR files Regenerate the deployed code for the EJBsImport the EJBs into WebSphere Studio Application Developer 6320chDEVmigration.fm Post-migration steps Lightweight test environment Setting up aliasesExample 8-2 Excerpt from the deployment.xml file Example 8-1 Excerpt from the looseconfig.xmi fileExample 8-3 Excerpt from the application.xml file Migrating custom code Command parameter validation User registration Background Logon commandCalculation usage framework Mapping between WebSphere Commerce commands Migration Example 8-5 Sample MyApplyShippingCmdImpl Example 8-4 Sample MyApplyShippingCmd6320chDEVpostmigration.fm 137 Example 8-6 Registering calculation method Interface changes WebSphere Commerce V5.6 command interfacesRefer to Example 8-5 on page 135 for an sample of this WebSphere Commerce Suite V5.1 interfaces for the commandsApplyOrderAdjustmentsCmd contain the following methods Accessing the order items Then this could be migrated into the following line Accessing OrderItemAccessBean Accessing Item143 Access bean string converters Configuration and code changes for migrated EJBs145 Example 8-7 Example ibm-ejb-access-bean.xmi file Change the access isolation level147 Add the WCSecurity role Remove serialVersionUID constants Change the container transaction typeEnsure that ejbCreate returns primary key object Delete this line and save your source by pressing Ctrl + SRemove java.rmi.RemoteException from remote methods Following method would be added to the home interface Match ejbPostCreate and ejbCreate methodsRemove FinderHelper interface Regenerating the deploy code 7 J2EE Connector ArchitectureChanged price task commands New task commandsPricing New data bean methodsPackage name change JSP and property file changes Rule server administration commandsChanges to myAccount.jsp Our exampleChanges to Register.jsp Example 8-8 The content of the modified myAccount.jsp file@ include file=getResource.jsp% Example 8-9 The content of the modified register.jsp fileChanges to property files Example 8-10 Error texts for file Register.jspExample 8-11 Error texts for file myAccount.jsp 159 6320chDEVpostmigration.fm Part 3 Production environment 6320p02.fm Installing WebSphere Commerce Software Single-node runtime overviewHardware Installation Install WebSphere Commerce IBM Http Server D\WebSphere\HTTPServer Enabling Cache accelerator Configuring IBM Http ServerEnabling for SSL WebSphere Commerce installation logs Verifying the installationVerify installation log files Examine the following log files DB2 Universal Database installation logsWebSphere Application Server installation logs Washome\logs\WASFixPack.log IBM Http Server installation logs Create a WebSphere Commerce instance Create test instanceWeb server restart prompt for commerce instance creation Commerce instance creation confirmation Create a WebSphere Commerce Payments instance6320chinstall56.fm Removing WebSphere Commerce instance Removing test instancesRmCommerceServer 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 Example 10-2 Our product.xml file Our example the product.xml file looked like thisWebSphere Commerce Suite Choosing the value for fixpack Disable security on WebSphere Application Server 189 Copying the database from Commerce V5.1 to Commerce Migrate the database Restore the configuration values to the original valuesScript is invoked as follows Updating database configuration valuesOrders status Changes are done by executing the following SQL commandsExample of a master catalog Update keys for category Update keys for catalogCreate catalog description 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 Migration overview Migrating commerce instance configurationMigrating the instance This will generate the following file Unpack backupwcim.zipEnter the previous IBM Http Server home directory Running the above command will produce the following fileFrom the following directory Wc56home\temp Enter the new IBM Http Server home directory Migrating commerce databaseScript receives the following parameters Migrating the databaseParameter name Parameter value Mandatory migration script parametersOur example Example 11-2 a small extract of the migration log file Sample of this error in the log Error SQL0605WError SQL0601N Choosing the master catalog Example 11-3 The content of the modified choosemc.sql fileMerchant key and encrypted data Migrating the encrypted dataEncrypted data migration script parameters Script must have the following mandatory parametersOptional parameters are Encrypted data migration script parameters and behavior ParameterMigrating Payment Manager Install Fixpack for WebSphere Payment Manager Our example, we used Install WebSphere Commerce Payments remote nodeEnsure that none of these files contain any error messages Next Package and transfer the Wcim tool Backup the WebSphere Payment Manager instance Backup the payment database Backup the WebSphere Payment Manager databaseTransfer assets to WebSphere Commerce Payments node Restore WebSphere Payment Manager databaseMigrate the WebSphere Payment Manager instance Our example we typedClick on OK Restart the Web server Click Apply Click OK on the following confirmation windowDelete the obsolete payment methods Migrate the WebSphere Payment Manager databaseDisconnect from the commerce database Disconnect from the payments databaseThis concludes the payments database migration 6320chpostmigration.fm Updating configuration Migrating static contentPost migration steps for IBM Http Server Document root is added as described belowExample 12-1 WebSphere Commerce section of httpd.conf DeployingDeploying EJBs Applying the JAR file to the production environment Configure and export the JAR fileExport the JAR file Deploying commands and databeansTo export store assets perform the following steps Deploying store assetsExporting store assets Select Create directory structure for files Applying the store assets to the production environment6320chpostmigration.fm Part 4 Appendixes 6320p04.fm Appendix A. Managing WebSphere Commerce components WebSphere Commerce instance management Run the following command from the washome\bin directoryChecking instance status Starting the instanceStopping the instance WebSphere Commerce Payments instance managementFollow these steps to start the Configuration Manager Start the Configuration ManagerDb2start Restarting IBM Http Server Output should be similar to what is shown in Example A-1Modifying trace strings for a running server Example A-1 Restarting the IBM Http ServerResulting in the following messages Our example, we issued the following commandQuit Tracing with WebSphere Commerce V5.6 Toolkit Tracing for Lightweight WebSphere Test EnvironmentExample A-2 Excerpt from Logging.properties file Tracing for Full WebSphere Test EnvironmentCreate wcspmpassword script Create missing password scriptsCreate wcspassword script 6320ax04.fm Appendix B. Backup WebSphere Commerce Suite Custom directories Default directoriesFile system Database backup Db2 backup database dbname to backupdirectory Appendix C. Migration scripts WebSphere Commerce V5.6 migration scripts behavior Here is an excerpt of the configuration fileMigratedb.bat behavior Example C-1 Excerpt of DataMigrationPlan51.xml fileMigrateEncryptedInfo.bat behavior Tables used by migrateEncryptedInfo script file Wcim.bat behavior6320ax02.fm Custom database migration scripts behavior Database preparation batch script Sequence diagram of the batch filesExample C-2 Content of the pre.migration.bat file Database preparation SQL script Example C-3 Content of the pre.migration.sql fileCreate NEW Master Catalogue Database migration batch scriptDatabase post migration batch script Example C-4 Content of the migration.bat fileDatabase post migration SQL script Example C-5 Content of post.migration.sql fileAppendix D. Moving from single to multi-node environment Create a Windows user for DB2 Installing and configuring the database nodeSingle-node environment Installing DB2 Backup the current production database Connecting to the remote databaseMoving the database Stop all connections to the databaseCreate a local alias for the remote database Verify connectivity6320ax01.fm Locating the Web material Using the Web materialCopy of the product.xml.51.sample file How to use the Web materialZipped containing the rmPaymentsServer.bat script and a Abbreviations and acronyms 6320abrv.fm Online resources IBM RedbooksOther publications Help from IBM How to get IBM RedbooksIBM Support and downloads IBM Global Services 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