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.
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 am trying to setup CI pipeline for .net core app with VSTS.
I am confused with Copy Files Over SSH step. Server is defined not by deployment group but by endpoint host.
How should I copy my deployment artifacts to ALL servers in deployment group with this tool?
Actually, same applies to "SSH" - it also get executed only on host from Endpoint definition.
Any ideas?
If you're using deployment groups, you don't need to SSH anything to them. The build artifacts will be automatically downloaded to them, since the build/release agent is already running on them and talking directly to VSTS.
I have deployed my application running on my local server # http://localhost:8048/myservice?day=xx&month=yy&year=zzzz , it works succesfully on my local machine, in that it downloads a file from the http site. However when I deploy to Mule Management console . I understand that the default port is 8585. When I change the URL to MMC & give the default port with the same path, it does not download the file . Am I missingsomething
The MMC is a utility for managing and monitoring Mule Standalone Runtimes.
One of its functions is to deploy apps to a Runtime. You are not actually deploying to the MMC.
Does this help clarify the situation or do you want any further help on want The MMC is used for and how to do it?
Please check the logs inside MMC.It stores the logfiles date wise.See if your application has been deployed in MMC successfully and if yes then do the following things:
1)If you are using any path to download the file then cross check the path details.You can put a logger to crosscheck that.
2)Put a logger before the business logic and after the business logic and follow what it is logging in the log file.
3)In case your server is Linux then check the path separator pattern
MMC is a Mule Management Console which is used (provides provision) to deploy, undeploy, manage, monitor application and server both. From the statement you mentioned in your query it seems you are trying to deploy the app in the MMC - MMC is not a server its a console where you can register your ESB Runtimes -or- API Gateways (on-Prem) servers so that you can deploy the applications to the server/runtimes (which will go to the runtimes location $MULE_HOME/apps).
Please check if you have registered the server under MMC's Server tab - if not then you have to do this first and then it will allow you to perform application deployment using the MMC's APplication tab where you can upload your deployment archive/artifacts/build to the mmc repo and then you can deploy through the deployment options by selecting your server (which you have registered).
If I am missing something from your statement then please clarify more and will try to help you out here.
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.
Multiple TFS 2010 MSBuilds are not triggering Web Deploy to publish the web application to the IIS website.
This is for multiple different software products, multiple different build configurations, 2 different build agents (on 2 different servers), multiple IIS web site instances on multiple different servers.
3 different continuous deployment setups were previously working.
So hopefully this rules out miss-configuration of the build/build servers/hosting servers/web deploy and IIS.
According to the network manager nothing has changed on the network (all servers are local), and port 8172 is not blocked by any security configurations.
All builds succeed, web deploy fails silently (no error, nothing in the logs). It appears that web deploy is no longer being triggered.
Are there any other ports that are used here?
What else could be blocking the communication between MSBuild and Web Deploy?
Would you expect it to fail silently (nothing in the logs or passed back to MSBuild)?
UPDATE
This is a similar question How to determine if MSBUILD Arguments were executed for TFS Build Definition
Assuming you are using vs2012, on your build server make sure the following two folders exist: Web & WebApplications in
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0
If these dont exist then need to be copied from a machine your do development on. This worked for me, and solved all of my problems with the Deployment of projects.