Installation for Weblogic

FlexDeploy is a J2EE application which may be installed on WebLogic or Tomcat application servers.

Requirements

  • WebLogic 12.1.3 including JRF 12.1.3 (See WebLogic 12.1.3 Installation Scripts for installation and configuration of WebLogic 12.1.3 domain). It is very important that ADF(JRF) is also part of WebLogic installation for FlexDeploy.
  • 8GB of RAM
  • 1 CPU
  • JDK 1.7.0+ (for additional certifications, see 12.1.3 Certification Matrix)
  • FlexDeploy Working Directory and Artifact Repository folders are created.

WebLogic Setup

Install and Domain setup

Install WebLogic 12.1.3 including JRF 12.1.3. For help creating a new installation, see WebLogic 12.1.3 Installation Scripts. We recommend that you follow WebLogic 12.1.3 Installation Scripts to save time spent in installation process.

After installing WebLogic with JRF, Creation of Domain, Configure a WebLogic Managed Server and Data Source as described in the following steps.

Create and Configure FlexDeploy Managed Server

  • Login into the WebLogic Administration Console
    • http://<adminserver host>/<adminserver port>/console
  • Create a WebLogic Cluster and Managed Server for installation of the FlexDeploy EAR file. You can skip this step if you already created the server using the provided scripts WebLogic 12.1.3 Installation Scripts, which would have created managed server.
    • For the purpose of these instruction let's assume you named the cluster FlexDeploy_Cluster, and the managed server FlexDeploy_Server1. You can name the cluster and managed server as you please but the preceding names will be referenced in the remainder of this section.

      Make sure to apply JRF Template on WebLogic Managed Server (FlexDeploy_Server1). FlexDeploy must be installed on only one Managed Server, so do not create more than one Managed Server.

  • Click on the FlexDeploy_Server1 server. From the Configuration tab, and the Server Start sub-tab, enter the following values in the Arguments section.

    JVM arguments
    -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xms1024m -Xmx2048m -Dflexagon.fd.install.root=/opt/flexdeploy/application -Dflexagon.fd.repository.root=/opt/flexdeploy/repository -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.mds.cache=simple -Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom -DUseSunHttpHandler=true

    Please make sure to modify the arguments for Server working directory (-Dflexagon.fd.install.root) and Artifacts repository (-Dflexagon.fd.repository.root) as per your installation. Be careful in copying arguments due to potential character changes.

  • Create the Data Source
    • Go to Services(left pane) - Data Sources - New (Generic Data Source for on-premise and GridLink Data Source for Cloud Based)
    • Set following values, then click Next
      • Name: flexdb
      • JNDI Name: jdbc/flexdbDS
      • Database Type: Oracle
    • Select Database Driver per the platform installation:
      • for on-premise use Oracle's Driver (Thin) for Instance Connections: Versions Any, then click Next.
      • for Cloud based use Oracle's Driver (Thin) for GridLink Connections: Versions Any, then click Next.
      • Do not use XA DataSource for this purpose.
    • Leave transaction information as default, then click Next.
    • Set following values, then click Next.
      • for on premise use:
        • Database Name: ORCL, XE or custom database name
        • Host Name: IP address or DNS name of database server
      • for Cloud Based use:
        • Complete JDBC URL: The connect descriptor from the Database Cloud Service instance attached to your Java Cloud Service instance
      • Database User Name: fd_admin
      • Password: <password for fd_admin> (password was setup when running Database schema setup in previous step)
    • Test the configuration, then click Next.
    • Select the cluster to associate the data source to (FlexDeploy_Cluster), then click Finish.
    • Adjust the Maximum Capacity of the data source
      • Click on the newly created data source under Services - Data Sources
      • Click on flexdb
      • Click on Configuration tab, and then Connection Pool sub-tab
      • Change Maximum Capacity to 100.
      • Click Save.
  • Setup Logger Configurations.
    • From the extracted zip directory, navigate to the WebLogic directory and locate these files:
      • FDWLSLogHandler.jar
      • logging.xml
    • Copy the FDWLSLogHandler.jar to the lib sub-directory of the domain.
    • Copy the logging.xml file to the config/fmwconfig/servers/FlexDeploy_Server1 subdirectory of the WebLogic domain. This step must be performed on the admin server domain if the WebLogic installation followed the Enterprise Deployment Guide (EDG).
  • If using IBM ClearCase, you will need to copy some jar files from your ClearCase server or ClearTeam Explorer installation into <DOMAIN_HOME>/lib

    • Copy all jar files found in the com.ibm.rational.teamapi_8.0.1.vxxx folder of your ClearCase server or ClearTeam Explorer installation to <DOMAIN_HOME>/lib folder. (commons-codec-1.3.jar, commons-lang-2.3.jar, icu4j-4_8.jar, remote_core.jar, stpclientws.jar, stpcq.jar, teamapiextensions.jar, unicodetypemgr.jar, commons-httpclient-3.0.jar, commons-logging-1.0.4.jar, icu4j-charset-4_8.jar, stpcc.jar, stpcmmn.jar, stpwvcm.jar, ucleardiffmerge.jar)
  • Recycle FlexDeploy_Server1.

EAR Installation

From the extracted zip directory navigate to the WebLogic sub-directory, locate the EAR file, and follow these instructions to install the EAR.

  • Shutdown the FlexDeploy_Server1 managed server
    • Go to the EnvironmentServers (left pane)
    • Click on the Control tab
    • Select the FlexDeploy_Server1 managed server
    • Click Shutdown - Force Shutdown Now
    • Wait for server to completely shut down
  • Install EAR file
    • Go to Deployments (left pane)
    • If FlexDeploy_WebLogic_[version] is already installed, uninstall it.
      • If your domain is using Production mode, click Lock and Edit first
      • Scroll down until the FlexDeploy ear is found (may be on next page)
      • Select the FlexDeploy_WebLogic_[version] and click Delete.
      • Activage Changes before next step.
    • If your domain is using Production mode, click Lock and Edit first
    • Click Install
      • We need to transfer downloaded FlexDeploy EAR to AdminServer for installation, use either copy or upload option
        • Copy option
          • Copy downloaded FlexDeploy EAR file to <Domain Home>/applications folder
          • Use Path input box or Recently Used Paths links to navigate to copied EAR file, then select EAR file and click Next.
        • Upload option
          • Click Upload your file(s) link (in the middle of the note)
          • Click the Choose File button
          • Select downloaded FlexDeploy EAR from your computer
          • Click Open
          • When upload completes, newly uploaded FlexDeploy EAR File should already be listed in Path, Click Next
      • Select Install this deployment as an application and click Next
      • Select the appropriate server under the cluster and click Next
      • Click Finish.
      • Activate Changes
  • Setup to automatic upload of Plugins
    • At startup, FlexDeploy will upload and activate all the plugins.
    • As per details provided in Loading FlexDeploy Plugins, create a folder called plugins inside your FlexDeploy working directory. Move or copy all the jar files from <WebLogic Complete Zip>/plugins to FLEXDEPLOY_WORKING_DIR/plugins.
  • Start the FlexDeploy_Server1 managed server
    • Go to EnvironmentServers (left pane)
    • Click on Control tab
    • Select the FlexDeploy_Server1 managed serer
    • Click the Start button
    • Wait for server to completely start
  • Ensure that the application is active after deployment. If not active, please start the application.
  • Plugins copied in previous steps should load and activate. Please visit Administration - Plugins to view progress and eventually there should not be any jar files left in FLEXDEPLOY_WORKING_DIR/plugins.