I am trying to setup a weblogic cluster running ATG Commerce. I have installed weblogic on machine A, with the following configuration.
Weblogic admin server
Managed servers: Production_A, Production_B, Publishing_A and Publishing_B that
shall run on machine A and B accordingly.
Do I have to install weblogic on machine B also?
(While installation of ATG commerce it ask which is our application server. I mean to say the production and publishing server shall run inside the weblogic server of machine A).
Secondly, do I have to actually specify the managed servers in weblogic while installing it on machine A. I mean to say while installing ATG commerce in machine B, during CIM configuration, I specify the weblogic of machine A, and I create production_B and publishing_B to run inside A's weblogic.
I am confused wheater I'm doing it right.
The managed servers production_B and publishing_B appear in A's weblogic After I do CIM configuration on B. The I set up machines(A and B in A's weblogic), add servers to machines, Add servers to cluster. Everything is happening. But when I try to run B's servers from A's weblogic, the servers do not start saying nodemanager is unreachable. In machine A, I have set the node manager for machine B to Machine A(I need to ask like will the node manager for machine B's server? Or it will run in A's weblogic node manager(production_A and Publishing_A runs with this node manager)) machine A is reachable from machine B(I can open weblogic console of Machine A on Machine B). Am I missing on anything?
Can Anyone direct me to a reference/blog for weblogic clustering in ATG Commerce
Firstly, you will need to install WebLogic on every physical machine on which you intend to deploy your EAR. It is the servlet container that you'll be using so without it (and it's obvious dependencies like JAVA) you won't be able to run your deployments on that machine.
As far as your ATG instances are concerned, I would do it as follow:
Create Commerce A and Publishing A on Server A (using CIM). Something that you are missing though is you have no LockManager configured. You'll require at least one of these to maintain your locks across your Commerce Instances and possibly another to do the same across your publishing instances (I've never deployed a clustered publishing environment, only ever one BCC per environment).
Having done the configuration on Server A, manually copy the ATG-Data/servers folder (or /servers) folder from Server A to Server B. Because you don't install ATG on every machine, in fact you don't need ATG to be deployed if you create your EAR in standalone mode, I would recommend you setup an ATG-Data folder on both Server A and Server B and deploy your configs in there.
Now, having copied the servers folder you will need to manually edit the following files:
Configuration.properties
This probably contains references to Server A that you want to update.
The Ports on Server B can be the same (per instance) as it is on Server A
Update the otherLockServer property in the LockManager instance (if you created it) for both Server A and Server B to reference the 'other lock server'
Update the ClientLockManager to point at both LockManagers
From a WebLogic point of view you need to create the servers on each instance as well. Even within a WebLogic Cluster (which is licensed separately with Oracle and not included in your ATG License) you need an AdminServer per WebLogic. I believe the NodeManager configuration would be different but I've not set this up in a WebLogic cluster, yet.
Related
I've created multiple managed servers in Weblogic. Each managed server has same IP(IP of weblogic server) and unique port.
I've installed ear and war files in these managed servers and all of them has their own context-root.
For example I have ear file A with context-root A on server A and a war file B with context-root B on server B.
Whenever I browse IP:PORT(A) which has set on server A, this application needs some files on war file B which has deployed in server B. So A can not find its resources and I get error.
I should mention that I put them in a cluster too but nothing changed.
How can handle this matter?
The cluster won't help you in this way because each web app is isolated from others in its own web container. If you need to share data or resources between web apps you can use a shared file system or a database for instance.
For this purpose I've used Oracle Http Server (OHS) plugin. after hours of searching in internet I've found that Weblogic application server does not implement anything to handle this issue.
https://docs.oracle.com/middleware/1213/webtier/
I want to create a weblogic cluster that has two managed servers each running on a physically separated remote machine
According to weblogic docs
All Managed Servers in a cluster must reside in the same domain; you
cannot split a cluster over multiple domains.
Ref: https://docs.oracle.com/cd/E24329_01/web.1211/e24970/understand_domains.htm#DOMCF125
If this is the case then where am I suppose to create the Managed Server on the remote machine. Since the managed server can only be created in the domain, am I not suppose to create the domain on the remote machine for holding managed server?
[edit]
As per the below documentation
https://docs.oracle.com/cd/E17904_01/web.1111/e14144/tasks.htm#WLDPU136
It seems that the admin server domain is replicated on remote managed servers using pack and unpack commands.
That means a separate copy of domain must be made available on remote machines in order to operate managed servers on it.
Is it the fault with the oracle documentation-
Because then its the violation of the Domain Restrictions rule which says that there should be only one domain per cluster?
Domain is logical group for all Weblogic resources like relam, cluster, manged servers. You can create managed servers on physically separated remote machine and group them in a same Weblogic domain.
In a WebLogic Server domain there is always one administration server. This special instance of WebLogic Server is responsible for the configuration of the entire domain. Other servers in the domain are called managed servers. These are typically the servers on which you run your applications. A domain can contain any number of managed servers. You can find the detail on this link -
https://docs.oracle.com/cd/E17904_01/web.1111/e14144/tasks.htm#WLDPU136
I have configured web application on server1. In configuration I choosed my cluster(server1 and server2) as target servers. What I want to learn is Do also need to configure a deployment on server2? There is no war file in server2 and I am a little curious about how this application will run also on server2.
Deployments process can be done in three ways...
1.Stage
2.Nostage
3.ExtenalStage
This is an explanation of the staging modes in WebLogic:
Stage mode—
The Administration Server copies the archive files from their source location to a location on each of the targeted Managed Servers that deploy the archive. For example, if you deploy a J2EE Application to three servers in a cluster, the Administration Server copies the application archive files to each of the three servers. Each server then deploys the J2EE Application using its local copy of the archive files.
Stage mode is the default mode when deploying to more than one WebLogic Server instance.
Nostage mode—
The Administration Server does not copy the archive files from their source location. Instead, each targeted server must access the archive files from a single source directory for deployment. For example, if you deploy a J2EE Application to three servers in a cluster, each server must be able to access the same application archive files (from a shared or network-mounted directory) to deploy the application.
Nostage mode is the default mode when deploying only to the Administration Server (for example, in a single-server domain). You can also select nostage mode if you run a cluster of server instances on the same machine.
External_stage mode—
External_stage mode is similar to stage mode, in that the deployment files must reside locally to each targeted server. However, the Administration Server does not automatically copy the deployment files to targeted servers in external_stage mode; instead, you must manually copy the files, or use a third-party application to copy the files for you.
Hope it helps you.
No, weblogic will handle deployment to both managed servers automatically.
i have 2 machines on which same version of glassfish is installed say A and B. they are nix based. on both the machines glassfish is hosting same applications. glasfish B is facing some issue which we are not able to sort. glassfish A and applications on it are working perfectly. can i take a backup-domain on glassfish A and restore it on glassfish B. ? in other words do domain configuration contains machine specific information or anything that might make this thing not possible ?
Yes. You should be able to do that. We went to lengths to make the configuration not machine-specific.
I recommend that you first backup GF "B" just to be safe.
If you have GF server instances (not domain) running on another machine, they have a config file that points back to the domain's host. You would need to edit that file if the domain host changed.
We are running Weblogic 7sp6. We have a working single node cluster with an Admin and two Managed servers. We are re-creating a 2nd standalone cluster on a 2nd server. We reinstalled Weblogic and have copied over all the configuration files to make thing. Its the same on both clusters. We changed all the references to IP and hostnames. We have used this method before without problems.
In the current case I can startup the Admin which listens on port 7001,7002. But when I try and startup either of the Managed servers it tells me that myserver1/2 is already up. (Managed Servers). I confirmed that myserver is configured to use port 7012,7013 and I cannot find any port conflicts especially because these exact ports worked on the first cluster. Any ideas of what else to look at? I have logged in the admin console and can see the ports are all unique. Thanks
The current version of WebLogic is 10.3. I'd strongly urge you to upgrade your WebLogic as soon as possible, especially if you're still using the version of JDK that it was certified for. If you're running JDK 1.4, you're crazy.