Wsrp portlets can't be deployed 11g
WLS_Portal, they need to be deployed to WLS_WSRP server. Below are the steps to create a new WLS_WSRP server through 11g Portal admin console:
1. Create a WSRP Managed Server.
a. Log on to the Oracle WebLogic Server Administration Console.
b. Click Lock & Edit.
c. In the Domain Structure tree, expand Environment and then select Servers.
d. Click New.
e. In the Create a New Server page enter the following information:
- Server Name: Enter the name of the server. For example: WLS_WSRP
- Server Listen Port: Enter the port number from which you want
to access the server instance. For example: 9003
- Select the No, this is a stand-alone server radio button.
f. Click Finish.
g. Click "Activate Changes".
1. Create a WSRP Managed Server.
a. Log on to the Oracle WebLogic Server Administration Console.
b. Click Lock & Edit.
c. In the Domain Structure tree, expand Environment and then select Servers.
d. Click New.
e. In the Create a New Server page enter the following information:
- Server Name: Enter the name of the server. For example: WLS_WSRP
- Server Listen Port: Enter the port number from which you want
to access the server instance. For example: 9003
- Select the No, this is a stand-alone server radio button.
f. Click Finish.
g. Click "Activate Changes".
2. Associate a machine to the new WSRP Managed Server.
a. Still connected to the Oracle WebLogic Server Administration Console,
in the Domain Structure tree, expand Environment and then select Servers.
b. In the Summary of Servers page, click on the Server (WLS_WSRP) you have created.
c. Click Lock & Edit.
d. Select your machine name from the Machine drop-down list.
e. Click Save.
f. Click "Activate Changes".
a. Still connected to the Oracle WebLogic Server Administration Console,
in the Domain Structure tree, expand Environment and then select Servers.
b. In the Summary of Servers page, click on the Server (WLS_WSRP) you have created.
c. Click Lock & Edit.
d. Select your machine name from the Machine drop-down list.
e. Click Save.
f. Click "Activate Changes".
3. Deploy the required libraries to the new WSRP Managed
Server.
a. Still connected to the Oracle WebLogic Server Administration Console,
in the Domain Structure tree, select Deployments.
This should show the "Summary of Deployments" page.
b. In the Deployment table click Customize this table and do the following:
- Uncheck the "Exclude libraries when displaying deployments" option.
- Number of rows displayed per page: 100
- Click Apply.
c. In the Deployment table repeat the following steps to add the following Libraries:
oracle.portlet-producer.wsrp(11.1.1,11.1.1)
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
DMS Application(11.1.1.1.0)
oracle.jsp.next(11.1.1,11.1.1)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
wsil-wls
oracle.jrf.system.filter
To each library do the following:
- In the Deployment table click the name of the desired library.
This should bring the Library settings page.
- Click the Targets tab.
- Click Lock & Edit.
- Check AdminServer and WLS_WSRP from the Servers section.
For updating "wsil-wls" you need to select "wsil-wls" and then click on "Change Targets".
- Click Save.
- Click "Activate Changes".
4. Start the new WSRP Managed Server.
a. In the Domain Structure tree, expand Environment and then select Servers.
The "Summary of Servers" page should be displayed.
b. Click the Control tab, and select the new wsrp server (WLS_WSRP).
c. Click Start.
The "Server Life Cycle Assistant" page should be displayed.
NOTE: You need to start the nodemanager for this to work.
d. Click Yes to start the server.
a. Still connected to the Oracle WebLogic Server Administration Console,
in the Domain Structure tree, select Deployments.
This should show the "Summary of Deployments" page.
b. In the Deployment table click Customize this table and do the following:
- Uncheck the "Exclude libraries when displaying deployments" option.
- Number of rows displayed per page: 100
- Click Apply.
c. In the Deployment table repeat the following steps to add the following Libraries:
oracle.portlet-producer.wsrp(11.1.1,11.1.1)
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
DMS Application(11.1.1.1.0)
oracle.jsp.next(11.1.1,11.1.1)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
wsil-wls
oracle.jrf.system.filter
To each library do the following:
- In the Deployment table click the name of the desired library.
This should bring the Library settings page.
- Click the Targets tab.
- Click Lock & Edit.
- Check AdminServer and WLS_WSRP from the Servers section.
For updating "wsil-wls" you need to select "wsil-wls" and then click on "Change Targets".
- Click Save.
- Click "Activate Changes".
4. Start the new WSRP Managed Server.
a. In the Domain Structure tree, expand Environment and then select Servers.
The "Summary of Servers" page should be displayed.
b. Click the Control tab, and select the new wsrp server (WLS_WSRP).
c. Click Start.
The "Server Life Cycle Assistant" page should be displayed.
NOTE: You need to start the nodemanager for this to work.
d. Click Yes to start the server.
5. Configure the Datasource for the new WSRP Managed Server.
To map the portletPrefs datasource targets to the managed server (WLS_WSRP), do the following:
Note that this step can be omitted if file based Pref storage is used rather than database based.
a. In the Domain Structure tree, expand Services,
then select and expand JDBC and click Data Sources.
You should see the "Summary of JDBC Data Sources" page.
b. Click the "PortletDS" link associated with the jdbc/portletPrefs JNDI.
c. Click the Targets tab.
d. Click Lock & Edit.
e. Check WLS_WSRP from the Servers section.
f. Click Save.
g. Click Activate Changes.
To map the portletPrefs datasource targets to the managed server (WLS_WSRP), do the following:
Note that this step can be omitted if file based Pref storage is used rather than database based.
a. In the Domain Structure tree, expand Services,
then select and expand JDBC and click Data Sources.
You should see the "Summary of JDBC Data Sources" page.
b. Click the "PortletDS" link associated with the jdbc/portletPrefs JNDI.
c. Click the Targets tab.
d. Click Lock & Edit.
e. Check WLS_WSRP from the Servers section.
f. Click Save.
g. Click Activate Changes.
6. Extend the Existing WebLogic Domain with the Oracle WSM
Policy Manager.
a. Shutdown all the servers in the Portal domain including the Admin Server.
b. Connect to the Server where Portal is installed.
c. Change to the following directory:
$ORACLE_PORTAL_HOME/common/bin
d. Run the config.sh script.
e. On the "Welcome" screen select:
"Extend an existing WebLogic Domain" and click Next.
f. On the "Select a WebLogic Domain Directory" screen, select your
valid Portal domain directory and click Next.
This is the Portal domain where you created the WLS_WSRP server.
g. On the "Select Extension Source" screen, select:
"Oracle WSM Policy Manager - 11.1.1.0 [Your portal Home]" and click Next.
Note that step g to k can be omitted if wsm Policy Manager is not needed.
h. On the "Configure JDBC DataSource" click Next.
i. On the "test JDBC Data Sources" screen click Next.
j. On the "Configure JDBC Component Schema" screen, check the OWSM MDS Schema.
Then provide the information to your MDS schema. This is the schema created for MDS
when you run the repository Configuration Utility (RCU) at install time. If you did not created
this schema already then you need to create this schema first using RCU.
For example:
Schema Owner: PROD_MDS
Schema Password: <mds_password>
DBMS/Service: orcl.us.oracle.com
Host Name: //databaseserver.domain
Port: 1521
Click Next.
k. In the "Test Component Schema" screen, confirm the test is successful and click Next.
l. In the "Select Optional Configuration" screen, select Deployment and Services and click Next.
m. In the "Target Deployments to Clusters or Servers" screen, ensure
wsp-pm is targeted to servers including WLS_WSRP and AdminServer.
Click Next.
n. In the "Target Services to Cluster or Servers" screen, click Next.
o. Review your settings in the "Configuration Summary" screen, and click Extend.
p. Click "Done" when finish.
q. Start the servers in the Portal domain including the Admin Server, WLS_PORTAL and WLS_WSRP.
a. Shutdown all the servers in the Portal domain including the Admin Server.
b. Connect to the Server where Portal is installed.
c. Change to the following directory:
$ORACLE_PORTAL_HOME/common/bin
d. Run the config.sh script.
e. On the "Welcome" screen select:
"Extend an existing WebLogic Domain" and click Next.
f. On the "Select a WebLogic Domain Directory" screen, select your
valid Portal domain directory and click Next.
This is the Portal domain where you created the WLS_WSRP server.
g. On the "Select Extension Source" screen, select:
"Oracle WSM Policy Manager - 11.1.1.0 [Your portal Home]" and click Next.
Note that step g to k can be omitted if wsm Policy Manager is not needed.
h. On the "Configure JDBC DataSource" click Next.
i. On the "test JDBC Data Sources" screen click Next.
j. On the "Configure JDBC Component Schema" screen, check the OWSM MDS Schema.
Then provide the information to your MDS schema. This is the schema created for MDS
when you run the repository Configuration Utility (RCU) at install time. If you did not created
this schema already then you need to create this schema first using RCU.
For example:
Schema Owner: PROD_MDS
Schema Password: <mds_password>
DBMS/Service: orcl.us.oracle.com
Host Name: //databaseserver.domain
Port: 1521
Click Next.
k. In the "Test Component Schema" screen, confirm the test is successful and click Next.
l. In the "Select Optional Configuration" screen, select Deployment and Services and click Next.
m. In the "Target Deployments to Clusters or Servers" screen, ensure
wsp-pm is targeted to servers including WLS_WSRP and AdminServer.
Click Next.
n. In the "Target Services to Cluster or Servers" screen, click Next.
o. Review your settings in the "Configuration Summary" screen, and click Extend.
p. Click "Done" when finish.
q. Start the servers in the Portal domain including the Admin Server, WLS_PORTAL and WLS_WSRP.
7. Log on to the Oracle WebLogic Server Administration
Console.
a. In the Domain Structure tree, select Deployments.
This should show the "Summary of Deployments" page.
b. In the Deployment table click wsm-pm.
This should bring the settings page.
c. Click the Targets tab.
d. Click Lock & Edit.
e. Select "wsm-pm" and then click on "Change Targets".
e. Check AdminServer and WLS_WSRP from the Servers section.
f. Click Save.
g. Click "Activate Changes".
a. In the Domain Structure tree, select Deployments.
This should show the "Summary of Deployments" page.
b. In the Deployment table click wsm-pm.
This should bring the settings page.
c. Click the Targets tab.
d. Click Lock & Edit.
e. Select "wsm-pm" and then click on "Change Targets".
e. Check AdminServer and WLS_WSRP from the Servers section.
f. Click Save.
g. Click "Activate Changes".
8. Deploy your provider EAR File.
