Migrate an existing configuration to a new SQL Server or Oracle database

Create a new configuration that is attached to the new database, set up that new configuration with your existing information, and then switch your users to the new configuration.

About this task

This setup is for an existing configuration that is published to Ellucian GO that you want to move to SQL Server or Oracle. This setup allows you to minimize downtime for your users.

Procedure

  1. Create an instance of the SQL Server or Oracle database that you want to use.
  2. Define a database user with the following permissions:

    In SQL Server, the user needs to have db owner permissions. In Oracle, give the user permissions as follows (where MOBILEDEV represents the username that you create):

    GRANT CREATE SESSION TO MOBILEDEV;
GRANT BAN_DEFAULT_M TO MOBILEDEV;
GRANT BAN_DEFAULT_Q TO MOBILEDEV;
ALTER USER MOBILEDEV DEFAULT ROLE BAN_DEFAULT_M;
ALTER USER MOBILEDEV DEFAULT TABLESPACE DEVELOPMENT;
ALTER USER MOBILEDEV TEMPORARY TABLESPACE TEMP;
GRANT CREATE TABLE TO MOBILEDEV;
GRANT UNLIMITED TABLESPACE TO MOBILEDEV;
GRANT CREATE SEQUENCE TO MOBILEDEV;
  3. Create a copy of your existing <sis>-mobileserver-config.groovy file, giving it a name different from any existing versions.
    Place it in a new <tomcat-userhome>/ellucianmobile/ directory — for example, <tomcat-userhome>/ellucianmobile/banner-sql-mobileserver/banner-sql-mobileserver-config.groovy.
  4. Add the following code to the new config.groovy file, replacing the highlighted text with the correct values for your institution. You can also adjust the properties if necessary:

    For SQL Server

    dataSource.driverClassName = "com.microsoft.sqlserver.jdbc.SQLServerDriver"

    dataSource.url = "jdbc:sqlserver://server:port;databaseName=mobile_server_db"

    dataSource.username = "mobiledev"

    dataSource.password = "MyPasswd99"

    dataSource.properties.maxActive = 5

    dataSource.properties.minIdle = 1

    dataSource.properties.maxIdle = 2

    dataSource.properties.maxWait = 10000

    dataSource.properties.minEvictableIdleTimeMillis=60000

    dataSource.properties.timeBetweenEvictionRunsMillis=60000

    dataSource.properties.testWhileIdle=true

    dataSource.properties.validationQuery = 'select 1'

    grails.plugin.databasemigration.updateOnStartFileNames = ['changelog-mssql.groovy']

    For Oracle

    dataSource.driverClassName = "oracle.jdbc.OracleDriver"

    dataSource.url = "jdbc:oracle:thin:@server:port:SID"

    dataSource.username = "mobiledev"

    dataSource.password = "MyPasswd99"

    dataSource.properties.maxActive = 5

    dataSource.properties.minIdle = 1

    dataSource.properties.maxIdle = 2

    dataSource.properties.maxWait = 10000

    dataSource.properties.minEvictableIdleTimeMillis=60000

    dataSource.properties.timeBetweenEvictionRunsMillis=60000

    dataSource.properties.testWhileIdle=true

    dataSource.properties.validationQuery = 'select 1 from dual'

    grails.plugin.databasemigration.updateOnStartFileNames = ['changelog-oracle.groovy']

  5. Update your grails.serverURL to reflect your new webapp name from Tomcat.
    For example, if you renamed the WAR file to banner-mobileserver-sql.war, then change the URL to match the webapp like this: grails.serverURL=https://hostname/banner-mobileserver-sql.
  6. Now that the new mobileserver configuration file is in place, in the Tomcat webapps folder, copy the existing WAR file to the new mobileserver name.
    If Tomcat is running, Tomcat will automatically deploy the WAR file using the settings in your new config.groovy file. If Tomcat is not running, start it to deploy the new mobileserver. For example, the new WAR file could be named banner-sql-mobileserver.war.
  7. In the Cloud Configuration system, click the Manage Configurations button manage configuration button.
  8. Click the Migrate tab.
  9. Select the source configuration and destination configuration.
  10. Click the Migrate button.