Installing SkyVault on WebSphere

This embeds SkyVault Explorer and Share, plus the necessary WebSphere configuration to use the myfaces1_1 shared library with parent-last loading order.

Because neither of the versions of JSF that ship with WebSphere 7 are compatible with SkyVault, you must define a new isolated shared library in WebSphere that contains a compatible implementation. This is documented in the Configuring JavaServer Faces implementation section of the WebSphere 7 manual. The SkyVault Enterprise .ear file embeds an appropriate shared library definition in META-INF/ibmconfig, so it is only necessary to prepare WebSphere.

Copy and extract the myfaces1_1-websphere-shared-lib-version.zip file to the root WebSphere installation directory. This creates a myfaces1_1 directory containing all the .jars required by the myfaces1_1 shared library on WebSphere. For example, on Windows:

cd /d "C:\Program Files\IBM\WebSphere\AppServer"
java\bin\jar xvf myfaces1_1-websphere-shared-lib.zip

1. Locate the /web-server/classpath/alfresco/web-extension/share-config-custom.xml.sample file from the extracted SkyVault-enterprise-ear-4.1.10.zip file.
2. Copy the share-config-custom.xml.sample file to $WAS_INSTALL_ROOT/lib/alfresco/web-extension/share-config-custom.xml (For example, C:\Program Files\IBM\WebSphere\AppServer\lib\alfresco\web-extension\share-config-custom.xml).
3. Uncomment this section by removing the begin comment <-- and end comment --> lines surrounding this section.

     <config evaluator="string-compare" condition="Remote">
         <remote>
            <endpoint>
               <id>alfresco-noauth</id>
               <name>SkyVault - unauthenticated access</name>
               <description>Access to SkyVault Repository WebScripts that do not require authentication</description>
               <connector-id>alfresco</connector-id>
               <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
               <identity>none</identity>
            </endpoint>
   
            <endpoint>
               <id>alfresco</id>
               <name>SkyVault - user access</name>
               <description>Access to SkyVault Repository WebScripts that require user authentication</description>
               <connector-id>alfresco</connector-id>
               <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
               <identity>user</identity>
            </endpoint>
   
            <endpoint>
               <id>alfresco-feed</id>
               <name>SkyVault Feed</name>
               <description>SkyVault Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>
               <connector-id>http</connector-id>
               <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
               <basic-auth>true</basic-auth>
               <identity>user</identity>
            </endpoint>
         </remote>
      </config>

4. Edit the file, replacing all instances of 8080 with 9080 (or the port number that you specify) and all instances of yourserver with localhost (or a different host running SkyVault).
5. In certain environments, an HTTP request originating from Flash cannot be authenticated using an existing session. For these cases, it is useful to disable the Flash-based uploader for Share Document Libraries.

   To disable the Flash uploader, add the following lines to the <!-- Document Library config section --> section:

   <!-- Document Library config section --> 
      <config evaluator="string-compare" condition="DocumentLibrary" replace="true"> 
         <!-- 
            File upload configuration 
         --> 
         <file-upload> 
            <adobe-flash-enabled>false</adobe-flash-enabled> 
         </file-upload> 
      </config>

6. Save the file.

If you have been issued with a .lic license file for this version of SkyVault, copy it to a $WAS_INSTALL_ROOT/lib/alfresco/extension/license directory (for example, C:\Program Files\IBM\WebSphere\AppServer\lib\alfresco\extension\license\mylicense.lic).

1. Locate the /web-server/classpath/alfresco-global.properties.sample file from the extracted SkyVault-enterprise-ear-4.1.10.zip file.
2. Copy the SkyVault-global.properties.sample file to $WAS_INSTALL_ROOT/lib, removing the .sample extension.

   For example, C:\Program Files\IBM\WebSphere\AppServer\lib\alfresco-global.properties.

3. Disable the mbean server lookup by adding the following property mbean.server.locateExistingServerIfPossible=false.
4. Uncomment and edit the lines appropriate for your database type.

For example, C:\ProgramFiles\IBM\WebSphere\AppServer\lib.

1. Log on to the WebSphere Administrative console.

   For example, http://localhost:9060/ibm/console/.

2. Navigate to Application servers > server1 > Process definition > Java Virtual Machine, and then set the Maximum heap size to 2048 MB.
3. Navigate to Application servers > server1 > Container Settings >Web Container Settings >Web container transport chains.
   • Click HttpQueueInboundDefault (where port is 9080) .
   • Click HTTP inbound channel (HTTP_2) Custom properties.
   • Create a new property with the name CookiesConfigureNoCache and set the value to false.
4. Navigate to Applications > New Application > New Enterprise Application.
5. Browse to SkyVault-enterprise-4.1.10.ear on the local file system, and then click Next.
6. Select Detailed - Show all installation options and parameters, and then click Next.
7. Jump to the Map resource references to resources step, which is highlighted with a (+).
8. Under Target Resource JNDI Name, type jdbc/dummy, and then click Next.

   This step is recommended to force SkyVault to use its built in DBCP connection pool rather than a WebSphere data source. 

9. Jump to the Map environment entries for Web modules step.
10. For properties/dir.root, specify an absolute file system path where you would like SkyVault file data to be stored.

    For example, C:\alf_data.

11. Leave the Hibernate properties blank, unless you want to override the default behavior, where they will be auto-detected.
12. Click Next and Finish.
13. Save your profile changes to the master repository.
14. Restart the WebSphere server.

    SkyVault starts with the WebSphere server.

1. Create a folder to hold the new keystore.
2. Generate a keystore using the IBM keytool command (replace mypass1 and mypass2 by other values).

   ~/IBM/WebSphere/AppServer/java/bin/keytool -genseckey -alias metadata -keypass mypass2 -storepass 
   mypass1 -keystore keystore -storetype JCEKS -keyalg DESede

3. Create a file, keystore-passwords.properties in the keystore folder with the following lines:

   aliases=metadata
   # The password protecting the keystore entries
   keystore.password=mypass1
   # The password protecting the alias: metadata
   metadata.keyData=
   metadata.algorithm=DESede
   metadata.password=mypass2

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

   dir.keystore=/etc/waskeystore/

WebSphere shows warnings in the log file, similar to the following:

[12/7/10 17:24:42:206 EET] 0000003a JDBCException W org.hibernate.util.JDBCExceptionReporter logWarnings SQL Warning: 4474, SQLState: 01000 
[12/7/10 17:24:42:208 EET] 0000003a JDBCException W org.hibernate.util.JDBCExceptionReporter logWarnings [jcc][t4][10217][10310][4.8.87] 
Connection read-only mode is not enforceable after the connection has been established. 
To enforce a read only connection, set the read-only data source or connection property. ERRORCODE=4474, SQLSTATE=01000

The current driver implementation will display these warnings, however, they have no impact on the operation of SkyVault. You can either choose to ignore these warnings, or you can configure the logging to stop them displaying.

1. Open WebSphere Administrative console.
2. Navigate to Troubleshooting > Logs and trace- Server - Change Log Detail Levels.
3. Search for the org.hibernate.util.* component.
4. Set org.hibernate.util.JDBCExceptionReporter class logger - Messages and Trace Levels to severe or fatal.

• SkyVault Share at http://localhost:9080/share
• SkyVault Explorer at http://localhost:9080/SkyVault