Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added Sencha SDK tools to the required software for developers

...

  1. Software Prerequisites (JDK, Tomcat, Maven, Ant, Sencha SDK Tools, RDBMS)
  2. SSP Open Source Project build and deployment
  3. SSP Platform build and deployment

...

  • Maven 3.0.3 or later
    • Download Loation: http://maven.apache.org
    • Environment Variable: MAVEN_HOME

      Tip
      titleMaven Environment Variables
      MAVEN_HOME= /path/to/your/maven (ie: /usr/local/maven or C:\tools\maven)
      M2_HOME= /path/to/your/maven (ie: /usr/local/maven or C:\tools\maven)

      (optional)
      PATH= append the bin subdirectory to the path statement
  • Ant 1.8.2 (use this exact version)
    • Download Location: http://ant.apache.org

    • Environment Variable: ANT_HOME

      Tip
      titleAnt Environment Variable
      ANT_HOME= /path/to/your/ant (ie: /usr/local/ant or C:\tools\ant)

      (optional)
      PATH= append the bin subdirectory to the path statement
  • Sencha SDK Tools (current version 2.0.0.0 beta 3
    • Download Location: http://www.sencha.com/products/sdk-tools/download/
    • Environment Variable not required, but helpful in adding to path
    • Windows x64 users will also need to install a 32-bit Java SDK/JRE for the sencha build command to work properly (one of the jars in sencha looks for the 32-bit runtime and won't play nicely with the 64-bit SDK/JRE.)

       

      Tip
      titleSencha SDK Tools

      PATH= append the Sencha SDK Tools installation directory (not the bin)

  • RDBMS (support for PostgreSQL and Microsoft SQL Server)
    • PostgreSQL 9.1 or later
      • Download Location: http://www.postgresql.org
        • On Unix:
        • 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
        • Server Connection
          • Launch the PG Admin application
          • In the Object Browser, navigate to and right click on Server Groups -> Servers -> PostgreSQL 9.1 (localhost:5432)
          • Click Connect and the enter the administrator password
        • Login Roles
          • In the Object Browser, right click on Login Roles and click New Login Role
            • In the Properties tab, enter a Role name of "sspadmin" without the quotes

            • In the Definition tab, enter a Password of "sspadmin" without the quotes

          • In the Object Browser, right click on Login Roles and click New Login Role


            • In the Properties tab, enter a Role name of "ssp" without the quotes

            • In the Definition tab, enter a Password of "ssp" without the quotes

          • Confirm the new Login Roles exist in the Object Browser
        • Database
          • In the Object Browser, right click on Databases and click New Database
            • Enter "ssp" without the quotes as the database name
            • Enter "sspadmin" without the quotes as the database owner
          • Confirm the new database exists in the Object Browser
    • Microsoft SQL Server 2005 or 2008 R2
      • 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 quote
          • Uncheck Enforce password policy
        • 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 quote
          • Uncheck Enforce password policy
        • 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
        • Confirm the new database exists
    • Run the following SQL to assign user permissions and configure the required database settings

       

      Code Block
      titleSQL Server Configurations
      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
      

       

       

      Code Block
      For MSSQL 2005:
      
      ALTER DATABASE ssp
       SET ALLOW_SNAPSHOT_ISOLATION ON;
       SET TRANSACTION ISOLATION LEVEL SNAPSHOT
      ALTER DATABASE ssp
       SET READ_COMMITTED_SNAPSHOT ON;
       SET TRANSACTION ISOLATION LEVEL READ COMMITTED
      
      For MSSQL 2008 or later:
      
      ALTER DATABASE ssp
       SET ALLOW_SNAPSHOT_ISOLATION ON
      ALTER DATABASE ssp
       SET READ_COMMITTED_SNAPSHOT ON

...