5.1.4 Install StarterKit
To install the starterkit:
- Create a directory and copy the generated starterkit zip file and unzip it.
- mkdir -p <dir_name>
                     Example:mkdir -p starterKit
- Copy the downloaded starterkit zip file into the created directory.
- cd <dir_name>
                     cd starterKit
- unzip <starterKitzipfilename>
                     Example:unzip starterKit_cappsalm10dec-prd_20.zip
- Assign EXECUTE permission installer script using the command:
                     chmod 755 *
- rm <starterKitzipfilename>
                     Example:rm starterKit_cappsalm10dec-prd_20.zip
Ensure that the path specified in $STARTER_KIT_HOME exists.If it doesn’t exist create the STARTER_KIT_HOME directory.STARTER_KIT_HOME is the same as what is mentioned in .profile in the Pre-installation Checklist section.
mkdir -p <starterkithome>
Example:mkdir -p shome
Edit the initParam.props file present inside starterKit/attributes folder.
Table 5-2 initParam.props file
| Parameter Name | Parameter Desc | 
| HOST | Schema name where starterkit is installed.Same schema which was created in section Assign Grants for Schema | 
| DB_HOST | Database Host name | 
| DB_PORT | Database Port number | 
| DB_SERVICE_NAME | Database Service Name or SID | 
| LOG_PATH | ABSOLUTE Log path where log files should reside | 
| EXTRACTOR_DUMP_HOME | ABSOLUTE Extractor Dump Home Folder path where export dump and import dump resides | 
| EXP_DUMP | Extractor Export Dump Folder name Where extracted scripts reside. Note:Values are defaulted and should not be changed. | 
| PAR_HOME | ABSOLUTE PAR Home path | 
| MANIFEST_FSAPPS_CREATE_SCRIPTS | Name of manifest file create scripts
                                deployment Note:Values are defaulted and should not be changed. | 
| MANIFEST_FSAPPS_INSERT_SCRIPTS | Name of manifest file insert scripts
                                deployment Note:Values are defaulted and should not be changed. | 
| IMP_DUMP | Extractor Import Dump Folder name Note:Values are defaulted and should not be changed. | 
Sample initParam.props file
#Enter HOME Schema name
HOST=custom
#Enter DB Host name
DB_HOST=<DB HOST IP ADDRESS>
#Enter DB Port number
DB_PORT=<DB PORT NUMBER>
#Enter DB Service Name or SID
DB_SERVICE_NAME=NXG19PDB
#Provide ABSOLUTE Log path
LOG_PATH=/scratch/iutusrext/shome/logs
#Sleep param value
SLEEP_VAL=sleep 3
#Provide ABSOLUTE Extractor Dump Home Folder path
EXTRACTOR_DUMP_HOME=/scratch/iutusrext/objExtDump
#Extractor Export Dump Folder name
EXP_DUMP=expDump
#Extractor Import Dump Folder name
IMP_DUMP=impDump
#Provide ABSOLUTE PAR Home path
PAR_HOME=/scratch/iutusrext/parDump
#Manifest fsapps for create scripts deployment
MANIFEST_FSAPPS_CREATE_SCRIPTS=manifest_fsapps_create.sql
#Manifest fsapps for insert DML scripts deployment
MANIFEST_FSAPPS_INSERT_SCRIPTS=manifest_fsapps_insert.sqlInstallation of starter kit
Go to the starterKit directory.
- Run the command to invoke setup.sh as follows:
                        . ./setup.shDuring its run this shell prompts you to enter the username, password, etc. of the database in which the Starter Kit files are to be deployed. Please provide them carefully. 
- Verify the execution status by running the following
                            query:
                        select * from setup_infoCheck the column F_STATUS for value S (Success). In case of failure, this column will be updated with value F (Failed). Additionally, verify the starterkit.logfile. The log path is mentioned in the properties file against the LOG_PATH parameter.