Upgrading JDK Used by SAP Applications


It is very important to keep up with SAP's recommendation to upgrade the JDK to the recommended release. If you ever take J2EE specific performance issues to SAP, upgrading to the latest JDK would be one of their recommendations. SAP note 709140 is the central note pointing to other SAP notes on JDK recommendations.

You must go through the note specific to the JVM you use to check for any pre-requisites.

Here are some steps that you will have to follow regardless of the JDK you use, when upgrading JDK.

1. Check SAP notes for pre-requisites to apply the latest recommended JDK and implement them.
2. Upgrade the JDK.
3. Reinstall "Unlimited Strength Jurisdiction Policy Files". You will have to implement this step even if you were using unrestricted policy files earlier as these files would be replaced by the upgrade.
4. Check the java vesion as <sid>adm to ensure that the new JDK is reflecting. If not, please ensure that the JDK was installed at the same path.
java -versionjava -fullversion
5. If you are using SMD agents, recompile the AutoProbeConnector.jar file uysing the following command:
java -Dcom.wily.autoprobe.prependToJVMRuntimePath=/usr/java14_64/jre/lib/jclSC14/classes.zip -jar CreateAutoProbeConnector.jar -jvm /usr/java14_64 -output AutoProbeConnector.jar
The above command assumes that the java home is at /usr/java14_64. Adjust the command according to your java home.
6. Delete the instance.properties.vmprop file in the /usr/sap/<SID>/<instance>/j2ee/cluster directory.
7. If the java parameters are required to be changed for the new JDK, make those changes using config tool.
8. Start the applications and check the trace files to confirm that the new JDK is being used.

Be prepared to replace your JDK with SAP's JDK. 1.4.2 JDKs will be out of support soon and as a result SAP have released its own JDK to help continue usage of SAP applications that run on 1.4.2

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more