Active Oldest Votes. Improve this answer. Rafa Arana Rafa Arana 44 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Who owns this outage? Building intelligent escalation chains for modern SRE.
Podcast Who is building clouds for the independent developer? The following are sample deployment commands:. Import coherence. As an alternative to using the manifest file, copy coherence. Example illustrates the contents of a sample manifest. Optional If you want to configure Coherence cluster properties, create a CoherenceClusterSystemResourceMBean and reference it as a coherence-cluster-ref element in weblogic.
Example illustrates a sample configuration for WAR-scoped clusters in the weblogic. For this enterprise deployment topology, you must install and deploy the dizzyworld. To do so, compete the following steps:. Extract the dizzyworld. Open the weblogic-application. Specify the path, where your dizzyworld. Select Install this deployment as an application and click Next. Figure Select Deployment Targets. Target the application to the administration server and the cluster. Once deployment has completed, start the managed servers however you like, such as in parallel simultaneously.
Perform the previous deployment steps except the last step. When you start the managed servers, start a single managed server first. After this managed server has started, you can start the remaining managed servers in parallel. Administration server and cluster up and running whether or not commerce is being used. Target the application to the administration server only.
On the Targets tab, target the administration server and the cluster, and click Apply. On the Deploy tab, redeploy the application. Most components must be targeted to the administration server as well as the cluster. Here are the following exceptions:. This full level of deployment on the administration server and the cluster is required, and it is the only supported configuration. There are several application design challenges specific to clustering that WebLogic Portal solves to ensure that portal applications perform properly and optimally in a cluster environment.
The full targeting scheme described is part of the solution to those design challenges. If you want to reduce the number of modules deployed on the administration server and the cluster, click Target Each Module in the deployment steps and untarget AppName Admin from the administration server and AppName Datasync from the cluster. While you need to deploy your portal application to the administration server, the administration server is not typically used to serve pages for portal applications.
In the previous steps, you targeted the entire application for deployment rather than targeting individual modules to the administration server and to the cluster. This is the recommended deployment approach. Since almost all modules must be deployed to both the administration server and to the cluster, any performance or disk space benefits you want to achieve by targeting individual modules is not significant. However, if for some reason you want to use targeted deployment, use the following recommendations, which are listed in order from easiest to most difficult.
The sequence with which you start managed servers is important and depends upon your application deployment. See Table for the startup sequences you must use. If you are not deploying a new application or an updated application , you can start all managed servers in parallel simultaneously. There are numerous ways to start a managed server and bind it to your administration server, including using Node Manager.
For your initial setup, you may want to use the startManagedWebLogic script in the domain root directory. You can run this script by specifying the name of the managed server for this server instance and the URL of the administration server.
Before starting the script, edit it and give the managed server more memory than it is allocated by default. For example, change the memory allocation to -Xmsm -Xmxm.
After starting a managed server, you can browse your portal application by going to the appropriate URL on the managed server instance. To provide your users a single point of entry to your cluster, as well as support session failover, you will need to configure a proxy server. There are no WebLogic Portal-specific configuration tasks when setting up a proxy plug-in. This is because the variables for those values are read from the request.
The same could happen if a user on a proxy server port 80 clicks a link to a resource outside the proxy server port This section contains instructions for redeployment, partial redeployment, and iterative deployment of datasync data, such as user profile properties, user segments, content selectors, campaigns, discounts, and other property sets. Deployer tool to redeploy an updated portal application to your production server. See weblogic.
Deployer Utility. The following batch file shown in Listing is an example of how to use weblogic. Deployer to redeploy a portal application to production. In certain situations you can reduce the time needed to redeploy individual pieces of a portal application by using the weblogic.
Deployer tool. If your updates are contained within a particular portal web application, you can redeploy just that web application and greatly reduce the time spent in redeployment. This is of use if you have new portlets and page flows, but no new EJBs, libraries, or modules which are Enterprise application scoped.
0コメント