Installation Guide. Version 2.1. on Oracle Java Cloud Service

Transcription

1 Installation Guide on Oracle Java Cloud Service Version

2 1 Preface This installation guide provides instructions for installing FlexDeploy on the Oracle Java Cloud Service. For on-premise installation instructions see the FlexDeploy Installation Guide. 2 Prerequisites You must have available credits for the following Oracle Cloud Services: Oracle Java Cloud Service Oracle Database Cloud Service Oracle Compute Cloud Service Oracle Storage Cloud Service 3 Creating an Oracle Database Cloud Service Instance You can create an Oracle Database Cloud Service instance by following the instructions located here: an_instance/obe_dbaas_creating_an_instance.html Note that FlexDeploy supports all database release versions and editions which are supported by the Oracle Database Cloud Service: Oracle Database 11g Release 2 (Standard or Enterprise) Oracle Database 12c Release 1 (Enterprise) 4 Creating an Oracle Java Cloud Service Instance You can create an Oracle Database Cloud Service instance by following the instructions located here: nce_create_instance/create_jcs_coherence_instance.html The following FlexDeploy specification should be used when creating the Java Cloud Service instance: Required WebLogic version: WebLogic Server 12c ( ) (Standard or Enterprise) Coherence is not required FlexDeploy only supports a single node cluster

3 Required Compute Shape depends on usage, but OC3 1 OCPU, 7.5 GB RAM is sufficient for most customers. 5 Database Schema Installation FlexDeploy has an Oracle database component, which is composed of schemas, users, and DDL to create its datastore. 5.1 Installation Instructions To download install and setup scripts, go to support.flexagon.com Navigate to Solutions tab - Software Downloads - FlexDeploy 2.1 Downloads Click on Oracle Database Install Scripts, which will download a zip file containing SQL scripts that can be run by a DBA. Extract the contents of zip file to a directory of choice. Transfer the.sql files to the Oracle Database Cloud Service VM and run the following SQL scripts using sqlplus. o CreateFlexDeploySchemas.sql <password> Pass one parameter to the script which is the password for the FD, FD_ADMIN and FF users that will be created with the execution of the script. o LoadFlexDeployMasterData.sql Alternatively, you can open an SSH tunnel to forward the SQL Net traffic on the VM, and use SQL Developer to run the statements within the scripts directly. See /JCS_SSH_Tunnel/SSH_Tunneling.html for instructions on establishing an SSH tunnel using PuTTy). 6 FlexDeploy Server Setup 6.1 Server Working Directory FlexDeploy uses a working directory for temporary files to be transferred between the server and its endpoints. This directory needs to available on the FlexDeploy Server. The endpoint will also have a separate working directory Requirements A storage volume (at least 1 GB) mounted on the Java Cloud Service instance hosting FlexDeploy

4 6.1.2 Setup Oracle does not supported creating application data under the /u01 mount point. Therefore, you must create a separate storage volume, attach it to your Java Cloud Service instance, and mount a directory to the underlying disk. See for instructions. Availability of space within the server working directory is critical to functioning of the FlexDeploy platform. Therefore it is highly recommended to have a file system size monitor in place for this directory and its size should be adjusted appropriately. 6.2 Artifact Repository The FlexDeploy artifact repository is a file system location on the FlexDeploy server where all build artifacts are stored and later retrieved for the deployments. You must create a directory on the FlexDeploy server for this purpose Requirements A storage volume (at least 4 GB) mounted on the Java Cloud Service instance hosting FlexDeploy Setup Oracle does not supported creating application data under the /u01 mount point. Therefore, you must create a separate storage volume, attach it to your Java Cloud Service instance, and mount a directory to the underlying disk. See for instructions. Due to the importance of the artifact repository, this file system should be backed up regularly. Availability of space within Artifact Repository is critical to the creation of new build versions. Therefore it is highly recommended to have a file system size monitor in place for this directory, and size should be adjusted based on the number of builds that occur and the size of the artifacts produced. 6.3 WebLogic Configuration General Setup Configure a WebLogic Cluster, Managed Server and Data Source as described in the following steps. Login into WebLogic Administration Console - 4 -

