Deploying WebLogic Platform Applications
The following checklists are provided for each step in the deployment:
The following checklist includes the items that you need to consider when planning the promotion of your application to different target environments. A plan should be prepared for each promotion stage; for example, the development, system integration, test/QA, and production environments.
Identify machines and their hardware required to host WebLogic Server instances, the database, load balancers, firewalls, and so on. |
||
Storage Area Network (SAN) or a multi-ported disk system is required for high availability in a cluster |
||
See Guidelines for Specifying the Names and Addresses of the Members in a Cluster. |
||
Ensure that the multicast address and port do not conflict with the multicast address and port of any other clusters on the network. This multicast address and port is used by cluster members to communicate within a cluster. |
||
Identify changes to the application source and configuration |
Also identify application version control requirements; for example, identifying files to maintain in a version control tool such as Perforce or CVS. |
|
Identify database access requirements with your database administrator |
||
Determine whether a packaged JDBC database driver is to be used, or whether a third party driver is required; identify XA and non-XA requirements |
||
Determine whether a hardware load balancer is to be used, or whether a third-party Web server or WebLogic Server is to be used as a proxy server |
||
Determine whether Node Manager is to be used to administer Managed Servers, and whether it is to be started as a Web service or via a script |
||
Determine whether the SDK is packaged with the WebLogic Platform installation or must be acquired separately. See WebLogic Platform 8.1 Supported Configurations at the following URL:
|
||
For example, Configuration Wizard, WLST Offline, |
||
Test plan, which specifies set of unit, stress, or other QA test requirements for each promotion stage |
||
Identify scripts to create and tools to use for promoting applications from development to production in an automated manner. See Automating the Promotion Process. |
The following checklist includes the requirements for installing the software and configuring the network in a secure manner.
Procure the hardware and software, as defined in the promotion plan. |
||
Install WebLogic Platform in a secure manner on all machines targeted for use in the domain. |
For details about installing WebLogic Platform, see Installing WebLogic Platform at the following URL:
Follow the guidance described in "Install WebLogic Server in a Secure Manner" in "Determining Your Security Needs" in Securing a Production Environment at the following URL:
|
|
Procure a cluster production license for each product installation. |
For licensing information, see Licensing at the following URL:
|
|
Ensure that multicast traffic is enabled to support clustering and that IP sockets are configured correctly. Note that some network topologies can interfere with multicast communication. For more information, see "WebLogic Server Communication in a Cluster" in "Communications in a Cluster" in Using WebLogic Server Clusters at the following URL:
|
||
Install the Web proxy plug-ins to support load balancing (Optional) |
Obtain the latest WebLogic proxy plug-ins. This step is not required if you are using WebLogic Server as a proxy or a hardware load balancer. |
The following checklist includes the requirements for creating and configuring a WebLogic domain.
Configure and target resources, including servers, clusters, machines, and JMS and JDBC resources. |
||
Add asynchronous dispatcher queues required by the application, as defined in the |
Adding Application Resources Required by the WebLogic Workshop Runtime |
|
Set the SDK, as described in Setting the SDK |
||
Set up the Managed Servers on the remote machines and configure the start attributes. |
||
If Node Manager is to be used, see Configuring Node Manager |
The following checklist includes the requirements for configuring a production database.
Create conversational state tables, as defined in the |
||
Promote WebLogic Integration application database information. |
Promoting WebLogic Integration Application Database Information |
The following checklist includes the considerations for securing the production environment.
"Firewall Considerations" in "Avoiding Problems" in "Clustering Best Practices" in Using WebLogic Server Clusters at the following URL:
|
||
A load balancer or Web proxy server distributes client connection requests, provides load balancing and failover across a WebLogic cluster, and provides security by concealing the local area network addresses from external users. For more information, see Using Load Balancers and Web Proxy Servers. |
||
"Securing Network Connections" in "Ensuring the Security of Your Production Environment" in Securing a Production Environment at the following URL:
|
||
"Securing the WebLogic Server Hosts in Securing a Production Environment at the following URL:
|
||
|
||
|
||
|
||
|
||
|
||
BEA recommends that you enable auditing in a production environment. An auditing provider stores operating requests and the results of those requests are collected, stored, and distributed for the purposes of non-repudiation. For more information about configuring auditing, see Configuring Security Providers in Managing WebLogic Security. |
||
Promoting Embedded LDAP Security Data to the Target Database |
||
The following checklist includes requirements for using load balancers and Web proxy servers.
Configure the Web proxy server or external hardware load balancer. |
||
Review considerations when configuring load balancers and Web proxy servers, such as setting up replication groups. |
Considerations When Configuring Load Balancers and Web Proxy Servers |
|
Configure load balancing and failover for servlets and JSPs, EJBs and RMIs, JMS destinations, and JDBC connections. |
For more information see "Load Balancing in a Cluster" and "Failover and Replication in a Cluster" in Using WebLogic Server Clusters at the following URLs, respectively: |
The following checklist includes the requirements for preparing the application files.
Update application project files to reference the domain in the target environment on which the application runs. |
||
Update WebLogic Portal cache configuration, behavior tracking, campaign, and commerce tax settings. |
See instructions about updating the |
|
See instructions for modifying the |
||
Tune WebLogic Workshop dispatcher and container EJBs for a production environment. |
See instructions for modifying these EJBs in Summary of Changes to Deployment Descriptors and Configuration Files. |
|
Enable session replication to maintain information about object state in the event of a server failure. |
Configure the |
|
Update host, port, and optionally security protocol of target service specified in the Web service controls. |
||
Set the concurrency strategy for stateful business process entity beans. |
Make sure that the |
|
Update the WebLogic Integration application views and adapter target event generators. |
||
The following checklist includes requirements for deploying the application.
Upload the deployment files to the Administration Server (Optional). |
"Uploading Deployment Files to the Administration Server" in "Performing Common Deployment Tasks" in Deploying WebLogic Server Applications at the following URL:
|
|
"Creating and Deploying Event Generators" in "Event Generators" in Managing WebLogic Integration Solutions at the following URL:
|