Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi,

Please find the IBM note re. fix pack 22 and Java 7. Refer https://www.ibm.com/support/pages/node/6605409

Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server:

• z/OS and Distributed users must uninstall Java SE 7 and 7.1 offerings before upgrading to 8.5.5.22 and later.

This is why you cannot apply fix pack 22.

To apply fix pack 22, after you have switched all your components from Java 7 to Java 8, you'll need to remove the optional Java 7 package. Once you uninstall the optional Java 7, versionInfo.sh will no longer list Java 7. Be sure to ensure you still java the old packages in case you need to rollback for any reason.

You can verify using managesdk.sh -listEnabledProfileAll

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi Sean,

Many thanks for the link. 

1. I have uninstalled all  JavaSDK 1.7 from the Dmgr + AppServ01(co-locate) and from all the other AppSrv01 profiles from the other 5 nodes.
2. stopped all the services on all the nodes
3. Through installation manager (./IBMIM) updated fixpack22 on Dmgr + AppServ01 node successfully. No errors occurred and services started successfully.
4. When I'm updating other nodes for fixpack22, Installation Manager pops up some warnings of not updating IBM JAVASDK 7, as it was not found. Also when i run ./managesdk command . ..it says javaskd 7 not found.

Hi,

Please find the IBM note re. fix pack 22 and Java 7. Refer https://www.ibm.com/support/pages/node/6605409

Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server:

• z/OS and Distributed users must uninstall Java SE 7 and 7.1 offerings before upgrading to 8.5.5.22 and later.

This is why you cannot apply fix pack 22.

To apply fix pack 22, after you have switched all your components from Java 7 to Java 8, you'll need to remove the optional Java 7 package. Once you uninstall the optional Java 7, versionInfo.sh will no longer list Java 7. Be sure to ensure you still java the old packages in case you need to rollback for any reason.

You can verify using managesdk.sh -listEnabledProfileAll

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi Faisal,

The error logs mentioned should provide some assistance.

I've replied to your email. From the above error and the other details you provided me it seems that maybe the switch from Java 7 to 8 may not be fully complete on the nodes you are having problems with.

------------------------------
Sean Boyd

Original Message:
Sent: Tue August 29, 2023 03:59 PM
From: Muhammad Faisal Syed
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi Sean,

Many thanks for the link. 

1. I have uninstalled all  JavaSDK 1.7 from the Dmgr + AppServ01(co-locate) and from all the other AppSrv01 profiles from the other 5 nodes.
2. stopped all the services on all the nodes
3. Through installation manager (./IBMIM) updated fixpack22 on Dmgr + AppServ01 node successfully. No errors occurred and services started successfully.
4. When I'm updating other nodes for fixpack22, Installation Manager pops up some warnings of not updating IBM JAVASDK 7, as it was not found. Also when i run ./managesdk command . ..it says javaskd 7 not found.

------------------------------
Muhammad Faisal Syed

Original Message:
Sent: Sun August 27, 2023 04:36 AM
From: Sean Boyd
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi,

Please find the IBM note re. fix pack 22 and Java 7. Refer https://www.ibm.com/support/pages/node/6605409

Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server:

• z/OS and Distributed users must uninstall Java SE 7 and 7.1 offerings before upgrading to 8.5.5.22 and later.

This is why you cannot apply fix pack 22.

To apply fix pack 22, after you have switched all your components from Java 7 to Java 8, you'll need to remove the optional Java 7 package. Once you uninstall the optional Java 7, versionInfo.sh will no longer list Java 7. Be sure to ensure you still java the old packages in case you need to rollback for any reason.

You can verify using managesdk.sh -listEnabledProfileAll

------------------------------
Sean Boyd

Original Message:
Sent: Fri August 25, 2023 03:40 AM
From: Muhammad Faisal Syed
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

------------------------------
Muhammad Faisal Syed

Original Message:
Sent: Thu August 24, 2023 11:35 AM
From: Sean Boyd
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

------------------------------
Sean Boyd

Original Message:
Sent: Thu August 24, 2023 08:35 AM
From: Muhammad Faisal Syed
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

------------------------------
Muhammad Faisal Syed

Original Message:
Sent: Thu August 24, 2023 02:51 AM
From: Sean Boyd
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

