Production Operations User Guide Preparing and Deploying the EAR File This chapter discusses the steps for preparing your application's Enterprise archive (EAR) file to be deployed. Note: WebLogic Portal only supports deployment to a clustered or stand-alone server configuration. Deployment of a WebLogic Portal application to a non-clustered managed server is not supported. This chapter includes the following topics: • • • • Preparing the EAR File for Deployment To bring your portal online in a production environment, it is first necessary to prepare your portal application. Mortal Kombat Deception Game Shark Codes. Typical preparation steps include modifying deployment descriptors for the product, building the Enterprise archive (EAR) with all its pre-compiled classes, and deciding if you want to compress that EAR into an archive or leave it exploded. Configuring Portal Application Deployment Descriptors Similar to any J2EE application, a portal application has a number of deployment descriptors that you may want to tune for your production environment.

After you have configured security settings, you can deploy the packaged Decision Center EAR file on WebLogic Server. To deploy the EAR file: In the WebLogic Server Administration Console, at the bottom of the Home Page, click Deployments. In the Summary of Deployments page, under Deployments, click Install. In the Install Application Assistant, click the upload your file(s) link. Click Browse next to Deployment Archive, upload one of the following files, and click Next. Applications will generally deploy the EAR. From an EAR file I. Set up a Standalone WebLogic Server. Deploying Applications to WebLogic.

Modifying Application Deployment Descriptors Within the Portal application is the /META-INF directory that contains a number of deployment descriptors, including application-config.xml, a portal-specific deployment descriptor that contains cache configuration, behavior tracking, campaign, and commerce tax settings. If these values are different for your production environment than for your existing development settings, modify this file appropriately before building the portal application. Modifying Web Application Deployment Descriptors Within any portal web application is a /WEB-INF directory that contains a number of deployment descriptors you may need to modify for your production environment. • web.xml is a J2EE standard deployment descriptor. Among other settings, it has a set of elements for configuring security for the web application. For more details about web.xml see.

Note: If you are running your portal application on a managed server, you can improve the performance of the WebLogic Administration Portal by adding the following parameter to the web.xml file: portalFileDirectory / This parameter takes advantage of an optimized call to an mbean that returns EAR content information. Without this parameter, the mbean call recursively searches for.portal files. Ripe Program Committee more. To avoid the overhead of this recursive call, you can place all of your.portal files in one directory and specify the directory with the portalFileDirectory parameter. In the example above, all.portal files reside in the web application's root directory ( /). If you use this parameter, you must place all of the.portal files in the same directory under the portal web application. Use the to specify the directory. Driver Modem Telkomsel Flash. • weblogic.xml is a standard WebLogic Server deployment descriptor for web applications that has a number of important descriptor entries.