To Deploy the EAR File to the Production Server

See step 8 below.

Open the WebLogic Server console for the target server running in production mode.

• On the left-hand side Change Center pane, click Lock & Edit.
• On the left-hand side Domain Structure pane, click Deployments.
• On the right-hand content pane, click Install.Browse to the directory where the EAR file resides, mark the radio button next to the EAR file you want to deploy, and click Next.
• Confirm that the radio button next to Install this deployment as an application is marked and click Next.
• Click Finish.
• On the left-hand side Change Center pane, click Activate Changes.
• On the right-hand content pane, mark the radio button next to the EAR just deployed.
• Click Start to view the dropdown list and select Servicing all requests.
• In the content pane of the new page, click Yes.

The main steps for creating a JDBC store are as follows:

• uk.co.certification.simulator.questionpool.PList@5bf1e4b0

* For JMS servers, select the JDBC store (C) on the General Configuration page.

* For Store-and-Forward agents, select the JDBC store on the General Configuration page.

Note: The WebLogic Persistent Store provides a built-in, high-performance storage solution for all subsystems and services that require persistence. For example, it can store persistent JMS messages or temporarily store messages sent using the Store-and-Forward feature. Each WebLogic Server instance in a domain has a default persistent store that requires no configuration and which can be simultaneously used by subsystems that prefer to use the system's default storage. However, you can also configure a dedicated file-based store or JDBC database-accessible store to suit your JMS implementation.

A: To create a deployment plan for a deployed application that does not already have a deployment plan, make a configuration change to the deployed application. When you make a persisted configuration change to a deployed application that does not have an existing deployment plan, the Administration Console automatically creates a deployment plan for you and prompts you for the location in which to save it.

B: The weblogic.PlanGenerator is a Java-based deployment configuration tool. It is primarily intended for developers who want to export portions of a WebLogic Server deployment configuration into an XML deployment plan. weblogic.PlanGenerator also enables you to generate a basic WebLogic Server configuration for applications that have only J2EE deployment descriptors.

D: Deployment plans can be created or edited through the deployment plan editor functionality available through the Web-based Oracle Enterprise Manager 10g Application Server Control Console interface and the J2EE and Studio Editions of the Oracle JDeveloper 10g integrated development environment.