About some years ago SAP release the Software Update Manager (SUM) and they decided that both JSPM and SDM were not worthy of being use to patching a Java system.There are plenty of guides about JSPM on the Internet since it was the most popular tool on those days. With the JSPM you could patch a full SPS, a single SP, install new software components, etc. The JSPM has a lot more features than the SDM and it was the standard tool for patching a JAVA NW. About the same time there was another thing named Java Support Package Manager (JSPM) which was an interface between the user and the SDM.There is a small guide about SDM right here. You could use the SDM to deploy/undeploy SCA files individually and to check which software components where installed within the JAVA system. Long time ago there was a thing named Software Deployment Manager (SDM).You will have lots of fun, I promise! A short history of patching JAVA stacksĪnyway, for you freshers that don’t know what I’m talking about here it’s a small explanation about patching JAVA stacks during the last years: Easy right? Otherwise you can go really crazy and try to patch a JAVA stack using NWDI. In the case of a JAVA stack you only need to download the files and select the directory during the SUM execution. For example, for using the Software Update Manager with an ABAP stack it is necessary to have a XML file in order to patch the system. Despite of this I must admit that patching a JAVA stack is becoming easier during the last years. There are a lot of tools and transactions from ABAP stacks that I really miss when I’m working with a JAVA stack. JAVA stacks for SAP NetWeaver AS are not my favorite thing in the world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |