XI SDM Deploy update Support Package

[Former Member]

Dears,

After a updated support package in our XI development to JSPM sp13 (e.g.example), asked to do a restore database, we restored succesfully the database and actually our support package is JSPM sp9 (e.g.example), We tried to update to SP13 but we received a message;

"SDM has not calculated any deployment actions, Possible reasons: All selected archives have already been deployed before in the same or in a higher version".

In our restore we just restored the database, we're afraid if this problem is relationed with this.

Can you help me with this?

Thanks in advanced

Cristiano

[Former Member · Accepted solution]

This message means, SDM sees that the version you are trying to deploy is already there on the system and so it doesn't take any further action. If you are using SDM to deploy the packages, on the deployment tab - when you click on the lower right side, a small triangle button, it shows 3 options. By default, first option is selected which tells SDM to not deploy the packages if it finds the same version on the system. You can choose option 3 which will deploy the packages regardless.

If you are using JSPM, you can update the forcemode to update all SCAs regardless of the version.

1. You can change the deploy version rule for SDM / Deploy Controller.

In /usr/sap/<SID>/<Central instance

name>/j2ee/JSPM/param/jspm_config.txt file, add the

'/jspm/deployVersionRule' property.

You can use one of the following values:

o updateLowerOnly - updates only newer counters (the default

behavior)

o updateSameAndLower - updates components whose counters are higher

than or the same as the counters of the components that are

already deployed

o updateAll - updates all components regardless of their counters

This property affects only SDAs.

2. It is possible to display and allow for patch also software

components whose support package and patch levels are the same. This

allows you to redeploy software components whose support package and

patch levels are the same as the ones of the software components that

are deployed in the system. In the /usr/sap/<SID>/<Central instance

name>/j2ee/JSPM/param/jspm_config.txt file, add the '/jspm/forceMode'

property.

You can use one of the following values:

o false - force mode is disabled (the default behavior)

o true - force mode is enabled. For versions lower than SP10 only -

this also changes the '/jspm/deployVersionRule' property to at

least 'updateSameAndLower'. In versions SP10 and later (as well

as in 7.10) property '/jspm/deployVersionRule' is not affected by

property '/jspm/forceMode'.

This property affects only SCAs.

Note: Different configuration files are used in different scenarios. So

check below which file you have to edit.

o jspm_config.txt - JSPM standalone GUI, started with go script

o jspm-srv_config.txt - A1S LiveUpdate, CEUPDATE tool, CE Update

Manager

o jspm-cmd_config.txt - JSPM command line, i.e. jspm_cmd or sl_auto

scripts

Hope the above helps.

Regards,

Snehal