Recycling Software Update Manager for own Java-Deployments?

[raphael_ostermann-goletz]

Hello,

we develop our own Java-components in the NWDI-environment an deliver them to our customers who had to install them - until now with JSPM but in the future with SUM (Software Update Manager).

Our Java-software is based on a specific SAP-Stack, and corrections use the same base in our release. So, the customer needs to run the same SUM version every time in our release.

Now, we search a simple deployment strategy without cleaning und reinstalling SUM (SUM is designed only to use once).

Is there a way, to recycle an installation of SUM to deploy new Patches (.sca-Files) of Non-SAP-Developments?

Thanks & Best regards

Raphael

[ashish_vikas]

You can keep SUM.SAR archive downloaded and next time you can just remove old SUM directory and extract .SAR again to use.

Also, telnet can be used for .SCA deployment.

best regards

ashish

[raphael_ostermann-goletz]

Hello Ashish,

thank you for your answer. The hint with telnet-deploy is interesting. I tested it with one sca, but the result was negative (why?):

Deploying test.sca
        Result: Failed
        Description: The archive [/usr/sap/MZE/J27/j2ee/deployment/scripts/../SAP_DM/1390393587534_test.sca/test.sca] is not recognized as a valid Java EE Application or Module according to JEE 5

So i tried it with SUM (deleting old SUM-directory, newly extracting existing SUM-SAR-File, starting) - with success on the same test.sca. Where is the difference between SUM and deploy-script?

The point of the wish to recycle SUM is, that for example if one uses the Target System Version "Manually prepared directory" and then select only a subset of the offered components (the other components are selected as "skipped"), the consequence is, that SUM can't be run for the other previously skipped components. Or is there any option or method to clean up SUM in an easy way?

Best regards

Raphael