7.1 Creating and Deploying the Applications Pack Web Archive

This section describes how to create and deploy the Applications Pack Web Archive.

OFSBD Application Pack Deployment

To create and deploy the Applications Pack web archive, follow these steps:

  1. Navigate to the $FIC_WEB_HOME directory.
  2. Execute the command:
    ./ant.sh
    .
    This will trigger the creation of EAR/WAR file - <contextname>.<extn>. Here <contextname> is the context name given during installation.

    Note:

    Creating ear/war files are done by the installer automatically. If the files are not created, user can execute these steps.

    On completion of the EAR/WAR files creation, the "BUILD SUCCESSFUL" and "TimeTaken" message is displayed and you are returned to the prompt.

    The EAR/WAR file - <contextname>.<extn> - is created under the $FIC_WEB_HOME directory.

    Note:

    This process overwrites any existing version of EAR/WAR file in the path. If the web application server is Apache Tomcat, the file created would be <contextname>.war.
  3. Deploy the generated EAR/WAR file on to the web application server. For more information, see Deploying EAR/WAR File.

Scenario Wizard Configuration and Deployment

The Scenario Wizard Configuration and Deployment must be performed if the following applications are installed.:

  • AML
  • FR
  • Trade Compliance
  • Broker Compliance
  • Fraud-EE
  • ECTC
  • TB

To configure and deploy Scenario Wizard, follow these steps:

  1. Navigate to $FIC_HOME/ficweb/SCENARIO_WIZARD.
  2. Update the install.properties file for the below parameter, if those parameter values are not mentioned in the file

    Note:

    In case of the wallet setup, the automated configured value smlite.db.url=jdbc:oracle:thin:/@CONFIG in install.properties file need to be manually changed to JDBC URL value (jdbc:oracle:thin:@Hostname:port:SID/Service Name).
    • smlite.db.host=##HOSTNAME##
    • smlite.db.port=##PORT##
    • smlite.db.sid=##SID##
    • smlite.db.url=##URL##
    • ws.app.rmiport= ##RMI_PORT## #
    • Provide the deployment Path for Scenario Wizard - ws.sw.deploy.path=##DEPLOYED_PATH## /SMLiteWeb
  3. Execute ./install.sh. When prompted for password, enter the KDD MNR Schema password.
  4. Deploy the <context-name>.war file (for example, SMLiteWeb.war) available at $FIC_ HOME/ ficweb/SCENARIO_WIZARD as an application on your Web application server. While deploying war file, keep context name as SMLiteWeb.

    Note:

    Only one instance of Scenario Wizard will run on one Application server at a time. While launching the Scenario Wizard if you find any exception pop-up saying java.rmi.bind exception or java.rmi.unknownhost exception, follow these steps:
    1. Stop the SMLiteWeb.war file.
    2. Navigate to <deployed area>SMLiteWeb\WEB- INF\classes\conf\mantas_ cfg\install.cfg.
    3. In install.cfg, change the token to some other port, which is not occupied.
    4. Define rmiPort. By default keep it 1099rmiPort=1099.
    5. Restart the server.
  5. Log Details:
    1. Log file name - smlite.log.
    2. Log path - Navigate to <deployedarea>SMLiteWeb\WEB-INF\classes\logs\smlite.log.
  6. To customize the Log path/log file name, follow these steps:
    1. Go to <deployed area>\SMLiteWeb\WEB-INF\classes\log4j.properties file.
    2. Change the value of the property log4j.appender.file.File="Your log filepath".
    3. Restart the SMLiteWeb.war file.

To configure and deploy Scenario Wizard on Weblogic:

  1. Navigate to the domain/bin folder.
  2. Add the following two lines into filesetDomainEnv.sh.
    • FIC_HOME = “##DEPLOYED_AREA##/SMLiteWeb.
    • export FIC_HOME.

To configure and deploy Scenario Wizard on WebSphere, follow these steps:

  1. Ensure that port 1099 is free and available.
  2. Create a folder named SMLiteWeb.ear in the deploy path.
  3. In the Install.properties file, under the ws.sw.deploy.path enter:
    ##Deployment_path##/SMLiteWeb.ear/SMLiteWeb.war. For example: /scratch/ IBM/WebSphere/AppServer/profiles/BECS8124WS/installedApps/ofss-mum-889-Node3-Cell08/SMLiteWeb.ear/SMLiteWeb.war
  4. Generate the SMLiteWeb.war file and place this file in the SMLiteWeb.ear directory in the deploy path.
  5. Navigate to Servers à Server Types à WebSphere Application servers à Choose your server.
  6. Navigate to your chosen server à Server Infrastructure à Java and Process Management àClass Loader.
  7. Add new class loader and select Classes loaded with local class loader first (parentlast).
  8. Navigate to your chosen server à Server Infrastructure à Java and Process Management à Process Definition à Environment Entries.
  9. Add FIC_HOME as Name and ##Deployment_path##/SMLiteWeb.ear/SMLiteWeb.war as value.
  10. Navigate to Applications > Application Types > WebSphere Enterprise Applications > Install and choose the SMLiteWeb.war from the specified path.
  11. During installation, for Map context roots for web modules choose the values as /SMLiteWeb.
  12. Navigate to Applications à Application Types à WebSphere Enterprise Applications à SMLiteWeb.
  13. Click on SMLiteWeb à References à shared Library References à choose application SMLiteWeb.
  14. Add the share libraries by going into Reference shared Libraries à move the available libraries to selected (For example: JERSEY2X).
  15. Navigate to Applications à Application Types à WebSphere Enterprise Applications à SMLiteWeb.
  16. Click on SMLiteWeb à References à shared Library References à choose Module Apache-Axis.
  17. Add the share libraries by going into Reference shared Libraries à move the available libraries to selected (For example: JERSEY2X).
  18. Start the application. If the application is not accessible, stop and start the application again from the websphere console.
  19. If the Scenario Wizard is not accessible, restart the web and app server and start the application.

    Note:

    See Post Deployment Configuration for more details.

    For Front-end access, the following settings must be changed on the client side for the Scenario Wizard to work on Windows XP/ Windows 7.

    1. Navigate to Java Control Panel.
    2. Under the General tab ensure the following two settings:
      1. Navigate to Network Settings and change the Network Proxy Settings to Direct Connection.
      2. Navigate to Settings under Temporary Internet Files and follow these steps:
        • Check the option to keep temporary files on my computer.
        • For Scenario wizard, in WebSphere, the Java version must be the same in App and Web Server.
  20. Click Delete Files to clear the Java cache.
  21. To configure Scenario Wizard on Tomcat 8 and above before deploying the war file, follow these steps:
    1. Remove the following text from context.xml at <deployed area>/conf/: AbandonedOnBorrow="true"
    2. AbandonedOnMaintenance="true" AbandonedTimeout="60"logAbandoned="true"/>
    3. Replace with the text: maxTotal="100" maxIdle="30"maxWaitMillis="10000"/>
    4. All resources have been moved to Context.xml from server.xml.
    5. Change the following text:
      <Context path =
/admin_tools" docBase="<deployed_area>/webapps admin_tools" debug="0" reloadable="true" crossContext="true">
to <Context>

Services Configuration and Deployment