...
- 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 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:
- If using IBM ClearCase, you will need to copy the following jar files from your ClearCase server into <TOMCAT<DOMAIN_HOME>/lib
- The jar files can be located in the com.ibm.rational.teamapi_8.0.1.vxxx folder of your ClearCase server.
- If you will be using the Salesforce integration,
- Recycle FlexDeploy_Server1.
...
- Shutdown the FlexDeploy_Server1 managed server
- Go to the Environment – Servers (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.
- Active Changes before next step.
- If your domain is using Production mode, click Lock and Edit first
- Click InstallClick on upload
- We need to transfer downloaded FlexDeploy EAR to AdminServer
- You can either copy downloaded FlexDeploy EAR file to <Domain Home>/applications folder OR
- Use on Upload your file(s) link (in the middle of the note). Click Upload your file(s) link, then click the Choose File button, and select
- downloaded FlexDeploy EAR
- from your computer, click Open
- Select FlexDeploy EAR File then Click Next
- 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.
- Active Changes
- We need to transfer downloaded FlexDeploy EAR to AdminServer
- Start the FlexDeploy_Server1 managed server
- Go to Environment– Servers (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.
...