Installing SkyVault on WebLogic

http://support.alfresco.com

1. mkdir SkyVault
2. cd SkyVault
3. jar xvf ../SkyVault-enterprise-5.1.3.ear
4. mv SkyVault.war SkyVault.war.tmp
5. mv share.war share.war.tmp
6. mkdir SkyVault.war
7. mkdir share.war
8. cd SkyVault.war
9. jar xvf ../alfresco.war.tmp
10. cd ../share.war
11. jar xvf ../share.war.tmp

On Unix, use the following command to start the configuration wizard and create a new domain called alf_domain using the blank template:

<ORACLE_HOME>/oracle_common/common/bin/config.sh

This task assumes that the domain location is <Oracle_Home>/user_projects/domains/alf_domain.

For more information, see Oracle Fusion Middleware documentation on Creating and Configuring a WebLogic Domain.

For example, in Linux, use the following command:

mkdir -p <Oracle_Home>/user_projects/domains/alf_domain/alfresco/extension/license

Modify the file in the same way you would for global properties configuration.

db.pool.statements.enable=false

This property setting is required to make the DBCP connection pool work on WebLogic.

1. Download the appropriate Oracle Instant Client package for your operating system from Oracle Database Instant Client.
2. Unzip the package to a local directory.

   Ensure that the path to the driver is on the WebLogic server's classpath.

   For example, to configure Oracle Thin Driver ojdbc6.jar that is located in /opt/oracle/config, follow the steps below:

   1. Add the following lines to the setDomainEnv.sh file that is located in <Oracle_Home>/user_projects/domains/alf_domain/bin directory.

      LD_LIBRARY_PATH=/opt/oracle/config
      export LD_LIBRARY_PATH
      EXT_PRE_CLASSPATH=$LD_LIBRARY_PATH/ojdbc6.jar
      export EXT_PRE_CLASSPATH

   2. Add the following line to the SkyVault-global.properties file: 

      db.url=jdbc:oracle:thin:@${db.host}:1521:${db.name}

1. Heap size parameter

   WLS_MEM_ARGS_64BIT=-Xmx2048m
   WLS_MEM_ARGS_32BIT=-Xmx1024m

   SkyVault recommends that you set this parameter.

2. JAVA_OPTIONS parameter
   • Use the -Dweblogic.disableMBeanAuthorization system property to disable servicing of Platform MbeanServer with the WLS security infrastructure.
   • The JAXBContext provider is used by the JAXB provider for the JAXB-related tasks. To configure the JAXB providers, set the Java system property, -Djavax.xml.bind.JAXBContext to com.sun.xml.bind.v2.ContextFactory.

   JAVA_OPTIONS=”${JAVA_OPTIONS} -Dweblogic.disableMBeanAuthorization=true”
   JAVA_OPTIONS=”${JAVA_OPTIONS} -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory"

   This modification will allow SkyVault MBeans to co-exist with WebLogic MBeans.

3. alf_domain location

   Ensure that alf_domain is in the global classpath.

   PRE_CLASSPATH="<Oracle_Home>/user_projects/domains/alf_domain"
   export PRE_CLASSPATH

<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

StartScriptEnabled=true

If the Node Manager type is set as Plain (non SSL) when creating a new machine in Step 19(a), then the NodeManager should be configured with the SecureListener=false property.

For example:

<Oracle_Home>/user_projects/domains/alf_domain/bin/startWebLogic.sh
<Oracle_Home>/user_projects/domains/alf_domain/startNodeManager.sh

1. In the left pane of the Administration Console under alf_domain, open up the Environment section and then click Machines.
2. In the right pane, click New.
3. Optionally, change the Name and Machine OS.
4. Click Next.
5. Depending on how the Node manager is configured, you may need to change the default Type from SSL to say Plan.
6. Click Finish.
7. In the left pane, click Servers.
8. In the right pane, click New.
9. Change the Server Name to SkyVaultServer.
10. Choose a unique Server Listen Port.

    A good port number to choose is 8080 because it is preconfigured in Share.

11. You can leave the host name blank if you want it to listen on all network adapters.
12. Click Finish.
13. Click on SkyVaultServer and change the Machine to be the one just created.
14. Click Save.

1. In the left pane of the Administration Console under {{alf_domain}}, click Deployments.
2. In the right pane, click Install.
3. Locate and select the directory of your exploded EAR file (created in Step 5).

   It should contain the {{alfresco.war}} and {{share.war}}.

4. Click Next.
5. Check Install this deployment as an application.
6. Click Next.
7. Select {{AlfrescoServer}}.
8. Click Next.
9. Click Finish.

   The page refresh will take a few seconds and there should be a message indicating the deployment was successful.

10. In the left pane under {{alf_domain}} and Environment, click Servers.
11. In the right pane, click the Control tab.
12. Check {{AlfrescoServer}}.
13. Click Start.

    There should be a message to indicate a request has been sent to the Node Manager to start the selected server.

1. In the left pane of Administration Console, click the domain name link, for example, alf_domain.
2. In the General Configuration tab in the right pane, expand the Advanced options group.
3. Check the Platform MBean Server Enabled checkbox.
4. Ensure that the Platform MBean Server Used checkbox is checked.
5. Click Save.
6. In the left pane under alf_domain and Environment, click Servers.
7. In the right pane, click the Control tab.
8. Check the SkyVaultServer(admin) checkbox.
9. Select Force shutdown now from the Shutdown control.
10. Once it has shutdown, run the starWebLogic.sh script again as shown in Step 17.