MySQL 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 MySQL database on Amazon RDS for use with Content Services, with the following prerequisites:

  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 MySQL database connector.

    The MySQL database connector is required when installing with MySQL, and allows the MySQL database to talk to the server. Check the Supported Platforms page for the correct driver.

    1. Download mysql-connector-java-8.x.x from the MySQL download site.
    2. Copy the JAR file into the /lib directory.

      For example, for Tomcat, copy the JAR file 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. Create a user named alfresco.
  8. Set the new user’s password to alfresco.
  9. Open the <classpathRoot>/alfresco-global.properties file.
  10. Edit the following line with 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

  11. Set and uncomment the database connection properties as shown below:
    db.name=alfresco
    db.username=alfresco
    db.password=alfresco
    db.host=alfqa-mysql5-6-19a.cw4mo3qj8qdu.us-east-1.rds.amazonaws.com
    db.port=3306
    db.pool.max=275
    
    # MySQL connection
      
    db.driver=com.mysql.jdbc.Driver
    db.url=jdbc:mysql://${db.host}:${db.port}/${db.name}?useUnicode=yes&characterEncoding=UTF-8
    
    Note: Ensure that these database connection properties aren’t commented out.
  12. Save the file.
  13. Restart the Content Services server.