Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
API Portal is a multi-tenant-enabled application.The different tenants share the infrastructure of their installation, but have completely separated content.
In general, a dedicated schema needs to be created for each tenant. Since as we mentioned above each API Portal installation has at minimum not one but two tenants ("default" and "master"), you need to create at least two schemas, plus additional schemas for each additional tenant you want use on the installation.
SQL scripts and all additional files. All scripts and files can be downloaded from the ARIS Download Center (https://aris.softwareag.com/DownloadCenter). To download the SQL scripts register(https://aris.softwareag.com/DCRegisterUser) yourself with ARIS download center.
API Portal is internally based on ARIS infrastructure. The SQL scripts are published to aris download center using ARIS specific version numbers. Below table summarizes the portal version and its corresponding ARIS version.
@ECHO OFF REM REM You may edit this section for customizing purposes. REM REM If you use named instances then append a "\" and the name of your instance SET MSSQL_SAG_MSSQL_SERVER_NAME=localhost REM The login name that is used to execute this script SET MSSQL_SAG_MSSQL_LOGIN_NAME=localhost\username REM name of database that will be created by the script. SET MSSQL_SAG_DATABASE_NAME=ARIS9DB REM folder in which the database files should be stored. SET MSSQL_SAG_FILEGROUP_FILE_DIR=F:\msqldata\ARIS9DB REM credentials of the login that is used by the application. SET MSSQL_SAG_APP_USER=ARIS9 SET MSSQL_SAG_APP_PWD=*ARIS!1dm9n#
REM schema names for the default and master tenants SET MSSQL_SAG_TENANT_DEFAULT=ARIS_DEFAULT SET MSSQL_SAG_TENANT_MASTER=ARIS_MASTER
...