CMSDK / iFS 9.0.3

Question

Under iFS version 1.1.x I was told that Oracle does not support more than one iFS schema per Oracle instance. Does this still hold true for CMSDK / iFS 9.0.3? We have a user written application that interacts with the iFS API/schema. We DO NOT use any of the iFS provided protocol servers. We do however run the IfsAgents Server for each iFS schema to maintain / garbage collect in each environment. Will CMSDK / iFS 9.0.3 allow more than one IfsAgent process on a server? I basically want one set of agents per CMSDK/iFS schema installed in one single instance on one server. Does this make sense? Is it possible to do this with the new version of iFS?

Answer 1

Here are the detailed instructions on how to do it. I hope this will work for you:
Setting up multiple CM SDK domains on one host
Introduction
============
The Oracle Content Management SDK (CM SDK) is released as a component of the Oracle 9iAS product suite. Upon installation users can configure the product for use. This by default includes the creation of one CM SDK domain (aka instance) and associated entities. Each of these domains includes a Domain Controller, one set of the CM SDK agents, one or more CM SDK nodes (residing on separate hosts), and one or more CM SDK HTTP nodes (residing on separate hosts).
It is also possible to configure multiple domains on a single middle-tier host. Each such domain would include one CM SDK node, one HTTP node, a Domain controller and a set of agents. There is only one installation of the CM SDK product, in effect only one set of binaries. The configuration process will permit multiple domains to use the same software. This document outlines the process setup such a configuration.
A. Installation
===============
Install Oracle iAS 9.0.2 or 9.0.2.0.1 on your machine. The J2EE (Core) option would suffice.
Install Oracle CM SDK 9.0.3 into your <oracle_home>. After installation is complete, your directory structure will look like this -
<oracle_home>
ifs
cmsdk
bin
lib
j2ee
OC4J_iFS_cmsdk
applications
cmsdk
cmsdk
applications-deployments
config
B. Configuration
================
Creating the First Domain
The CM SDK Configuration Assistant will automatically start when iFS is installed. Follow the instructions in the CM SDK Installation Guide to complete your configuration process. You can also choose to run the Configuration Assistant later. This is done by using the script ifsca in the <oracle_home>/cmsdk/bin directory.
Be sure to choose to create a domain. Call this first domain "DOMAIN1".
Have all the following selected:
Run Domain Controller
Run HTTP Node
Run Node
Your first domain is now ready.
Creating a Second Domain
Run the CM SDK Configuration Assistant. Again create a domain with the same options, but call this second domain "DOMAIN2".
Be sure to give different port numbers for protocols you wish to use.
Disable these protocols on your second domain if they are enabled on the first:
SMB
AFP
E-Mail protocols (IMAP/SMTP)
The configuration will not work as before. It will prompt you with the following dialog:
There already exists an OC4J instance for another HTTP Node configured on this machine. Do you wish to replace that instance? Click "Yes" to replace the instance. Click "No" to leave the instance untouched and not create any instance for this new HTTP Node.
Click "No". This second OC4J instance must be set up manually.
You now have two iFS domains configured within the same <oracle_home>. You may now use "ifsctl" to start and stop each independently. An HTTP Node exists for DOMAIN1, but not for the DOMAIN2; this must now be manually configured to work.
C. Setting Up Your Second OC4J Instance
=======================================
In order to create your second OC4J instance, you must first prepare a new EAR (Enterprise Application Resource) for use.
Preparing an EAR file for Second OC4J Instance
Create a temporary directory for use. Assign it to an environment variable $IFSTMP.
Copy the <oracle_home>/ifs/cmsdk/lib/cmsdk.ear file into $IFSTMP.
Go into $IFSTMP. Uncompress the EAR file. Use the following command:
jar xvf cmsdk.ear
Edit the application.xml file located in $IFSTMP/META-INF directory. You will see the following contents in the file:
<application>
<description>Oracle ifs Administration</description>
<display-name>Oracle ifs Administration<display-name>
<module>
<web>
<web-uri>cmsdk.war</web-uri>
<context-root>/cmsdk</context-root>
</web>
</module>
</application>
Replace the term "cmsdk.war" with "domain2.war" and "cmsdk" with "domain2" (above). "domain2" is now the new name of your second OC4J instance.
Go into $IFSTMP. Rename the cmsdk.war file to "domain2.war". Now use the following command to jar it all up (NOTE: The JAR process will ignore the $IFSTMP/META-INF/MANIFEST.MF file which is O.K.)
jar cvf domain2.ear
You now have a EAR file which you can use for deployment.
Deploying EAR file
==================
Now open a web browser and connect to the iAS Enterprise Manager Console. You must open your browser on the machine where you put your new EAR file.
Under the "System Components" section, choose "Create OC4J Instance".
You will be prompted for a new name for your chosen OC4J Instance. Enter "OC4J_iFS_domain2". After the instance has been created, select "OK" and return to the main EMD page.
You will now see your newly created OC4J instance listed. Click on it.
You will now see information about your OC4J instance. Under the "Applications" section, click on "Deploy EAR File".
You will now be presented with a Deploy Application wizard. Read and click through to "Step 2" of the wizard.
You will now need to name and deploy your EAR file. In the text box "J2EE Application", indicate the path to your modified EAR file from the "Preparing And Deploying Second Instance for OC4J" section. You will find your domain2.ear in $IFSTMP. You can also click the "Browse..." button to find it.
For the text box marked "Application Name" enter "domain2".
For the rest of the Deployment Wizard steps. You can simply click "Next" and accept all the defaults. After "Step 8", click "Deploy".
You should have the following setup:
OC4J Instance Name Domain Name Application Name EAR
OC4J_iFS_cmsdk domain1 cmsdk cmsdk.ear
OC4J_iFS_domain2 domain2 domain2 domain2.ear
You now have a second OC4J instance of CM SDK recognized by the iAS Enterprise Manager Console. It does not work yet. You must now manually prepare your new OC4J instance.
Your directory structure now looks like
<oracle_home>
ifs
cmsdk
bin
lib
j2ee
OC4J_iFS_cmsdk
applications
cmsdk
cmsdk
applications-deployments
config
OC4J_iFS_domain2
applications
domain2
domain2
applications-deployments
config
Setting Up OC4J Configuration Files for Your Second Instance
First make a backup copy, then modify the file <oracle_home>/opmn/conf/opmn.xml. Look for a section that looks something like this
<oc4j maxRetry="3" instanceName="OC4J_ifs_cmsdk" gid="OC4J_iFS_cmsdk" numProcs="1">
<config-file path="/iashome/j2ee/OC4J_iFS_cmsdk/config/server.xml"/>
<java-option value="-Xmx256m "/>
<oc4j-option value="-properties"/>
<port ajp="3001-3100" jms="3201-3300" rmi="3101-3200"/>
<environment>
<prop name="LIBPATH" value="/iashome/lib32:/iashome/lib"/>
<prop name="DISPLAY" value=":0.0"/>
<prop name="NLS_LANG" value=".UTF8"/>
<prop name="LD_LIBRARY_PATH" value="/iashome/lib32:/iashome/lib"/>
<prop name="SHLIB_PATH" value="/iashome/lib32:/iashome/lib"/>
</environment>
Look for the section where instanceName="OC4J_iFS_domain2". It looks like this:
<oc4j instanceName="OC4J_iFS_domain2" gid="OC4J_iFS_domain2">
<config-file path="/iashome/j2ee/OC4J_iFS_domain2/config/server.xml"/>
Now copy the first <environment> section into the section for your second OC4J instance.
Make a backup copy, then modify the file <oracle_home>/j2ee/OC4J_iFS_domain2/config/application.xml. Comment out the following sections:
<library path="../../../jlib/uix2.jar" />
<library path="../../../jlib/share.jar" />
Copy the file <oracle_home>/j2ee/OC4J_iFS_cmsdk/config/oc4j.properties to the directory <oracle_home>/j2ee/OC4J_iFS_domain2/config/. Make a backup copy, then edit your new copy of the file. It will look something like this:
java.awt.headless=true
IFS.DOMAIN.Name=ifs://mydbserver:1521:orcl8:DOMAIN1
IFS.DOMAIN.NODE.Name=myappserver.oracle.com HTTP Node
IFS.DOMAIN.NODE.OracleHome=/iashome
replace the domain name DOMAIN1 with DOMAIN2.
Make a backup, then edit the file <oracle_home>/j2ee/OC4J_iFS_domain2/applications/domain2/domain2/index.html.
change all instances of "cmsdk" to "domain2"
Edit the file <oracle_home>/j2ee/OC4J_iFS_domain2/config/default-web-site.xml. Look for the following section:
<default-web-app application="default" name="defaultWebApp" root="/j2ee"/>
<web-app application="default" name="dms" root="/dmsoc4j"/>
<web-app application="domain2" name="domain2" root="/domain2" load-on-startup="true"/>
Add the last line to that section.
Copy the file <oracle_home>/j2ee/OC4J_iFS_cmsdk/application-deployments/cmsdk/cmsdk/orion-web.xml into the directory <oracle_home>/j2ee/OC4J_iFS_domain2/application-deployments/domain2/domain2. Make a backup copy of the file if it already exists in the destination directory.
Log into the Enterprise Manager Console. Under the "System Components" section, click on your second domain (myserver:1521:myservice:DOMAIN2) to set that up. Under "Configuration" click "Server Configurations".
Then click on HttpAdminServerConfiguration. Under the Properties, modify the following properties with these values
IFS.SERVER.APPLICATION.UIX.ApplicationServletMount /domain2/admin
IFS.SERVER.APPLICATION.UIX.ContentServletMount /domain2/content
IFS.SERVER.APPLICATION.UIX.StaticResourcesMount /domain2/static
Save the above properties. Now, you have to change certain properties in the DavServerConfiguration. From the above UI, cliek on the DavServerConfiguration and click Properties. Modify the following property to have the value shown below:
IFS.SERVER.PROTOCOL.DAV.ContextServletPath /domain2/content
Save and exit out of EMD.
Restart EMD, iAS & iFS (both domains). At this point both the domains should be up and running.
If you are able to access the following URLs and use them, then your multi iFS domain has worked correctly.
EMD
http://<server-name>:1810
Domain 1
Content Servlet - http://<server-name>:<port-number>/cmsdk/content
Admin Servlet - http://<server-name>:<port-number>/cmsdk/admin
Domain 2
Content Servlet - http://<server-name>:<port-number>/domain2/content
Admin Servlet - http://<server-name>:<port-number>/domain2/admin
You should also be able to see the logs of two different machines domains, nodes under directory $ORACLE_HOME/ifs/cmsdk/log.
D. Notes
========
Oracle CM SDK does not support installation of multiple 9iAS Oracle Homes on the same machine.