During the lifecycle of a custom Java application, based on SAP Netweaver, it happens that archive name(s) change with the new version of the software. As SAP Software logistics logic rely on archive name (to find the application components successors), there is special treatment build in the update and upgrade Java tools called refactoring.
Example: existing application has version 1.x.x and the new release 2.x.x comes with different number SCAs. Some of the SCAs have changed name and, in addition, some SDAs inside were removed.
The mapping between old source (SCA/SDA) components and the new target components is done with the help of a specific configuration file (.sap-refactoring) which should be packed in new target (2.x.x) SCA. You need one SCA which haven't change its name between 1.x.x and 2.x.x release which contains .sap-refactoring file. This .sap-refactoring file will describe structural changes of all you components and the upgrade tool will use it to map the detected source component to the new target components.
How to delete a development component:
Note
<?xml version="1.0" encoding="utf-8"?>
<refactoring
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation=".sap-refactoring_1_0.xsd">
<sc>
<guid>00000000-0000-0000-0000-000000000000</guid>
<textIDList>
<textID>
<vendor>sap.com</vendor>
<name>YOUR-SC-NAME</name>
<when>
<date>2000-01-01</date>
</when>
</textID>
</textIDList>
<dcList>
<dc>
<guid>00000000-0000-0000-0000-000000000000</guid>
<textIDList>
<textID>
<vendor>sap.com</vendor>
<name>YOUR-DC-NAME</name>
<when>
<date>2001-01-01</date>
<refactoringSlot>preDeployment</refactoringSlot>
</when>
</textID>
</textIDList>
<deletedList>
<deleted>
<when>
<date>2001-01-01</date>
</when>
</deleted>
</deletedList>
</dc>
</dcList>
</sc>
</refactoring>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
10 | |
10 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 |