Can we create multiple servers in the websphere application server profile
Usually the default is server1 gets created , when you create the stand alone instance.
Yes, you can via wsadmin scripting, check details here:
Creating a server using scripting
however by default to configure and install app on that server you will need to use console installed on server1 or scripting, so it is a bit troublesome. That server will also share some configuration settings with server1 e.g. security settings.
If you want more isolation it is usually easier to just create another Application Server profile, from the same WebSphere installation (using Profile Management Tool, or manageprofiles script).
Related
Hi I want to include cluster option in IBM 8.5 where it is installed on Linux how to add this package through the terminal where in my server menu I have only server types
Your question is not clear enough, but here are my assumptions:
you are using WebSphere Application Server 8.5.5.x
you want to have cluster options in the Web Administrative console (accessed via /ibm/console)
You currently have standalone single server profile, this profile doesnt have cluster management capabilities. You have to create different profile - deployment manager - either via graphical UI - https://www.ibm.com/docs/en/was-nd/8.5.5?topic=mpugui-creating-management-profiles-deployment-managers or via manageprofiles.sh commandline tool - https://www.ibm.com/docs/en/was-nd/8.5.5?topic=mpnzos-manageprofiles-command-1
To create cluster you will need at least one additional profile (appserver or custom) and federate it to the deployment manager.
Here are various installation secenarios (https://www.ibm.com/docs/en/was-nd/8.5.5?topic=installation-planning-install-websphere-application-server)
The simplest clustering scenario would be Scenario 7: Single-machine installation of a cell of application servers and a web server
Does Open Liberty support network deployment?
Are we able to buy IBM Support for Open Liberty? and How?
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment? e.g Having Load balancer (hardware) received request from web application and auto distribute received request to 2 or more standalone Open Liberty installed in separate VM/Machine?
Thanks
Your question is a bit vague, so I'll try my best.
Does Open Liberty support network deployment?
Depends what you mean by that support. You can install multiple Open Liberty on multiple VM/machines that will serve your applications and use LB/or IHS to route to them.
You cannot centrally manage via single console, for that you need WebSphere Liberty ND version that supports collectives.
However most recent deployments will use more 'farm' like or container orchestration approaches rather than central management via dedicated manager (as Dmgr in WAS v9).
Are we able to buy IBM Support for Open Liberty? and How?
Yes you can. See Get IBM or Red Hat support for Open Liberty page for general info and contact IBM sales representative for best option for your needs.
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment?
Depends on your application and non-functional requirements. You can setup LB or IHS with plugin (for more intelligent balancing) to route requests to multiple VM/machines with Open Liberty.
Check for example this Configuring IBM HTTP Server for Liberty and here Open Liberty Plugin Configuration. Few manual steps will be needed to edit generated config file to support many servers.
In our project we have installed both the “WebSphere application server” and “WebSphere Process Server” in a single machine. But we are unable to run both the server at a same time.
WebSphere Process Server is mounted on top of WebSphere Application Server, so while we are running the process server the default WebSphere application server instance is starting with the process server. So after that if we try to start the separately installed WebSphere application server, we are getting error that one instance is already running. Please suggest how to avoid this conflict and run both the process and application server in the single machine?
Both are using the same port. We already renamed the server name of the separately installed WebSphere application server with “server2” and Process Server’s application server name is “server1”
Please share your suggestions
You need to create separate profile. You don't have to install WAS first, or install it again, if you don't want. You may use Profile Management Tool from your installation to create new separate profile for WAS (choose Application Server profile type, not Process Server).
If you want complete separation e.g different versions (like vX of WPS and vY of WAS), or different fix pack level, you will need to do full separate WAS install.
Websphere Process Server extends Websphere Application Server (WAS), so you should install WAS first. Websphere Process Server (WPS) install should be made on top. When installation is complete you will be able to create WAS and WPS profiles on this machine. WPS profile always include WAS libraries and can be managed exactly the same way as WAS.
If you want separate servers, you should create two profiles, one for WAS and one for WPS.
You will be able to manage them separately.
I am new to WebSphere application server. I need to make minor changes on the server.
I don't know how to launch the Admin console.
Assuming that the default ports are used you can access the console from http://localhost:9060/ibm/console
I am using Weblogic Server em console to restart a webserver, URL looks like this:
http://localhost:7001/em/
AdminServer is named 'AdminServer', I wish to restart this server instance,
I click on server in EM console then user menu option like this:
(Weblogic server>Control>Shut Down...) I get this error:
'No Machine associated with server AdminServer. Please associate a machine to this weblogic server using weblogic console first.'
Not able to understand what this means....
What am i missing here?
With Oracle WebLogic, a Machine represents... well, a physical machine (and you can associate Servers i.e. WebLogic instances to it). This is not a fundamental concept except when using Node Managers. In general, you create Machine(s), Server(s) and their association with the configuration wizard at domain creation time.
It is however possible to add a Machine from the console (Environment > Machines > New):
But you can't add a RUNNING Server to a Machine with the console, which will be a problem for the admin Server. So, I'd recommend to use the configuration wizard to extend your existing domain and add Machine(s).
Note that all this will only solve the "shutdown problem", restarting will involve Node Manager which is very likely not configured.