Custom Startup Extensions

The out of the box customization init image defines the below directory and file structure for custom startup extension with placeholder scripts which can then be updated by extending the image:

ibm
 b2bi
  customization
   startup
    pre-container-startup-extn.sh
    pre-app-startup-extn.sh
    post-app-startup-extn.sh

The startup extension scripts are plugged in at specific lifecycle hooks during application container startup and can be used to execute any custom commands inheriting the same security environment context of the enclosing application containers:

1. Pre-container-startup-extn.sh (Pre container startup) - This is executed as the first script during application container startup before any application logic or scripts are executed.
2. Pre-app-startup-extn.sh (Pre application startup) - This is executed before the application startup or runtime script - run.sh/startContainer.sh/startLiberty.sh - depending on the type of container.
3. Post-app-startup-extn.sh (Post application startup) - This is executed post the application startup script or runtime script - run.sh/startContainer.sh/startLiberty.sh - depending on the type of container.

The scripts inherit few global environment variables from the main container entrypoint script including:

• INSTALL_DIR - the application install directory. It can be used to access install sub-folders like bin or properties viz. $INSTALL_DIR/bin or $INSTALL_DIR/properties.
• SERVER_TYPE - indicates the server type based on the container - asi, ac or api. It can be used to execute scripts or commands for specific server types.