------------------------------
Sean Boyd

Original Message:
Sent: Wed August 23, 2023 04:37 AM
From: Muhammad Faisal Syed
Subject: IBM WebSphere Application Server 8.5.5 fixpack 22 update and JavaSDK 1.8 selection

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

------------------------------
Muhammad Faisal Syed
------------------------------

Hi,

Thanks again for the support. I am trying to update all the services to 1.8_64_bundled. 

Hi Faisal,

The error logs mentioned should provide some assistance.

I've replied to your email. From the above error and the other details you provided me it seems that maybe the switch from Java 7 to 8 may not be fully complete on the nodes you are having problems with.

Hi Sean,

Many thanks for the link. 

1. I have uninstalled all  JavaSDK 1.7 from the Dmgr + AppServ01(co-locate) and from all the other AppSrv01 profiles from the other 5 nodes.
2. stopped all the services on all the nodes
3. Through installation manager (./IBMIM) updated fixpack22 on Dmgr + AppServ01 node successfully. No errors occurred and services started successfully.
4. When I'm updating other nodes for fixpack22, Installation Manager pops up some warnings of not updating IBM JAVASDK 7, as it was not found. Also when i run ./managesdk command . ..it says javaskd 7 not found.

Hi,

Please find the IBM note re. fix pack 22 and Java 7. Refer https://www.ibm.com/support/pages/node/6605409

Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server:

• z/OS and Distributed users must uninstall Java SE 7 and 7.1 offerings before upgrading to 8.5.5.22 and later.

This is why you cannot apply fix pack 22.

To apply fix pack 22, after you have switched all your components from Java 7 to Java 8, you'll need to remove the optional Java 7 package. Once you uninstall the optional Java 7, versionInfo.sh will no longer list Java 7. Be sure to ensure you still java the old packages in case you need to rollback for any reason.

You can verify using managesdk.sh -listEnabledProfileAll

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.

Hi Boyd,

Many many thanks for your support, issue has been resolved now.

I'm following this roadmap now which works fine.:

1. WAS ND Cluster Nodes upgrade to fixpack14 along with JAVA8 SDK 8.0.5.17 from previous fixpack11. This updates all for example : PROFILE_COMMAND_SDK, NODES, T24Srv01, nodeagent SDK, webserver1 SDK.
2. Uninstall IBM JAVA SDK 7
3. Install fixpack22 

All done.

Hi,

Thanks again for the support. I am trying to update all the services to 1.8_64_bundled. 

Hi Faisal,

The error logs mentioned should provide some assistance.

I've replied to your email. From the above error and the other details you provided me it seems that maybe the switch from Java 7 to 8 may not be fully complete on the nodes you are having problems with.

Hi Sean,

Many thanks for the link. 

1. I have uninstalled all  JavaSDK 1.7 from the Dmgr + AppServ01(co-locate) and from all the other AppSrv01 profiles from the other 5 nodes.
2. stopped all the services on all the nodes
3. Through installation manager (./IBMIM) updated fixpack22 on Dmgr + AppServ01 node successfully. No errors occurred and services started successfully.
4. When I'm updating other nodes for fixpack22, Installation Manager pops up some warnings of not updating IBM JAVASDK 7, as it was not found. Also when i run ./managesdk command . ..it says javaskd 7 not found.

Hi,

Please find the IBM note re. fix pack 22 and Java 7. Refer https://www.ibm.com/support/pages/node/6605409

Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server:

• z/OS and Distributed users must uninstall Java SE 7 and 7.1 offerings before upgrading to 8.5.5.22 and later.

This is why you cannot apply fix pack 22.

To apply fix pack 22, after you have switched all your components from Java 7 to Java 8, you'll need to remove the optional Java 7 package. Once you uninstall the optional Java 7, versionInfo.sh will no longer list Java 7. Be sure to ensure you still java the old packages in case you need to rollback for any reason.

You can verify using managesdk.sh -listEnabledProfileAll

Hi,

Following the selection of Java 1.8, through WAS Console> JAVASDK selection, still Java 1.7 is shown on the versionInfo.sh. 

also when I try to update fixpack 22 following message is shown:

HI,

The process you followed looks good. If you are seeing Java 8 in the logs you should be good-to-go.

