IBM SG24-6320-00 Manual Do Utilizador

 Chapter 8. Post-migration steps 

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

:
:
:

<looseArchives binariesPath="..\workspace\Stores\Web Content" 
resourcesPath="..\workspace\Stores\Web Content" uri="Stores.war" 
xsi:type="com.ibm.etools.commonarchive.looseconfig:LooseWARFile"/>
<looseArchives binariesPath="..\workspace\static_http\WebContent" 
resourcesPath="..\workspace\static_http\WebContent" uri="static_http.war" 
xsi:type="com.ibm.etools.commonarchive.looseconfig:LooseWARFile"/>
<looseArchives binariesPath="../wars/Payments.war" 
resourcesPath="../wars/Payments.war" uri="Payments.war" 
xmi:type="com.ibm.etools.commonarchive.looseconfig:LooseWARFile"/>

:
:
:

3. Edit the deployment.xml file located in one of the following directories, 

depending on the type of test environment that you use:

– Full test environment:

<wctoolkit_home>\conf\servers\fullconfig\cells\localhost\applications\wc
full.ear\deployments\wcfull\deployment.xml

– Lightweight test environment:

<wctoolkit_home>\conf\servers\lightconfig\cells\localhost\applications\w
clight.ear\deployments\wclight\deployment.xml

As shown in Example 8-2. If you entered a different name for the Web Project 
replace 

static_http

 in the file for the one you entered.

The value for 

startingWeight

 determines the starting order for modules in the 

server. The modules with smaller the values are started first.

The value for 

xmi:id

 (

WebModuleDeployment_567

 in the example) should be 

chosen such that it is unique within the deployment.xml file.

:
:
:

<modules startingWeight="10010" uri="Stores.war" xmi:id="WebModuleDeployment_5" 
xmi:type="appdeployment:WebModuleDeployment">
<targetMappings target="ServerTarget_1" xmi:id="DeploymentTargetMapping_18"/>
</modules>
<modules startingWeight="10020" uri="static_http.war" 
xmi:id="WebModuleDeployment_567" xmi:type="appdeployment:WebModuleDeployment">
<targetMappings target="ServerTarget_1" xmi:id="DeploymentTargetMapping_567"/>
</modules>