Monday, February 27, 2012

How to run 32bit RCU on 64bit Linux in graphical mode?

RCU is available only on 32-bit x86 Linux and 32-bit Microsoft Windows operating system platforms. For Release 11.1.1.4.0 and later, RCU can also be run on 64-bit x86 Linux and 64-bit Microsoft Windows operating systems. 

If you run the RCU in graphical mode using x11 client from the 64-bit x86 Linux, you will get following error:-
Exception in thread "Main Thread" java.lang.InternalError: Can't connect to X11 window server using 'localhost:10.0' as the value of the DISPLAY variable.
        at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
        at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
        at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
        at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:169)
        at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
        at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:89)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:169)
        at java.awt.Toolkit$2.run(Toolkit.java:834)
        at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:826)
        at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:484)
        at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249)
        at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135)
        at oracle.sysman.assistants.rcu.ui.InteractiveRCUModel.<init>(InteractiveRCUModel.java:117)
        at oracle.sysman.assistants.rcu.Rcu.execute(Rcu.java:292)
        at oracle.sysman.assistants.rcu.Rcu.main(Rcu.java:344)

Solution

1.       Go to $RCU/bin and change the permission of rcu.sh file using chmod 755 rcu
2.       Edit the rcu.sh using nano rcu
3.       Change the 32bit JRE path to with 64bit JRE path
JRE_DIR=export JAVA_HOME=/apps/oracle/java/jrockit-jdk1.6.0_26/ jre

Now, run the rcu again.

Wednesday, January 4, 2012

Hiden Gem of Oracle WebCenter: Spaces Automatic Services Configuration

Spaces supports automatic configuration of certain Oracle WebCenter Portal services.  Mean, you don’t need to set discussion, portlet, UCM services etc from the EM manually. This feature is available from 11G PS3 onward.
The Automatic Service Configuration only worked if the following conditions are met:
  • Spaces and the target component must be installed in the same domain.
  • The managed server of the target component must have an explicit listening address. If its listening address is empty or null or "localhost", then it must have a system associated to it that has an explicit address.
  • The target component (like discussions, ucm, pagelet etc) must not be deployed to a cluster.
  • You must start the managed servers associated to the WebCenter Portal services first. Then, start the WC_Spaces managed server.

Currently, automatic Service Configuration is implemented for the following Services:
Component/Service
Default Connection Name
Specific Rule
Discussions and Announcements services
WebCenterSpaces-Discussions
The user granted the Administrative role exists in discussions.

Documents service
WebCenterSpaces-ucm

Pagelet producer
WebCenterSpaces-PageletProducer

Personalization service
Conductor-WCPSSpaces
 and
Properties-WCPSSpaces

Preconfigured portlet producers
wc- OmniPortlet

wc-WebClipping

wc-WSRPTools

Worklist service and Spaces workflows
WebCenterSpaces- Worklist



Every time you start Spaces it will try to create the connections unless they already exist. This will be true until the service is configured for the first time unless you disable automatic service configuration. If the automatic configuration fails for a specific component, then you will have to manually configure the service.
You can verify from the EM that service connections are automatically configured for the Spaces application when you start the managed servers.
If required, you can disable the auto-configuration feature by setting the following Java property in domain_home/bin/setDomainEnv.sh  (on UNIX) or domain_home\bin\setDomainEnv.cmd (on Windows). 
-Dwebcenter.spaces.disableAutoConfigure=true

Reference:

Oracle® Fusion Middleware Installation Guide for Oracle WebCenter Portal 11g Release 1 (11.1.1.6.0)

4.2 Working with Oracle WebCenter Portal: Spaces

http://docs.oracle.com/cd/E23943_01/install.1111/e12001/wc_components.htm#CHDGEJFG

Monday, December 19, 2011

Why Web Server for WebCenter? Oracle HTTP Server (OHS) vs Apache HTTP Server? How to configure Apache HTTP Server as a Web server for WebCenter?


Why Web Server for WebCenter?
To configure any HTTP Server for WebCenter is important in following scenarios:-
a.      For a good integration between WebCenter and UCM
b.   To configure SS0
c.       Access UCM few functionalists like Document Manager, document rendition support, advanced metadata edit, the IFRAME functionality, and so on.

Oracle HTTP Server (OHS) vs Apache HTTP Server
You can also use Oracle Web Tier that also has HTTP Server (OHS) instead of Apache HTTP Server. The advantage of using Apache HTTP Server is easy to download due to small size, easy to install and its light weight. The advantage of using OHS is that it’s also based on Apache HTTP Server, already configured for Weblogic Server.

Configure Apache HTTP Server as a Web server for WebCenter
Assuming that WebCenter and UCM is installed and configured. Start the Admin Server and other manage servers. You can access Weblogic Console with the URL http://localhost:7001/console, WebCenter Spaces with http://localhost:8888/webcenter and UCM with http://localhost:16200/cs.

