SQL Server Database on Amazon RDS - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

You can configure a SQL Server database on Amazon RDS for use with Content Services, with the following prerequisites:

To configure the database:

  1. Use the ssh command to connect to the Amazon EC2 instance using a provided .ppk key.
    • For Amazon Linux, the user name is ec2-user.
    • For RHEL5, the user name is either root or ec2-user.
    • For Ubuntu, the user name is ubuntu. For SUSE Linux, the user name is root.
  2. Execute sudo su to change to root.
  3. Install Content Services.
  4. Install the Microsoft SQL Server database connector to allow the database to talk to the server.

    Check the Supported Platforms page for the correct driver version.

    1. Download sqljdbc4.jar from the Microsoft SQL Server download site.
    2. Copy the JDBC driver into the <TOMCAT_HOME>/lib directory.
  5. Install and use a database tool to connect to the Amazon RDS.
  6. Create a database named alfresco.
  7. Enable snapshot isolation mode with the following command:
     ALTER DATABASE alfresco SET ALLOW_SNAPSHOT_ISOLATION ON;
    
  8. Create a user named alfresco.
  9. Set the new user’s password to alfresco.
  10. Open the <classpathRoot>/alfresco-global.properties file.
  11. Locate the property: dir.root=
  12. Edit this to set an absolute path to point to the directory in which you want to store Content Services data. For example: dir.root=C:/Alfresco/alf_data
  13. Set and uncomment the database connection properties as shown below:
    db.name=alfresco
    db.username=alfresco
    db.password=alfresco
    db.host=sql-alfresco.cw4mo3qj8qdu.us-east-1.rds.amazonaws.com
    db.port=1433
    db.pool.max=275
    db.txn.isolation=4096
    
    # SQL Server connection
    
    db.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver
    db.url=jdbc:sqlserver://${db.host}:${db.port};databaseName=${db.name}
    
  14. Save the file.
  15. Restart the Content Services server.