Page Comparison

...

• JDK 1.6 update 21 or later (JDK 1.7 is not supported as of 2012/04)
  • http://java.sun.com (openjdk works as well)
• Tomcat 6.X (Tomcat 7 is not supported as of 2012/04)
  • Download source, http://tomcat.apache.org
    • On Unix:
      • Tomcat is available in the package manager of most linux distributions.
      • Install it according to the distribution's instructions.
        • Ubuntu - https://help.ubuntu.com/11.10/serverguide/C/tomcat.html
    • On Mac:
      • Tomcat is available via the homebrew package manager or
      • Download at: http://tomcat.apache.org/download-60.cgi
    • On Windows:
      • Tomcat is available as a download at: http://tomcat.apache.org/download-60.cgi
• PostgreSQL 8 or later (9.1 is recommended and used for development and testing)or Microsoft SQL Server 2008 or newer
  
  • PostgreSQL
    
    • Download source http://www.postgresql.org
      • On Unix:
        • PostgreSQL is available in the package manager of most linux distributions.
        • Install it according to the distribution's instructions
        • Ubuntu - https://help.ubuntu.com/11.10/serverguide/C/postgresql.html
      • On Mac:
        • PostgreSQL is available via the homebrew package manager or as a download on the postgresql.org site.
      • On Windows:
        • PostgreSQL is available as a download on the postgresql.org site.

    • Configure PostgreSQL

      • Connect via pgadmin or your preferred db admin tool

      • Create the "ssp" & "sspadmin" users and the "ssp" database.

  • Microsoft SQL Server 2008 or newer
    • JDBC Driver
      • Download the Microsoft SQL Server JDBC driver from http://msdn.microsoft.com/en-us/sqlserver/aa937724.aspx
      • Rename the downloaded file extension from .exe to .zip. Unzip the sqlserver-jdbc4-3.0.jar file to a directory of your choice.
      • Follow the install instructions as specified in the driver package.
    • Server Connection
      • Launch the SQL Server Management Studio application
      • Enter your database connection info including administrator account credentials, and click Connect
    • Login Roles
      • Navigate to Security->Logins, and right click on New Login
        

        • Login name of "sspadmin" without the quotes

        • Select SQL Server authentication and enter a Password of "sspadmin" without the quotes

        • Uncheck Enforce password policy

        • Click OK

      • Right click on Logins again, and New Login Role

        • Login name of "ssp" without the quotes

        • Select SQL Server authentication and enter a Password of "ssp" without the quotes

        • Uncheck Enforce password policy

        • Click OK

      • Confirm the new users exist
    • Database
      • Navigate to and right click on Databases and click New Database
        • Enter "ssp" without the quotes as the database name
        • Click OK
      • Confirm the new database exists
      • Run the following SQL to associate the new user accounts with the correct permissions on the new database:

        • USE [ssp]
          GO
          IF NOT EXISTS (SELECT name FROM sys.filegroups WHERE is_default=1 AND name = N'PRIMARY') ALTER DATABASE [ssp] MODIFY FILEGROUP [PRIMARY] DEFAULT
          GO
          IF NOT EXISTS (SELECT name  FROM sys.database_principals WHERE name = 'ssp')
          BEGIN
          CREATE USER [ssp] FOR LOGIN [ssp]
          EXEC sp_addrolemember N'db_datawriter', N'ssp'
          EXEC sp_addrolemember N'db_datareader', N'ssp'
          END
          GO
          CREATE USER [sspadmin] FOR LOGIN [sspadmin]
          GO
          EXEC sp_addrolemember N'db_owner', N'sspadmin'
          GO

...

• Update the configuration files on Unix/Mac/Windows:

  • Copy the SSP source files in src/main/config/external to /usr/local/etc/ssp or C:\ssp (depending on the environment)

  • Review each file carefully to set the appropriate settings.

    • ssp-config.properties: database connectivity, users and database
    • • Unique identifier of the SSP instance
        
        • system_id
      • Values for connecting to the SSP database
        
        • db_url: jdbc connection syntax
          • For Microsoft SQL Server, either specify a port (the default is 1433) or ensure that the SQL Server Browser service is running because the SQL Server JDBC driver defaults to port 1434 which is the SQL Server Server Browser service default port. Depending on the server configuration, either may work, or you may want to explicitly specify the port and instance name, if applicable.
        • db_driver_class: jdbc database connectivity syntax
        • db_dialect: Spring Hibernate dialect
        • db_username
        • db_password
        • db_admin_username
        • db_admin_password
      • Values for SSP generated emails
        
        • smtp_username
        • smtp_password
        • smtp_host
        • smtp_port
        • ssp_admins_email_addresses: recipient of system generated messages
      • Deployment options
        
        • spring.profiles.active
          • dev-standalone: completely free of uPortal
          • standalone: as the only portlet in a uPortal instance
          • uPortal: as one of many portlets in a uPortal instance
    • logback.xml: properties file location
      • Example: <property file="/usr/local/etc/ssp/ssp-config.properties" /> )

• Add the following environment variables to your system, and point them to the appropriate external configuration path:

  • On Unix/Mac:

    • SSP_CONFIGDIR=/usr/local/etc/ssp

  • On Windows:

    • SSP_CONFIGDIR=C:\ssp

  Tip
  title Additional Information
  Optional environment and configuration parameters are defined in the Developer Environment Setup Instructions

...