Dear SDN Users!
You might have participated in our Share your SAP NetWeaver AS-JAVA upgrade/update experience and earn SDN points! on Java Update and Upgrade Feedback and wonder what the results are and which actions were triggered based on this feedback.
In this Blog I’d like to give you an overview on the most important results and improvements you can expect to see in the area of Java Update and Upgrade.
As expected most respondents were giving feedback about JSPM (76%) and not for SAPJup (24%). We were pleased to hear that most customers (79%) used these tools without external support. This is a clear indication that the tool development heads into the right direction and that administrators with up to medium skills can use the tools – 58% of the respondents fall into this range. At the same time 82% of the respondents are overall satisfied or very satisfied. The largest dissatisfaction was in the area of downtime, 21% of the respondents would like to see a shorter downtime. Surprisingly only 22% of the people would use a possible advance mode of our tools to tweak all possible parameters. This shows that the basic parameterization of JSPM / SAPJup is acceptable for a broad range of customers. For the 22% of respondents who want to change as many parameters as possible the jspm_config.txt file has been better documented in the JSPM user guide.
Of course no software will be ever perfect, so you came up with lot’s of great ideas for improvements. Some of the improvements can be found already today in the product, some will be available with NetWeaver 7.1 others are introduced into the planning cycle for the next release of NetWeaver beyond NetWeaver 7.1.
All statements made here are subject to change without further notice!
One of the most often requested features was a better handling of JSPM on UNIX boxes in terms of remote connection. The requested feature is implemented in NetWeaver 7.1. Since changes in the infrastructure were necessary this feature can’t be ported to NetWeaver 7.0. Check SAP’s online help system here how to connect remotely to JSPM.
Another point mentioned frequently was the integration of MOPZ (Solution Manager Maintenance Optimizer) and JSPM. A tighter integration of both tools has been achieved with EhP 1 of NetWeaver 7.0 for business suite systems and will be extended to include NetWeaver systems in the future, including CE.
Some users reported issues with the XML stack definition file, these fall into the same category since the tighter integration of MOPZ and JSPM will reduce the risk of potential failures greatly. Some best practices about the handling of the XML stack definition file can be found SAP NetWeaver Support Package stack guide – the starting point when updating your system.
Last but not least the inclusion of patches into the stack download is already available with MOPZ.
Apart from the performance improvements done in the latest SPs further improvements are planned for the next NetWeaver release after NW 7.1. It is planned that with the usage of an XML stack definition file not the whole inbox gets scanned but only the items in the XML file. For very large inboxes this should result in a much better performance. Though, SAP’s recommendation to keep the inbox of JSPM as lean as possible remains the same.
Some usability improvements are planned for the future. These include among others the select/de-select of all components for update, additional password checks as well as supportability improvements.
Some uncertainties of the kernel update process existed and thus an additional note 1167830 was created and should help to avoid issues in the future.
Finally the un-deployment of usage types is planned to be supported with a future release of NetWeaver.
I hope this gives you a good overview what changes you can expect and what impact your participation had on the product.
Jochen Rundholz (SAP NetWeaver Regional Implementation Group (RIG) APJ)