I have a Websphere profile which has 2 nodes. I can login into the
https://localhost:9044/ibm/console/
and click on the Application Server, I can only see the Node02 applications as the header is
Cell=Node02Cell, Profile=AppSrv02.
Actually in the
c:/IBM/Websphere/profile/,
there are 2 servers AppSrv01 and AppSrv02, both are startup. May I know how to see Node01Cell server and applications?
In addition to Alasdair answer, in case of WAS base, if you want to manage all servers on the same host you can use Admin Agent profile. You would need to create new profile and register your profiles in the admin agent.
Then you will be able to manage both servers via single console, selecting during login, which server you want to manage.
For details see Setting up the administrative agent environment
I'm assuming from your question that the two servers are in different sub directories of the one quoted. Assuming you are using the WAS base product there is no way to see both profiles in single admin console at once. You can use WebSphere Application Server Network Deployment and federate two different profiles into the same cell at which point you could see both of the servers. With base you can use the admin agent to manage two profiles on the same machine, but you would manage each profile individually.
I am assuming that you installed two stand-alone application server profiles with individual console. To create a clustered or multiple node setup, you will need to install a Deployment Manager profile as your main console then add two nodes to be federated by the Deployment Manger.
See: Installing WebSphere Application Server
Related
Encountered a requirement in our team when trying to migrate a WebSphere application into Tomcat and deploy onto Pivotal Cloud Foundry to have same application to connect to two different databases which have entirely same schema with different data, essentially having same application code deployed in different paths and be able to connect to the databases based on the URL being called for accessing the application.
Currently, we handle this situation in Websphere by using the deployment script to deploying the application into two servers and give the different database details in JNDI and access the application using the server names.
We use Jenkins to deploy the application onto PCF.
Tried to use maven to deploy on to different context paths which did not help and have ended up in the loop, Have anyone encountered a situation like this, Any thoughts would be appreciated.
I think there are a number of ways you could handle this.
Modify your application so it's aware and let's you pick. Perhaps have a query parameter to select or /dev/blah goes to one DB and /test/blah goes to another.
Push the same application twice, but bind different databases and routes to each app.
Attempt to run two instances of the same app code inside Tomcat in one app on CF.
Of those, #1 is fine but would probably require code changes. #2 would be my choice as it's very quick to do, #3 would be a lot of work because you'd be fighting against the Java buildpack, which is not recommended.
To accomplish #2, you would do the following:
Push your app code as app-A.
Bind the database service.
Map a route with a context path like my-cool-app.example.com/app-a.
Start your app.
Repeat the same for app-B, but use a different database and route/path (i.e. my-cool-app.example.com/app-b)`.
If you are deploying a WAR file, you will need to tell the Java buildpack to deploy your app on a context path (it should match the route context path you set).
cf set-env my-application JBP_CONFIG_TOMCAT '{tomcat: { context_path: /app-a }}'
https://github.com/cloudfoundry/java-buildpack/blob/master/docs/container-tomcat.md#common-configurations
If you're using Spring Boot and a JAR deployment, you'd need to set server.contextPath=/app-a.
Hope that helps!
I have been trying WildFly as application server for a production enviroment, however I have few doubts that I can't answer with the documentation or previous questions.
In the domain mode using the same machine, I have created two server group that are containing one server each one, this is with the idea of isolate two different production enviroments. The problem with the dataSource, is that obviously I have to create them in the profile associated to the server group, but always that I create a new dataSource I need to restart de group, this is a problem since I can't restart the servers for doing this.
Is there a way to do this in a more friendly way?
I'm currently using WildFly 13 and the HAL console to admin the servers.
According to JBoss documentation:
In managed domain deployments are associated with a server group.
Deployments will be provided to any server that belongs to a
particular group.
...the multiple servers in common server group become the single one virtually.
But how does JBoss choose the target actual server for deployment?
For example, i have two different vps servers with JBoss running, which are combined to the single main-server-group. Then which vps server will actually host the application by following command?
[domain#localhost:9999 /] deploy ~/Desktop/test-application.war --server-group=main-server-group
'test-application.war' deployed successfully
The application will be deployed to both servers.
If you were to go to http://server1:8080/MyApp you should see the same as if you went to http://server2:8080/MyApp
The reason for this is that you would normally have a web server or proxy to load balance between the two servers. If you want to have two separate servers which don't have the apps deployed to each, then put them in different server groups or, a better solution would be to run JBoss in standalone mode, rather than domain mode.
I have a server on which should running several Demo Applications on JBoss. The applications are exactly the same like each other. Only the ports for the web access, used database and so on should be differ (so each customer has an separate access to his demo system). All demo applications should be running on the same machine / operating system.
Whats the best/correct way? Standalone (with different JBoss instances for each demo application; see also here)? Or the domain mode with different JBoss server/server-groups for each demo application?
This depends on if you want to manage your servers from one location (so called Domain Controller) - it will give you the ability to control all servers (hosts in this case), deploy apps and configure them from one management console. If you need this, you could benefit from Domain Mode. If not, there is no reason why you shouldn't have separated instances of JBoss in standalone mode and control them separately, both options are perfectly fine.
We have already created 2 JAVA web applications A & B and hosted it on 2 different
servers using TOMCAT on both these servers. These applications have already been moved
to production and we cannot make any major changes or move it to a single server as it is not in our control.
The authentication is being done through a common LDAP server which is being used by many other applications also.
Now, the client wants us to create a new application C and once logged in, the end users should be able to access the above 2 Applications A & B(through links) without having to
re-login again(SSO).
Pls advise on how to implement the same.
CAS seems the right solution for this but I don't see how you could do to avoid touching anything.
You will at least have to touch some config files.
Look at:
- Spring Security and CAS Integration
Regards