Skip to main content
Solved

Cloud Instance for Java Development not working

  • July 17, 2024
  • 1 reply
  • 100 views

Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • 12 replies

We are trying to implement some Java code for our IFS Cloud system. The versions of our environment are:

  • Application service update: 23.2.3
  • Framework service update: 23.2.7
  • IFS Cloud Web version: 23.2.7.20240605150108.0
  • IFS OData provider version: 23.2.7.20240605053529.0

I set up a remote minikube server and managed to connect my local kubectl with it. I also tried to install it locally, but this is unfortunately not an option. With kubectl running, I went through the steps described here: Technologies - Technical Documentation For IFS Cloud

 

I managed to start the application server and got the following output:

secret "ds-db-secret" deleted
secret/ds-db-secret created
secret "ds-docker-secret" deleted
secret/ds-docker-secret created
deployment.apps/ifsapp-mock-iam created
service/ifsapp-mock-iam created
deployment.apps/ifsapp-client created
service/ifsapp-client created
deployment.apps/ifsapp-client-services created
service/ifsapp-client-services created
deployment.apps/ifsapp-odata created
service/ifsapp-odata created
deployment.apps/ifs-file-storage created
service/ifs-file-storage created
pod/ifsapp-odata-84766bc845-sfh89 condition met
Forwarding from 127.0.0.1:8080 -> 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080

At the end it’s mentioned that I have to open http://localhost:8080/main/ifsapplications/web/start

I can see that something is running, but not what I was hoping for:

I haven’t found anything in the documentation or here in the community.

Thanks for any idea on how to get this working.

Best answer by Remo

It turns out to be much easier than I thought. I had to execute the following commands on my server:

kubectl get pods

kubectl logs ifsapp-odata…. (take exact name from previous command)

There I saw that my port 1521 is being blocked. A quick change to the firewall and it works!

View original
Did this topic help you find an answer to your question?

1 reply

Forum|alt.badge.img+4
  • Author
  • Do Gooder (Customer)
  • 12 replies
  • Answer
  • July 18, 2024

It turns out to be much easier than I thought. I had to execute the following commands on my server:

kubectl get pods

kubectl logs ifsapp-odata…. (take exact name from previous command)

There I saw that my port 1521 is being blocked. A quick change to the firewall and it works!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings