Rebrand Sterling File Gateway, myFileGateway, and myFileGateway2.0 UI in Certified Container Deployment

You can rebrand Sterling File Gateway, myFileGateway, and myFileGateway2.0 to use your company's logo or other special content in a Certified Container deployment by extending the Sterling B2B Integrator/Sterling File Gateway images by following the steps below.

Procedure

  1. Download the filegateway skins folder FileGateway_v001.zip and unzip it.
  2. Download the myfilegateway skins folder myFileGateway_v001.zip and unzip it.
  3. Download the folder assets.zip for myfg2.0 customization and unzip it.
  4. In the working directory, which will serve as the build context directory, create the following directories:
    • filegateway
    • myfilegateway
    • myfg20
  5. Create a Docker file in your docker build context directory as mentioned below:
    FROM  <Image>:<Tag>
    USER root
    COPY --chown=1010:0 ./filegateway /ibm/b2bi/install/container/Applications/tmp_filegateway/isomorphic/skins/
    RUN if [ "$(ls -A /ibm/b2bi/install/container/Applications/tmp_filegateway/isomorphic/skins/)" ]; then echo "Applying branding changes for filegateway" \
        && cd /ibm/b2bi/install/container/Applications/tmp_filegateway \
        && /ibm/b2bi/install/jdk/bin/jar uvf /ibm/b2bi/install/container/Applications/filegateway.war * \
        && cp /ibm/b2bi/install/container/Applications/filegateway.war /ibm/b2bi/install/noapp/deploy/filegateway.war \
        && rm -rf /ibm/b2bi/install/container/Applications/tmp_filegateway \
        && echo "Branding changes for filegateway applied successfully"; else echo "No branding changes provided for filegateway"; fi
    
    COPY --chown=1010:0 ./myfilegateway /ibm/b2bi/install/container/Applications/tmp_myfilegateway/isomorphic/skins/
    RUN if [ "$(ls -A /ibm/b2bi/install/container/Applications/tmp_myfilegateway/isomorphic/skins/)" ]; then echo "Applying branding changes for myfilegateway" \
        && cd /ibm/b2bi/install/container/Applications/tmp_myfilegateway \
        && /ibm/b2bi/install/jdk/bin/jar uvf /ibm/b2bi/install/container/Applications/myfilegateway.war * \
        && cp /ibm/b2bi/install/container/Applications/myfilegateway.war /ibm/b2bi/install/noapp/deploy/myfilegateway.war \
        && rm -rf /ibm/b2bi/install/container/Applications/tmp_myfilegateway \
        && echo "Branding changes for myfilegateway applied successfully"; else echo "No branding changes provided for myfilegateway"; fi
    
    COPY --chown=1010:0 ./myfg20 /ibm/b2bi/install/container/Applications/tmp_myfg20/
    RUN if [ "$(ls -A /ibm/b2bi/install/container/Applications/tmp_myfg20)" ]; then echo "Applying branding changes for myfg2.0" \
        && cd /ibm/b2bi/install/container/Applications/tmp_myfg20/ \
        && /ibm/b2bi/install/jdk/bin/jar uvf /ibm/b2bi/install/container/Applications/myfg.war * \
        && cp /ibm/b2bi/install/container/Applications/myfg.war /ibm/b2bi/install/noapp/deploy/myfg.war \
        && rm -rf /ibm/b2bi/install/container/Applications/tmp_myfg20 \
        && echo "Branding changes for myfg2.0 applied successfully"; else echo "No branding changes provided for myfg2.0"; fi
    
    USER 1010
    
  6. Update the <Image> and <Tag> in the above Docker file with the base B2BI/SFG image details.
  7. Copy the folders you downloaded as per steps 1 to 3 to their respective directories created as per step 4 and rename the skin folder (FileGateway_vXXX) with an appropriate version number, for example FileGateway_v002. The folder structure should be as mentioned below:
    • DockerFile
    • filegateway
      • FileGateway_vXXX
    • myfilegateway
      • FileGateway_vXXX
    • myfg20
      • assets
  8. Update the respective application skins folder with the required branding changes for filegateway/myfilegateway/myfg20. For rebranding FileGateway and myFileGateway, refer to Rebrand Sterling File Gateway and myFileGateway in IIM Deployment and for rebranding myFileGateway 2.0, refer to UI Branding in myFileGateway 2.0.
  9. Additionally, in the filegateway and myFileGateway directories, update line 13 in the files filegateway/FileGateway_vXXX/brandingcontent/header.txt and myfilegateway/FileGateway_vXXX/brandingcontent/myFgHeader.txt to include the skins folder version as shown below:
    </td>
    <td id="ibm-banner-logo" width="49"><img src="isomorphic/skins/FileGateway_vXXX/images/FGimages/brandingimages/ibm-logo-white.gif" width="41" height="15" alt="IBM logo"/></td>
    </tr>
  10. Extend the image using the following docker build command:
    docker build . -t <Image>:<newTag>
  11. Configure and use the new image tag for Certified Container deployment.
  12. Update the skins folder version for File Gateway and myFileGateway using customer_overrides from customization UI.
    • filegateway_ui.fgSkinName= fileGateway_vXXX
    • filegateway_ui.myfgSkinName= fileGateway_vXXX