Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Login into the WebLogic Administration Console
    • http://<adminserver host>:<adminserver port>/console
  • Lock console for Edit if necessary.
  • Click on the FlexDeploy_Server1 server.

  • From the Configuration tab, and the Server Start sub-tab, enter the following values in the Arguments section as per Operating System.

  • Make sure to Click Save and

  • Activate Changes if necessary.

    Code Block
    languagebash
    themeRDark
    titleJVM arguments (Unix)
    -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


    Code Block
    languagepowershell
    themeRDark
    titleJVM arguments (Windows)
    -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xms1024m -Xmx2048m -Dflexagon.fd.install.root=c:/flexdeploy/application -Dflexagon.fd.repository.root=c:/flexdeploy/repository -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.mds.cache=simple -Djava.awt.headless=true  -DUseSunHttpHandler=true


    Info

    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 from browser due to potential character changes.


...

  • Login into the WebLogic Administration Console
    • http://<adminserver host>:<adminserver port>/console
  • Lock console for Edit if necessary.
  • 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.
  • Activate Changes if necessary.

Setup Logger Configurations

...

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

  • Login into the WebLogic Administration Console
    • http://<adminserver host>:<adminserver port>/console
  • Shutdown the FlexDeploy_Server1 managed server if it is Running.
    • 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
  • Lock console for Edit if necessary.
  • 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 Click Install
      • For installation of EAR we can either use copy or upload option
        • Copy option
          • Copy downloaded FlexDeploy EAR downloaded FlexDeploy-WLS.ear file to <Domain Home>/applications folder on AdminServer host.
          • 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 -WLS.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 (FlexDeploy_Server1) under the cluster and click Next
      • Click Finish.
  • Activate Changes Setup to automatic upload of Pluginsif necessary.

Copy Plugins for Auto upload

At startup, FlexDeploy will upload and activate all the plugins.

...

See 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 FlexDeploy Server

  • Login into the WebLogic Administration Console
    • http://<adminserver host>:<adminserver port>/console
  • 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 FlexDeploy-WLS application.
  • Plugins copied in previous steps should load automatically upload and activate in few minutes.

Launch FlexDeploy

  • Launch FlexDeploy in browser when managed server is Running. http://<host>:<port>/flexdeploy
  • Default credentials
    • user - fdadmin
    • password - welcome1
  • Please visit Administration - Plugins to view progress and eventually there should not be any jar files left in FLEXDEPLOY_WORKING_DIR/plugins.

...