FlexDeploy is a J2EE application which must be installed on either a WebLogic or GlassFish application server.
...
- WLS 12.1.3 including JRF 12.1.3 (See Appendix A)
- 4GB of RAM (this would be 7.5G for Cloud Based, lowest size available)
- 1 CPU
- JDK 1.7.0+ (for additional certifications, see 12.1.3 Certification Matrix)
WebLogic Setup
Install and Domain setup
Install WebLogic 12.1.3 including JRF 12.1.3. For simplicity, Appendix A covers the process of performing this install using WebLogic scripting.
After installing WebLogic with JRF, configure a WebLogic Cluster, 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.
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.
Info Make sure to apply JRF Template on WebLogic Managed Server (FlexDeploy_Server1)
Click on the FlexDeploy_Server1 server. From the Configuration tab, and the Server Start sub-tab, enter the following values in the Arguments section.
Code Block language text title JVM arguments -verbose:gc -Xms1024m -Xmx2048m -Dflexagon.fd.install.root=/opt/flexdeploy/application -Dflexagon.fd.repository.root=/opt/flexdeploy/repository -Doracle.jdbc.autoCommitSpecCompliant=false -Doracle.mds.cache=simple
| Info |
|---|
| The FlexDeploy install root(-Dflexagon.fd.install.root) and FlexDeploy repository root(-Dflexagon.fd.repository.root) values should be replaced by the directories created in Server Working Directory and Artifact Repository, respectively. |
| Warning |
|---|
| NOTE: 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 XA) for GridLink Connections: Versions Any, then click Next.
- 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)
- for on premise use:
- 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).
- From the extracted zip directory, navigate to the WebLogic directory and locate these files:
- Recycle FlexDeploy_Server1.
...