5 o host>/<adminserver port>/console Review the WebLogic Cluster and Managed Server for the Java Cloud Service instance. o For the purpose of these instructions let s assume your cluster is named FLEXDEPLOY_cluster and FLEXDEPLOY_server_1. These objects will be named according to the Java Cloud Service instance, but the preceding names will be referenced in the remainder of this section. o Click on the FLEXDEPLOY_server_1 server. From the Configuration tab, and the Server Start sub-tab, enter the following values in the Arguments section. -verbose:gc -Xms1024m -Xmx1024m -Dflexagon.fd.install.root=<FlexDeploy install root> -Dflexagon.fd.repository.root=<FlexDeploy repository root> NOTE: be careful in copying arguments due to potential character changes. 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. Create the Data Source o Go to Services(left pane) - Data Sources - New (GridLink Data Source) o Set following values, then click Next Name: flexdb JNDI Name: jdbc/flexdbds o Select Database Driver as Oracle s Driver (Thin XA) for GridLink Connections Versions Any, then click Next. o Click Next. o Select Enter complete JDBC URL, then click Next. o Set following values, then click Next. 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) o Test the configuration, then click Next. o Click Next o Click Next o Select to associate the datasource to the managed server or cluster in your Java Cloud Service instance, and click Finsih o Adjust the Maximum Capacity of the data source Click on the newly created data source under Services - Data Sources Click on flexdb. Change Maximum Capacity to 100. Click Save. Setup Logger Configurations. o Download following files from support.flexagon.com. FDWLSLogHandler.jar logging.xml o Copy the FDWLSLogHandler.jar to the lib folder of the domain

6 o Copy the logging.xml file to the config/fmwconfig/servers/flexdeploy_server_1. This step must be performed on the admin server domain if the WebLogic installation followed the Enterprise Deployment Guide (EDG). Recycle FLEXDEPLOY_server_ EAR Installation To download the WebLogic EAR file, go to support.flexagon.com Navigate to Solutions tab - Software Downloads - FlexDeploy 2.1 Downloads Click on Link named WebLogic (requires ) to download EAR file for WebLogic. After download is completed. Shutdown FlexDeploy_Server1. o Go to Environment (left pane) - Servers o Click on Control tab. o Check FlexDeploy_Server1. o Click Shutdown - Force Shutdown Now. o Wait for server to completely shut down. Install EAR file. o Go to Deployments(left pane) o If the FlexDeploy-WLS EAR is already deployed, stop it, and delete it. o Click Install Click on upload your file(s) link (in the middle of the note). Click Choose File and search for the downloaded ear on your system. Ensure the Path textbox matches the ear to install and click Next. Select Install this deployment as an application and click Next. Select the appropriate server under the cluster and click Next. Click Finish. Start FLEXDEPLOY_server_1. o Go to Environment (left pane) Servers. o Click on Control tab. o Check FLEXDEPLOY_server_1. o Click Start. o Wait for server to completely start. Start the FlexDeploy-WLS application. Ensure that the FlexDeploy-WLS application is active. 7 Endpoints An Endpoint is a target server where FlexDeploy can perform build or deploy activities. Endpoints are configured within the FlexDeploy UI (See FlexDeploy User s Guide for more information)

7 7.1 Requirements JDK version 1.6 or higher Disk space on each endpoint of 1GB 7.2 Setup Make sure JDK 1.6 or higher is installed. Setup working directory folder for Endpoint with initial size of at least 1GB. See note below if EndPoint is a Java Cloud Service instance. The files are transient in nature and will be purged by FlexDeploy after 3 days. The actual size of the directory will depend on the number of projects and deployments, but 1GB is a good starting point. It is highly recommended to have a file system size monitor in place for this directory, and size should be adjusted as necessary. As this file system contains only temporary files, there is no reason to backup this directory. Local disk storage is preferable, but a shared file system can be used. Note: Oracle does not supported creating application data under the /u01 mount point. Therefore, you must create a separate storage volume, attach it to your Java Cloud Service instance, and mount a directory to the underlying disk. See for instructions