versionInfo.sh will show what installed and available to use on your system. By using managesdk.sh you can select which java version to use for your app. This you did and your logs show this is working fine.

FYI - you can also check the java version being used in the WAS admin console (in case you are not aware): Servers -> Server Types -> WebSphere application servers -> your server name -> Java SDKs. This view should give you confidence with your setting.

Below is a view from versionInfo.sh for one of our apps still using Java 7 on AIX. As can be seen the Java 7 package is still showing. (Unlike what you are trying to do, we are actually still using Java 7 for this one app).

When we switched most of our apps from Java 7 to Java 8 many years back, we followed a similar process to the one you described. After we switched to Java 8 for the apps, we kept the Java 7 package installed for some time just in case we needed to rollback (it would simplify the rollback should we need to do so). So even though our app was running Java 8 (and our logs showed the same), versionInfo.sh still showed Java 7 installed (but not used).

Later, when you uninstall the optional (I assume you are seeing it as optional) Java 7 package, it will disappear.

If you are seeing different, or I have misunderstood anything, please let me know.

Product List
--------------------------------------------------------------------------------
IBMJAVA71                installed
BASE                     installed

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere SDK Java Technology Edition (Optional)
Version               7.1.5.0
ID                    IBMJAVA71
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.IBMJAVA.v71_7.1.5000.20220202_1042
Architecture          PPC64
Installed Features    IBM WebSphere SDK for Java Technology Edition Version 7.1

Installed Product
--------------------------------------------------------------------------------
Name                  IBM WebSphere Application Server
Version               8.5.5.21
ID                    BASE
Build Level           cf212205.01
Build Date            2/2/22
Package               com.ibm.websphere.BASE.v85_8.5.5021.20220202_1245
Java SE Version       8
Architecture          PPC64
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Hi,

Many thanks for your response, you are right Installation Manager stops when updating fixpack 22 on (in my case) WAS 8.5.5.14. So i first need to switch to 1.8

Since in my WAS environment there are two java sdks i.e 1.7 and 1.8, whereas as 1.7 is currently selected as default, and I wanted to make JavaSDK 1.8 bundle-up as the default javaSDK,  So I performed the following:

Result:

Although SystemOut. is showing Java 1.8 in the start of the logs. but "versionInfo.sh" still showing sdk 7.

Any suggestion?

Hi Muhammad,

1. 

While I have never seen issues when we run mixed versions of IHS and WAS, in your case I'd suggest you upgrade WAS plus IHS and the Plugin to the same version. This will also ensure you get the latest security and bug fixes also.

2. 

I cannot remember which fix pack version it is, but I know there was a change somewhere around your fix pack version where bundled Java 8 became the default. And later that optional Java 8 became unsupported.

You can still use Java 7 as an optional package - we still do for a couple apps. You can manage all this using managesdk.

But, Java 7 came out of support in July 2022 so you may want to explorr the option, if possible, of updating your app to support Java 8.

You will find you'll be encouraged to do this at some time. Refer the comment in the fix pack 22 release notes "Fix pack 8.5.5.22 and later will not install if Java 7 or 7.1 are in use by the application server …". For our Java 7 apps we have only updated to 8.5.5.21 due to this comment. I have not tried applying 8.5.5.22 for these apps but the comment is quite clear that it won't be possible.

So to answer your question, when you apply the later fix pack the default java will automatically switch from java 7 to bundled java 8. You then use managesdk to switch your app to use optional java 7. It is quite straightforward but I will admit I found it a little confusing at first.

Of course ensure you test in a dev environment and I would also suggest you test your rollback process to ensure should you encounter problems you have tested and got confident with the process to rollback. This will be a slightly different fix pack than you're probably used to.

Hi,

We have a IBM WebSphere Application Server ND 8.5.5.14 clustered(horizontal) environment of 6 nodes with IHS on all 6 nodes on AIX.

Need suggestion for the following two tasks

1. If we have to update a fixpack 22 , should we only select WebSphere Application Server 8.5.5 through "Installation Manager" or select all components such as IHS and plugins and download their fixpack as well.
2. We have Java SDK 1.7 selected as a default, whereas other Java SDK 1.8 bundled-up needs to be selected. What should be the step-by-step procedure to followed for the selection of JavaSDK 1.8.

Appreciate response.