How do I upgrade the jre of websphere server stub? - macos

I'm trying to connect to a remote server websphere server from my mac. I am using the websphere traditional v8.5 stub. I am able to connect to the server (my remote server is using java 8) but I am having some issues when compiling and running my code. I am getting an error saying project facet java 1.8 is not supported by WAS 8.5. I can see when I set my project facets to java 1.8 no runtimes are available. I attached the image of my project facets. I know where it says runtime compositions I need to get that up to java 1.8 instead of 1.7. I know how to do this on windows but I cannot find any info on how to do it using mac with the remote server stubs. Thanks in advance for any helpenter link description here
enter image description here

You might need to update your IDE. Java 8 wasn't supported until 8.5.5.9.

Related

Does anyone know if the ibm jdk associated with websphere 8.5.5.19 supports debugging via jpda using dt_socket option on windows 10?

Intellij automatically generates read-only debug options that include dt_socket but we are using this ancient jvm that "may" only support dt_shmem on windows. Just want to know for sure that it will never work with the version of intellij we are using.
rtfm says https://www.ibm.com/docs/en/sdk-java-technology/8?topic=applications-debugging-java
Secondary followup question. Is it possible to run websphere 8.5.5.19 on the oracle or openjdk jvm in a non-production environment.
dt_socket works on Windows as well. The documentation is a bit misleading in that dt_shmem is only an option on Windows.
For the record, that probably isn't an ancient JVM in there unless it just hasn't been updated. If you updated the JDK when you updated WAS to 8.5.5.19, it would have a version of Eclipse OpenJ9 from about a year ago (and Eclipse OpenJ9 is single source across all JDK releases, so it includes all the same JVM goodies as in recent JDK releases).

Is there a way to activate earlier Java version in Websphere Application Server 8.5?

When I was installing WAS, there was a prompt alerting me to use Java 8 by default. I aggreed, because back then it wasn't matter which version to use.
Time passed and now I have necessity to use Java 6 in one of my profiles, which is coming with the WAS by default. Since I aggreed to use newer Java, WAS working on Java 8 by default now. I searched in installation repository, but in IBM Installation Manager Java versions I need are greyed out and cannot be installed separately.
Is there a way to install Java 6 alongside Java 8 in WAS, so I could just switch between them in profiles' setting? I tried official repository for Java 6, but it is empty since IBM dropped it's support in April.
P.S. I tried to change variable JAVA_HOME in Websphere profile setting (as well as in system variables) to look at JDK 1.6 I installed separately, but then my profile refuses to start.
Java 6 is no longer supported, so the WAS Installation Manager has likely removed the option to use JDK 6. For WAS 8.5 you can use either Java 7 or Java 8.
This article talks more about Java 6 End of Support:
https://developer.ibm.com/wasdev/blog/2017/10/25/java-6-end-support/

Pentaho BI Server won't run on my 32bit Windows 7 computer

My 32bit Windows 7 server is running Pentaho bi server ce 7.0.
Everything seemed to install fine, but I'm having trouble getting the server to run.
Attempt 1
Everything seems OK after running start-pentaho.bat and accessing localhost:8080, however accessing localhost:8080\Pentaho\login returns an error.
Attempt 2
I am unable to access the site after running start-pentaho.bat and accessing localhost:8080.
Can anybody help?
It seems that the BI Server is only supported on 64-bits OSes all the way back to version 5.1. The documentation for 4.4 is already gone from the Pentaho support site.
https://help.pentaho.com/Documentation/7.0/0D0/160/000

IBM MobileFirst 7.0 Windows8 App connection issue after iFix

We recently implemented MobileFirst 7.0 IF201609291531 iFix and started experiencing a windows 8 app connection issue when a new runtime is created on the server and a windows8 app uploaded:
The windows8 App is deployed on a device via App Center
When the windows8 app attempts to connect, the server log records the message:
FWLSE0332E: The application some_app for the environment windows8 does not exist on the server. Cannot register this client.
I double checked that the app was in fact deployed on the server, I confirmed the version number, app id, and server details in the wlclient.properties file. The same build process also deployed an Iphone and Android app, both of which works and connects correctly.
I decided to change the windows8 application access to "Active, notifying" just as a test. The console did not save the message, and when I looked at the log, it recorded:
000000e5 com.ibm.worklight.admin.actions.BaseTransaction E Result: newruntime: mobileFirstServer///XX.xx.X.xx: There is no deployed application with name 'some_app-windows8-2.0.25'
I managed to set the application access for both the iPhone and Android apps without any problems.
This behaviour is only evident on any new runtimes created since the ifix was installed. When I upload the windows8 app to a runtime that existed before the ifix it connects as expected.
I've tried this on multiple MobileFirst servers with the ifix loaded and the behaviour is consistent across all of them.
My build setup is as follows:
The binaries are built using MobileFirst CLI (initially with IF201607241420, and then with IF201609291531) using Jenkins
The binaries are then uploaded and deployed to the MobileFirst server using the worklight_build.xml ant script
Server OS: RHEL 7.0
MobileFirst configuration: standard Liberty profile
DBMS: MySQL
Has anyone experienced this before? Could it be a database or permission issue?
Our sys admin is planning on removing the ifix on Monday, after which I'll run another test to see if it resolves the issue. I'll post the result of the test here.
It's clear you are experiencing some kind of a regression with the latest iFix. I suggest then that you'll just open a PMR. This is not a question for Stack Overflow.
I have found a work-around for the issue.
It seems the issue occurs if a new runtime is deployed via the ant scripts, and the application is also deployed via ant scripts (no manual deployment was done). When I manually deployed the application via the web console it resolved the issue. This manual upload seems to only be required once, after that the app continued to connect as expected even with subsequent ant uploads.

Can the code developed and running in Websphere application server v5.1 run in Websphere application server v6.0/6.1/7.0?

Can the code developed and running in Websphere application server v5.1 run in Websphere application server v6.0/6.1/7.0 without any problems?
My scenario:
Originally, the application developed using Java 1.4 and WAS v5.1. As part of change request, we are going to do some changes in that application.
Currently, in my development environment i have RSA(Rational Software Architect) 7.5. It complaint with only WAS v6.0/6.1/7.0. So i can work with one of these WAS version.
Which version i can choose to work for development WAS v6.0/6.1/7.0?
But finally the developed/changed code in WAS6.0/6.1/7.5 will be deployed in WAS v5.1(PRODUCTION) only. I am worried about whether code will run properly or not.
Will i get any complaint problem in this scenario?
Thanks in advance.
The most important is not to change your compiler settings from 1.4 to the RSA 7.5 default which I believe is 1.5.
In case you compile your source code with higher version of Java and deploy it in a Container which runs on a lower version you are going to have trouble.
Generally it is safe to run and test your legacy app on a higher WAS version but keep your eyes on the compiler settings as I mentioned.

Resources