Multiple ultrasearch portlets with unique datasources

Question

Hi All,
I need to know,Is it possible to create multiple ultrasearch portlets with unique datasources?If yes,steps we need to follow for the same would really be helpful.
Regards,
Milind

Answer 1

The Ultra Search portlet is a JSP application deployed in it's own
individual .ear file on Oc4J. It connects to an Ultra Search database, and
specifically to a schema that hosts the Ultra Search instance. Connectivity
is configured via the data-sources.xml file, which is located in
$ORACLE_HOME/j2ee/OC4J_Portal/config/data-sources.xml
If you want to run two Ultra Search portlet instances, You'll have to
perform the following. (Note, I'm describing manual steps. If you use
Enterprise Manager, some of these steps may be automatically done for you):
(1) Create a .ear file containing the Ultra Search Portlet, along with
modifications you have performed to it if any.
(2) Edit $ORACLE_HOME/j2ee/OC4J_Portal/config/server.xml, creating a new
<application> entry referencing the .ear file in (1).
(3) Edit $ORACLE_HOME/j2ee/OC4J_Portal/config/default-web-site.xml, defining
a new <web-app> for the application you've created in (2).
By now, you should see that OC4J has expanded the ear file you created in
(1) into a directory structure. If this has not occurrred, bounce Oc4J. If
that doesn't help, you might have made a mistake in one of the steps in (1),
(2) or (3) and will have to examine the Oc4J log files to determine exactly
what went wrong.
(4) Edit $ORACLE_HOME/j2ee/OC4J_Portal/config/data-sources.xml, adding a new
<data-source> section defining connectivity to the second Ultra Search
instance you want your second portlet to connect to.
For example, if the original data-sources.xml file contained the following
entry:
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="UltraSearchDS"
location="jdbc/UltraSearchPooledDS"
username="user1"
password="password1"
url="jdbc:oracle:thin:@host1.us.oracle.com:1521:sid1"
connectionCachingEnabled="false" />
You'll now have to add a second <data-source> element as follows:
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="UltraSearchDS_2"
location="jdbc/UltraSearchPooledDS_2"
username="user2"
password="password2"
url="jdbc:oracle:thin:@host2.us.oracle.com:1521:sid2"
connectionCachingEnabled="false" />
(5) Edit the data source reference in the second portlet.
The location attribute is used by the Ultra Search portlet to lookup the
connectivity info. Hence, you must edit your second portlet's
common_customize_instance.jsp file to use the correct key. To do this,
locate the file common_customize_instance.jsp. If your .ear file was
expanded into directory $SECOND_EAR_FILE_DIR, then look for
$SECOND_EAR_FILE_DIR/query/common_customize_instance.jsp.
Edit this file and change the file that reads:
String m_datasource_name = "jdbc/UltraSearchPooledDS";
to :
String m_datasource_name = "jdbc/UltraSearchPooledDS_2"; (or use whatever
key you entered in in your new <data-source> tag.
(6) Touch the search.jsp file to force recompilation.
When you save the common_customize_instance.jsp file edited in (5), OC4J
should automatically re-compile the Ultra Search portlet code.
common_customize_instance.jsp is included by the main JSP (search.jsp).
However, if this does not happen, you may need to "touch"
$SECOND_EAR_FILE_DIR/query/portlet/search.jsp. Updating the timestamp of
this file tricks Oc4J into recompiling it.