Installing on Oracle Application Server 10.1.3.1

Document created by resplin Employee on Jun 6, 2015
Version 1Show Document
  • View in full screen mode

Obsolete Pages{{Obsolete}}

The official documentation is at: http://docs.alfresco.com



InstallationBack to Server Installation


Alfresco 2.1 instructions


Pre-requisites:


  • Install Oracle 10g and create an 'alfresco' user with ‘connect’ and ‘resource’ permissions
  • Install Oracle Application Server 10(J2EE + Web) and create domain.



Installation Steps:


  • Navigate to the OC4J container in which you are going to install Alfresco.
    • Select the Administration Tab.
    • Select Administration Tasks ‐> Properties ‐> Shared Libraries described as 'Manage the shared libraries of this OC4J instance.'
    • Select create.
    • Enter the name for the library and its version, and hit next
    • Add the path to the archive (The Cryptix jar can be found in the alfresco.war or get it here http://www.cryptix.org/) , and hit next, then press Finish.
  • Navigate to the OC4J container in which you are going to install Alfresco.
    • Select the Administration Tab
    • Select Administration Tasks ‐> Properties ‐> Server Properties described as 'Configure server properties for this OC4J instance.'
Increase ‐XX:MaxPermSize=256M (increase Maximum heap size accordingly)
Click 'Add Another Row'
Enter ‐Doc4j.jmx.security.proxy.off=true
Click 'Add Another Row'
Enter ‐XX:CompileCommand=exclude,org/apache/lucene/index/IndexReader$1,doBody
Click 'Add Another Row'
Enter ‐XX:CompileCommand=exclude,org/alfresco/repo/search/impl/lucene/index/IndexInfo$Merger,mergeIndexes
Click 'Add Another Row'
Enter ‐XX:CompileCommand=exclude,org/alfresco/repo/search/impl/lucene/index/IndexInfo$Merger,mergeDeletions

  • Select apply
  • Restart OC4J instance(OAS_INSTALL/opmn/bin/opmnctl stopall then OAS_INSTALL/opmn/bin/opmnctl startall)
  • Unwar alfresco.war
  • Open the WEB‐INF/classes/alfresco/repository.properties file in a text editor
  • Set 'dir.root' to the fully qualified name of the directory where you wish to place the Alfresco repository
  • Set database connection properties in WEB‐INF/classes/alfresco/repository.properties to
db.driver= oracle.jdbc.OracleDriver
db.name=alfresco
db.url= jdbc:oracle:thin:@localhost:1521:alfresco
db.username=alfresco
db.password=alfresco

  • Open WEB‐INF/classes/alfresco/domain/ hibernate‐cfg.properties file in a text editor and set

hibernate.dialect= org.hibernate.dialect.Oracle9Dialect


  • Rewar alfresco.war
  • Navigate to the OC4J container. Make sure it has the required shared libraries.
  • Hit deploy to start the deployment wizard.
    • Select the location of the alfresco war. Allow the wizard to build a new deployment plan.
    • Click Next.
    • Enter the application name (e.g. Alfresco), leave all other values to the defaults, and click next.
    • In the final step the class loading needs to be configured:
    • Select Configure Class Loading
    • Deselect Inherit parent application's shared library imports
    • Import the following libraries:
    • Cryptix as previously loaded into the shared library area
    • The JDBC driver
    • This is sufficient to deploy with the default settings.
    • To add a location for an extensions directory:
    • Select «Add Another Row' on Configure Application Libraries
    • Enter the root of the config directory (one that contains alfresco/extension)
  • Hit Deploy. This will take some time. Some progress information is reported. The alfresco.log file is located in 'OAS_HOME'/j2ee/home the deployed application is in 'OAS_HOME'/j2ee/home/applications/Alfresco
  • Test the installation by opening http://SERVER_IP:7777/alfresco in a browser

Common


Install the prerequisites for Alfresco.

Install oracle application server. If your server uses DHCP and not a fixed IP address you *will* need to add support for an MS loopback netwrok connection. This is covered in the OAS installation guide. In the urls to follow I wil assume this was required and a loopback connection was created on 10.10.10.10 and the default port of 8888 was used in the install.

Install your database of choice and configure an appropriate user for the Alfresco repository and make sure there is a database/tablespace/schema for this user to use.

Start OAS. This can be done by going to the directpry 'OAS_INSTALL'/opmn/bin and then run 'opmnctl startall'. 'opmnctl status' can be used to monitor start up. THis will start OC4J and supporting services.

To successfully deploy Alfresco requires that the Cryptix library included with Alfresco be loaded as a shared library (or there are class loading issues). You probably want to load the JDBC jar for your database as shared library.

Loading a jar as a shared library


  1. Open 'http://10.10.10.10:8888/em' and login as oc4jadmin using the password set at install time.
  2. Navigate to the OC4J container in which you are going to install Alfresco.
  3. Select the Administration Tab
  4. Select Administration Tasks -> Properties -> Shared Libraries  descibed as 'Manage the shared libraries of this OC4J instance.'
  5. Select create
  6. Enter the name for the library and and its version, and hit next
  7. Add the path to the archive, and hit next
  8. The final screnn allows you to configure which shared libraries your imported library will use. There is nothing required, so just hit finish.

This process can be repeated. The UI can also be used to removed shared libraries.

The Cryptix jar can be found in the alfresco.war.

The amount of memory allocated to the OC4J instance and for PermGenSpace may not be sufficient.
To alter the OC4J server start up option for these properties


  1. Navigate to the OC4J container in which you are going to install Alfresco.
  2. Select the Administration Tab
  3. Select Administration Tasks -> Properties -> Server Properties  descibed as 'Configure server properties for this OC4J instance.'
    1. Increase -XX:MaxPermSize=256M       from 128
    2. Increase the Maximum heap size
  4. Select apply

You will have to stop and start the OC4J instance for the changes to take effect. (On the 'Home' Tab for the OC4J instance). Note if you are using opmn these options are in 'OAS_HOME'\opmn\conf\opmn.xml.


V1.4.x


Navigate to the OC4J container. Make sure it has the required shared libraries.

Select the applications tab.

Hit deploy to start the deployment wizard.


  1. Select the location of the alfresco war. Allow the wizard to build a new deployment plan. Click Next.
  2. (Uploading will take a few monents)
  3. Enter the appliaction name (e.g. Alfresco), leave all other values to the defaults,  and click next.
  4. In the final step the class loading needs to be configured:
    1. Select Configure Class Loading
    2. Deselect Inherit parent application's shared library imports
    3. Import the following libraries
      1. Cryptix as previously loaded into the shared library area
      2. The JDBC driver
      3. oracle.xml



This is suffiecient to deploy with the default settings.

To add a location for an extensions directory:


  1. select 'Add Another Row' on  Configure Application Libraries
  2. enter the root of the config direcory (one that contains alfresco/exptension)

At the moment, I am not clear where this path is inserted into the class path. The location is certianly used and should be fine for entries in the extension folder, license etc.

Select OK

At this point you could save the deployment plan - or just deploy.

Hit Deploy. This will take some time. Some progress information is reported.
The alfresco.log file is located in 'OAS_HOME'/j2ee/home the deployed application is in 'OAS_HOME'/j2ee/home/applications/Alfresco

Wait for a notification like 'Application Deployer for Alfresco COMPLETES. Operation time: xxxxxx msecs'

Once deployment is complete you can access the web client using http://10.10.10.10:8888/alfresco
FTP, WebDav will also be available.

On my deployment with DHCP and loopback, CIFS access was not as straight forward as //Name/Alfresco but this is likely to be related to deploying on 10.10.10.10 and has not been investigated further. I did manage to map a network drive from previous settings, so CIFS is alive and working. The Loopback connection may have some issues with CIFS trying to connect.

The application can be undeployed from the OC4J Applications tab.


V2.0.x


Deployment in the same fashon as 1.4.x gives an RMI error.

A work around for this isue will appear here when complete.




Extra Info


Here is some extra info found whilst browsing forums:

'I've further tested this here and have successfully installed Alfresco 201 on OAS. I found the workaround in the Spring Forums, you'll need to start OAS with the JVM parameter':

-Doc4j.jmx.security.proxy.off=true 

'I used  'Add Another Row' in the deployment steps and provided the absolute path for the extension folder.

You might find now that you have your 1.4 running if you take the extension out of the WAR file and use Add Another Row - it should work.'

Attachments

    Outcomes