1.      Download the Apache HTTP Server at http://httpd.apache.org/download.cgi#apache22 according to your OS
2.      Install the Apache HTTP Server 2.2.x
3.      Start the Apache HTTP Server and access the Apache HTTP Server using http://localhost. If you see message that “It Works!”, its mean its installed successfully
4.      Copy the mod_wl_22.so from $WL_HOME\wlserver_10.3\server\plugin\win\32\mod_wl_22.so to APACHE_HOME\modules
5.      Open the httpd.conf file at APACHE_HOME\conf
6.      By default, Apache HTTP Server listen on port 80, you can change the port using Listen property like Listen 7777. We will use default port.
7.      Add the following line in
httpd.conf LoadModule weblogic_module   modules/mod_wl_22.so
8.      Add the following request to proxy

<Location /console>
 SetHandler weblogic-handler
 WebLogicHost localhost
 WebLogicPort 7001
</Location>

#Spaces
<Location /webcenter>
WeblogicHost localhost
WebLogicPort 8888
SetHandler weblogic-handler
</Location>

<Location /webcenterhelp>
WeblogicHost localhost
WebLogicPort 8888
SetHandler weblogic-handler
</Location>

# Discussions
<Location /owc_discussions>
    WebLogicHost localhost
        WebLogicPort 8890
    SetHandler weblogic-handler
</Location>

#UCM
<Location /cs>
WeblogicHost localhost
WebLogicPort 16200
SetHandler weblogic-handler
</Location>

<Location /adfAuthentication>
WeblogicHost localhost
WebLogicPort 16200
SetHandler weblogic-handler
</Location>

9.      Start the Apache HTTP server
10.  Open the browser and test the following URLs:
http://localhost/webcenter
http://localhost/cs 

 You will see that its working now without any Admin Server port.

Friday, October 28, 2011

Start WebLogic’s Managed Server without Username and Password manually

After you installed Fusion Middleware products like WebCenter, UCM, SOA etc you have plenty of Managed Servers (MS) and you have to enter username and password when you start each Managed Server (WC_Spaces, UCM_server1, IBR_server1, WC_Portlet, WC_Utilities, BAM_server1 etc) from the command line.  To make it automatic so that you don’t need to enter username and password. Follow the following steps:-

Apply to all the managed servers (Unsecured and simple way)

If you want that all my Managed Servers (MS) will not prompt for username and password then this approach is for you. In this approach, you just need to change one file and all the MSs will not prompt you for username and password without doing any change in individual MS. Follow the following instructions:-
1.       Go to bin of weblogic domain. In my case, following is the domain path:- <Middleware-Home>\user_projects\domains\<doman>\bin i.e. C:\Oracle\Middleware\user_projects\domains\wc_domain\bin
2.       Open the startManagedWebLogic.cmd in any text editor
3.       Set the following two variables with your weblogic admin user and its password
Set WLS_USER=<Admin-User-Name>
Set WLS_PW=<Admin-User-Password>
4.       Save the file and now start your MS from the command line.
startManagedWeblogic <MS-Name> <Admin-Server-IP:Port>
i.e. startManagedWeblogic WC_Spaces http://127.0.0.1:7001
If everything is ok then it should not prompt you for username and password.
Pls note that username and password will remain unencrypted.

Apply to individual MS changes (Secured and recommended way)

If you want to go with secured way and want to configure few servers that will run without asking for username and password then you need to go with this approach.
1.       (First time only). If you not started your MS before, you need to start it once from the command line so that it create required directories inside <Middleware-Home>\user_projects\domains\<domain> \servers\<MS-Name> i.e. C:\Oracle\Middleware\user_projects\domains\wc_domain\servers\UCM_server1
2.       Once started successfully, shutdown it.
3.       Create a security folder  in <MS-Name> folder
4.       Copy the boot.properties file from <MiddlewareHome>\user_projects\domains\wc_domain\servers\AdminServer and past it into newly created security folder.
Pls note that you can also create a boot.properties, just open any text editor like notepad and enter the following content:-
username=weblogic
password=welcome1

Don’t worry about plain text username and password. Once you start your MS, username and password will be encrypted with AES and will remain encrypted.

Tuesday, September 27, 2011

How to apply patchset 11gR1PS4 to Oracle WebCenter 11gR1PS3 for Windows?


Patching Scope
This guide will cover the patching information of following products:-
- Oracle Weblogic Server 11gR1PS3 (PS#12395560)
- Oracle WebCenter 11gR1PS3 (PS#12395099)
- Oracle Universal Content Management 11gR1PS3 (PS#12395130)

Patching Pre-requisits
1. Must have a Oracle Support account that have downloading permission
2. Your existing Oracle WebCenter is up and running properly. 
3.  Download the Oracle WebLogic Server 11gR1PS4
4. Download the Oracle Fusion Middleware (WC & ECM) 11gR1PS4 from

Patching Instructions
1. Stop all the servers.
2. Take the backup of Oracle Homes, oracle_common and domain directories
Following diagram will explain the high level steps for this patching process:-


 2. Run the wls1035_upgrade_win32.exe file. Here you need to specify the Middleware home of your weblogic.
3. Run the Patch Set Assistant in order to patch the MDS Schemas using following command:-
ORACLE_HOME\bin\psa.bat -dbType Oracle -dbConnectString //localhost:1521/xe -dbaUserName sys -schemaUserName DEV_MDS
Note:- For WebCenter PS3, you only need to update MDS schema.
4. Merge downloaded directories (disk1 and disk2) of ECM patchset into one single directory and run the Oracle ECM installer (setup.exe) to patch your Oracle ECM software. Here you need to specify the updated middleware home directory.
5. Run the Oracle WebCenter installer (setup.exe) to patch your Oracle WebCenter software. Here you need to specify the updated middleware home directory.
6. Start all the servers.

Post Installation Task
There is no post intallation task from 11GR1PS3 to 11GR1PS4 for our

Monday, September 12, 2011

How to configure embedded (default) LDAP for WebCenter Collaboration Server (i.e. Discussion and Announcement Services)?

Applies to Oracle WebCenter 11G PS3 & PS4

Steps:
If you want to revert back from external or custom LDAP to embedded LDAP, you will not get clearly written steps in WebCenter Administration and Security Guides. Following are the simple steps in order to use embedded LDAP again:-  
Step 1. Enable Embedded LDAP Access
When WebLogic Server is installed, the LDAP access credential is set as a randomized value and encrypted in the config.xml file To reset the access credential for the embedded LDAP:
1.      Log in to the WebLogic Server Administration Console.
2.      In the Domain Structure pane, click wc_domain.

3.      In the Settings pane for wc_domain, click the Security tab, and then click the Embedded LDAP tab.
The Settings Pane for wc_domain displays the embedded LDAP settings
4.      Enter a new password in the Credential field, and reenter it in the Confirm Credential field.
5.      Click Save to save your settings.
6.      Restart the WebLogic server.
After this, you are ready to access the embedded LDAP server with the following values:
·         the DN value for admin access is "cn=Admin"
·         the password is the value you entered in the Credential field
·         the port is the same as the admin port, which by default is 7001

Step 2. Enabling Discussions Setup
1. Stop WC_Collaboration managed server (MS)
2. Change <setup>true</setup> entry to false on
<WebCenter-Domain-Home>\ config\fmwconfig\servers\WC_Collaboration\owc_discussions\jive_startup.xml.
...
<jive>
<!-- When setup is false, you can access the setup tool. -->
<setup>false</setup>
<!-- Database settings -->
3. Start WC_Collaboration MS

Step 3. Running Discussions Setup Screen
1. Log in to the Discussions Server Administration Console at:
http://localhost:8890/owc_discussions/admin
2.  On the Installation Checklist page, click Continue.
3. On the Database Settings page, choose JNDI Datasource, and click Continue.

4. Enter jdbc/OWC_DiscussionsDS in the JNDI Datasource Name field and click Continue.

5. For User, Group and Authentication Systems, select LDAP and click Contrinue.


6. Enter the following values for the embedded LDAP system and click Continue.
LDAP Host : localhost
LDAP Port: 7001
Base DN: ou=people,ou=myrealm,dc=wc_domain
Admin DN: cn=Admin
Admin Password: <Password of embedded LDAP>
 
 

7. For Admin Account Setup, enter the user name (i.e. weblogic)of the user for the Discussions (Jive) administrator.

You can now log in to Oracle Discussions with any user available in the embedded LDAP server.
You can log in to the Oracle Discussions Admin Console at: http://localhost:8890/owc_discussions/admin (use weblogic/<password>)

Friday, July 8, 2011

How to add a Worklist component to a page at runtime using WebCenter Space?

If you want to add Worklist service component to a page at runtime (i.e. from WebCenter Space), you have to perform following two tasks:-

1. Creation of BPEL Connection:
i. Login to your Enterprise Manager
ii. Click WebCenter -> Settings -> Service Configuration -> Worklist
iii. Add a new Connection, select Active Connection, enter your BPEL SOAP URL (like http://<SOA_SERVER_HOSTt>:<SOA_SERVER_PORT>/)
iv. Restart Webcenter managed server.

2. Adding a Worklist component to a page
Once connection has been established successfully, 2nd step is how to add Worklist components from the Resource Catalog to a page. For this follow the following steps:-
i. Login to WebCenter Spaces
ii. Navigate to the relevant page where you want to add Worklist service (OR) create a new page.
iii. Open a page in Edit mode. You can also open page in edit mode by pressing Ctrl+Shift+E
iv. Click the Add Content button on the target region to open the Resource Catalog
v. Navigate to the Alerts and Updates --> Worklist component  and click Add link next to it.
vi. Click Save and then Close to exit page edit mode.

NOTE
: Pls note that Worklist tasks will be displayed inside authenticated pages only. 2ndly, WebCenter Space and BPEL should configured with same LDAP server (Recommended way). You can add worklist task flows in personal pages only.

For Administration of Worklist Connection, pls see http://download.oracle.com/docs/cd/E15523_01/webcenter.1111/e12405/wcadm_worklist.htm#CHDFCDGA

How to add Component on a page, pls see http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e10149/pages_build.htm#CHDHJEEB