bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Platform > WebLogic Portal > Development Guide > Adding Portal to an Existing Domain |
Development Guide
|
Adding Portal to an Existing Domain
This section explains how to add portal functionality to an existing domain. These procedures and tasks are highly technical and require a good deal of familiarity with WebLogic Server and J2EE architecture.
About Your Domain
The overall procedure outlined in this section is based on the following assumptions about your existing domain:
Before You Begin
Arrive at the following decisions before moving on:
After these decisions are made, select which procedures to perform and get started.
Preserve or Replace the Existing Domain
The first decision to be made is illustrated in Figure 3-1, and concerns the domain containing your existing Web application.
Figure 3-1 Decision 1
Procedure A
Once these steps have been completed, you will have a single domain containing your existing portal Web application and a complete portal Web application.
Procedure B
Note: This partsDomain will be used as a template, but will never be started. Therefore, do not add a link to it on the Start menu.
Use or Replace Existing Database
Another decision, illustrated in Figure 3-2, concerns what database to use.
Figure 3-2 Decision 2
Procedure C
If the existing Web application can be supported by a new database, load the database objects that support the existing Web application inside the database inside the new domain.
Procedure D
To retain the database associated with the existing Web application, the following entries must be put in place:
JDBC Entries
The following JDBC entries must be added to the config.xml file from the existing domain:
Listing 3-1 Commerce Pool Datasource entry
<JDBCDataSource
JNDIName="weblogic.jdbc.pool.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="portalServer"
/>
Listing 3-2 CommercePool DataSource entries
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="portalServer"
/>
<JDBCDataSource
JNDIName="weblogic.jdbc.pool.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="portalServer"
/>
Listing 3-3 DataSync Pool entry
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.dataSyncPool"
Name="dataSyncPool"
PoolName="dataSyncPool"
Targets="portalServer"
/>
Listing 3-4 DataSync DataSource entry
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.dataSyncPool"
Name="dataSyncPool"
PoolName="dataSyncPool"
Targets="portalServer"
/>
<WebAppComponent
Name="datasync"
ServletReloadCheckSecs="300"
Targets="portalServer"
URI="datasync"
/>
Select a Realm (Optional)
Key Bootstrap (if using commerce):
Using commerce credit card functionality with the portal application requires a reference to the KeyBootstrap class, as shown in (shown in Listing 3-5):
Listing 3-5 Reference to the KeyBootstrap class
<StartupClass
ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
FailureIsFatal="false"
Name="KeyBootstrap"
Targets="portalServer"
/>
P13N Console
Listing 3-6 Personalization Console Deployment Entry
<Application
Deployed="true"
TwoPhase="true"
StagedTargets="portalServer"
Name="p13nConsoleApp"
Path="<BEA_HOME>/weblogic700/portal/lib"
>
<WebAppComponent
Name="p13nConsole"
ServletReloadCheckSecs="300"
Targets="portalServer"
URI="p13nConsole.war"
/>
</Application>
WLPDocs Services
Listing 3-7 WLPSDocs Services entries
<Application
TwoPhase="true"
StagedTargets="portalServer"
Deployed="true"
Name="wlpDocsApp"
Notes=""
Path="<BEA_HOME>/weblogic700/portal/lib"
>
<WebAppComponent
IndexDirectoryEnabled="false"
Name="wlpDocs"
Targets="portalServer"
URI="wlpDocs.war"
ServletReloadCheckSecs="300"
/>
</Application>
Tax and Payment Services (optional)
To add sample payment and tax services to the existing domain requires the entries shown in Listing 3-8. For information on adding these services to your portal application, consult "Setting Up Commerce Services" in the Administration Guide at http://download.oracle.com/docs/cd/E13218_01/wlp/docs70/admin/commerce.htm.
Listing 3-8 Tax and Payment Services entry
<Application
Deployed="true"
TwoPhase="true"
StagedTargets="portalServer"
Name="paymentWSApp"
Path="<BEA_HOME>/user_projects /myPARTSdomain/beaApps/paymentWSApp"
>
<EJBComponent
Name="payment"
URI="payment.jar"
Targets="portalServer"
/>
<WebAppComponent
Name="payment-webservice"
URI="pay-ws"
Targets="portalServer"
/>
</Application>
<Application
TwoPhase="true"
StagedTargets="portalServer"
Deployed="true"
Name="taxWSApp"
Path="<BEA_HOME>/user_projects/myPARTSdomain/beaApps/taxWSApp"
>
<EJBComponent
Name="tax"
URI="tax.jar"
Targets="portalServer"
/>
<WebAppComponent
Name="tax-webservice"
URI="tax-ws"
Targets="portalServer"
/>
</Application>
Verify Server References
Examine the config.xml file after these edits. Search and replace any reference to portalServer with the name of the server targeted by the existing domain.The config.xml file in your existing domain now has the entries required so that the WebLogic Portal server can connect to all the components that make up your J2EE enterprise Portal application. The next step is to identify the enterprise application in which these components can run on the server.
Locate or Install Enterprise Application
Within a BEA WebLogic Platform 7.0 domain, portal requires a complete J2EE application. At Decision 3, illustrated in Figure 3-3, an enterprise application is designated: Either
it is added to the existing domain by following Procedure E, or portal functionality is merged with an enterprise application already present in the existing domain, Procedure F.Figure 3-3 Decision 3
Procedure F
tools/
DataSync/
toolSupport/
bea\user_projects\portalDomain\beaApps\portalApp-project
Listing 3-9 Listings for
weblogic-application.xml<module>
<web>
<web-uri>tools</web-uri>
<context-root>portalAppTools</context-root>
</web>
</module>
<module>
<web>
<web-uri>datasync</web-uri>
<context-root>portalAppDataSync</context-root>
</web>
</module>
<module>
<web>
<web-uri>toolSupport</web-uri>
<context-root>portalAppTool</context-root>
</web>
</module>
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |