This chapter will guide you through an Oracle Business Process Management Suite Quick Start installation and introduce you to using the Integrated WebLogic Server's default domain or creating a standalone domain.
By the end of this chapter, you will be able to develop Oracle Business Process Management Suite applications using Oracle Business Process Management Studio (referred as Oracle JDeveloper throughout this guide). You will also be able to test those applications using the Integrated WebLogic Server and Java DB.
This chapter contains the following sections:
This section will help you verify that Quick Start can run on your system.
Before using Quick Start, you need to prepare your system for the installation by completing the following tasks:
Make sure that you are installing your product on supported hardware or software configuration. See the certification document for 12c (12.1.3) on the Oracle Fusion Middleware Supported System Configurations page.
Verify that your user account has the required privileges for installing Oracle Fusion Middleware. For more information, see "Selecting an Installation User" in Planning an Installation of Oracle Fusion Middleware.
Check the Oracle Fusion Middleware System Requirements and Specifications to see if your system meets the requirements for 12c (12.1.3).
Log into the host computer where you want to install Oracle Business Process Management Suite.
Refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme File to find and download the following files:
The Oracle Business Process Management Suite Quick Start installer zip file. This is located on the Oracle Software Delivery Cloud as part of the Oracle Fusion Middleware 12c Media Pack.
You can register an account and download software from the Oracle Software Delivery Cloud is located at the following URL:
If you cannot find the installer at the above location, verify the download location with the Oracle Fusion Middleware Download, Installation, and Configuration Readme File.
The latest supported Java Development Kit (JDK) for your operating system. As of its release, Oracle Fusion Middleware 12c (12.1.3) requires a minimum of JDK 7.0 Update 55 or later.
You can find the latest JDK at the following URL:
You should always verify the recommended version number and download location with the "Downloading a Supported Java Development Kit (JDK)" in the Oracle Fusion Middleware 12c (12.1.3) Download, Installation, and Configuration Readme File.
Install the JDK. The installation path must not contain any spaces.
You can find more information on installing a certified JDK under "Installing a Certified JDK" in Planning an Installation of Oracle Fusion Middleware.
Set the environment variable
JAVA_HOME to point to the location of your JDK. Note that
JAVA_HOME must be in all caps. Your path definition should look something like the following:
JAVA_HOME=$HOME/Java/jdk1.7.0_xx export JAVA_HOME
|Windows||Search for cmd.exe in the Start menu. Right-click the
SET JAVA_HOME="C:\Program Files\Java\jdk1.7.0_xx"
Your JDK folder may not be named the same or located at the destination in the above example. Make sure you point to the actual destination.
This section will help you launch the Quick Start installer.
After you have done all the items in Section 4.1, you can launch the Quick Start installer.
Unzip the contents into a location you can find easily. You may have several .jar files.
Using the command prompt, navigate to the directory where you unzipped the jar files. Launch the installation wizard with the appropriate command.
|Generic Installer for Linux||
JAVA_HOME/bin/java -jar fmw_126.96.36.199.0_bpm_quickstart.jar
|Generic Installer for Windows||
JAVA_HOME\bin\java.exe -jar fmw_188.8.131.52.0_bpm_quickstart.jar
Note:You can also launch the installer in silent mode to ensure that no configuration options are displayed during the installation process. For more information about silent or command line installation, see "Using the Oracle Universal Installer in Silent Mode" in Installing Software with the Oracle Universal Installer.
The installation wizard should launch. If you have any problems getting the installer to run, double-check your system preparations, covered in Section 4.1.
Note:Though you may have multiple jar files, you do not need to run the install command on all of them. You only need to run the above command on fmw_184.108.40.206.0_bpm_quickstart.jar.
This section will guide you through the Quick Start installation.
Once you have launched the Quick Start installer, the installation wizard displays the screens listed and described sequentially in Table 4-1.
This screen introduces you to the product installer.
Use this screen to specify the location of your Oracle home directory. Ensure that the name of the directory that you choose does not contain spaces.
For more information about Oracle Fusion Middleware directory structure, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware.
This screen verifies that your system meets the minimum necessary requirements.
Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation.
This screen allows you to see the progress of the installation.
This screen appears when the installation is complete. Review the information on this screen.
At the bottom of this screen, there is a checkbox to launch Oracle JDeveloper upon closing the installation wizard.
Description of the illustration ''startjdev.gif''
This guide recommends that you uncheck this box.
For more information about the installation screens, see "A Oracle Universal Installer Installation Screens" in Installing with Oracle Universal Installer.
See Section 4.4 to see how to prepare your environment for using JDeveloper. Then see Section 4.5 for the two supported methods of launching the Integrated WebLogic Server. You can find a tutorial for using the Integrated WebLogic Server to develop an application under Section 7.2.
This section explains how to prepare your environment before launching the Integrated WebLogic Server.
This section contains the following tasks:
JDEV_USER_DIR environment variable to define the location of your user home directory. This should be a unique location for your distribution. The user home directory will contain subdirectories for your domain files and your user-generated application files.
Note:This step is crucial if you are planning to install and run multiple distributions of JDeveloper on the same machine. Assign a unique user home directory for each distribution you install. See Section 4.7 for more information.
Oracle recommends a directory structure similar to the one shown in Figure 4-1, where
config shows the location of the user home directory.
If you do not define
JDEV_USER_DIR, your domain home and application home will be created at two different locations.
On an UNIX host, the default domain home will be created at
$HOME/.jdeveloper/system12.1.3.x.x.x.xxxx/DefaultDomain. The default application home will be created at
On a Windows host, the default domain home will be created at
%USERPROFILE%\AppData\Roaming\JDeveloper\system12.1.3.x.x.x.xxxx\DefaultDomain. Your default application home will be created at
Once you have defined
JDEV_USER_DIR, the domain home and application home will be co-located as subdirectories under the defined location. For example, on a UNIX system, the domain home will be located in
JDEV_USER_DIR\system12.1.3.x.x.x.xxx. The application home will be located in
You can also set
ORACLE_HOME. While this step is not necessary, it will simplify the process of navigating to the various directories when you are running installation and configuration commands.
The path definition should look something like this:
ORACLE_HOME=$HOME/Oracle/Middleware/Oracle_Home export ORACLE_HOME
If you are installing on an Oracle Linux (formally Oracle Enterprise Linux) machine, you should ensure that you have sufficient entropy. You need at least 500 for the Integrated WebLogic Server to start up in a timely manner.
To check for entropy, run the following command:
If you have less than 500, use the following command to replenish bytes to
/dev/urandom as the source:
rngd -r /dev/urandom -o /dev/random -b
You can configure this command by editing /etc/sysconfig/rngd and add the following line:
EXTRAOPTIONS="-i -r /dev/urandom -o /dev/random -b -t 60 -W 2048"
This section will help you configure a domain that uses Java DB.
Launching the Integrated WebLogic Server automatically generates a domain, designated as the default domain. However, you also have the option of launching the WebLogic server outside of JDeveloper and configuring a standalone domain.
The advantages and disadvantages of each domain is detailed in the following table. You should choose the domain configuration that best suits your end goals.
|Configure the Integrated WebLogic Server's default domain in JDeveloper.||Launching the Integrated WebLogic Server from inside JDeveloper will create the default domain.
In this case, the server is tethered to your current JDeveloper session. When you quit JDeveloper, the Integrated WebLogic Server shuts down as well. Every time you start a new JDeveloper session, you need to relaunch the Integrated WebLogic Server.
|See Section 4.5.1.|
|Configure a standalone domain.||You can create a standalone version of the Integrated WebLogic Server. The server and domain run independently of JDeveloper.
This will you save you startup time if you plan on developing an application in JDeveloper over a series of separate sessions, or if you plan to develop applications in the Oracle Service Bus browser-based console.
|See Section 4.5.2|
|Configure a compact domain.||You can configure your Quick Start installation to use an Oracle database with an external compact domain.
You should only choose this option if you know you want your domain to be compatible with Enterprise Scheduler, Managed File Transfer, B2B, Heathcare, or BAM components.
|See Chapter 5.|
Any other method of configuring a domain is not recommended.
This section explains how to configure JDeveloper's default domain by launching the Integrated WebLogic Server. You will complete the following tasks:
Launch JDeveloper with the following command:
cd $ORACLE_HOME/jdeveloper/jdev/bin ./jdev
CD %ORACLE_HOME%\jdeveloper jdeveloper.exe
As JDeveloper launches, you will get three prompts.
When prompted, select Studio Developer as your role and press OK.
When prompted, say No to import preferences from a previous JDeveloper installation.
When prompted about Oracle Usage Tracking, check whether or not you want Oracle JDeveloper to send automated usage reports to Oracle and press OK.
JDeveloper has fully launched at this point.
Launch the Integrated WebLogic Server by choosing Run from top menu bar. Select Start Server Instance from the drop-down menu, as seen in Figure 4-2.
The first time you launch the server instance, you will be prompted to enter a password for your default domain, as seen in Figure 4-3.
The Administrator ID, Listen Address, Listen Port, and SSL Listen Port should already have values. Review them and make any appropriate changes.
Launching the integrated server will take several minutes.
You can track the server's launch in the Messages window pane. This window should automatically open at the bottom of the JDeveloper screen. If it is not there, you can open it by selecting Window from the top bar menu and Log from the drop-down menu. You can also activate it with the keyboard shortcut
Note:If the creation of the Integrated WebLogic Server domain fails with the following error:
Failed to query contents of table SERVICETABLE. - Schema 'DEMODB' does not exist
Make sure to shut down all running servers, even if they are not using Java DB, and try the domain creation again.
VPN Issue:If your machine is connected through a VPN, Coherence may be confusing the local and VPN IP addresses. Change the Coherence cluster to multicast.
When you see the following messages appear in the log, the Integrated WebLogic Server has launched successfully.
[SOA Platform is running and accepting requests [IntegratedWebLogicServer started.]
Your default domain is already configured with Oracle SOA Suite and Oracle Business Process Management Suite runtime components. You should now verify your installation.
Access the Enterprise Manager Fusion Middleware Control, which is located at an URL following this format:
Note:The default port for the Integrated WebLogic Server should always be 7101 unless you changed it during configuration.
Log in using the username and password that you specified when launching the Integrated Weblogic Server.
For more information on using Fusion Middleware Control, see "Getting Started Using Oracle Enterprise Manager Fusion Middleware Control" in Administering Oracle Fusion Middleware
This is an optional task. SSL is enabled by default in the Integrated WebLogic Server. If you do not have stringent design time requirements, you can disable SSL by doing the following:
Go to the Administrator Console at
Log in with your credentials.
Navigate the menus with the following options: Environments -> Servers -> Admin Server.
Uncheck SSL Listen Port Enabled.
Restart the Integrated WebLogic Server.
Go to Section 4.8, "Next Steps" to see what steps you can take next.
This section describes how to launch a standalone version of the Integrated WebLogic Server and domain. You will complete the following tasks:
Make sure no other servers are running on your system.
From the command prompt, use the appropriate commands to do the following:
Navigate to ORACLE_HOME
QS_TEMPLATES environment variable to the BPM domain template.
Launch the standalone domain configuration wizard.
If you have defined the
ORACLE_HOME variable, the command sequence for this task should resemble one of the following:
cd $ORACLE_HOME/soa/common/bin QS_TEMPLATES="$ORACLE_HOME/soa/common/templates/wls/oracle.bpm_template_12.1.3.jar" export QS_TEMPLATES ./qs_config.sh
CD %ORACLE_HOME%\soa\common\bin set QS_TEMPLATES=%ORACLE_HOME%\soa\common\templates\wls\oracle.bpm_template_12.1.3.jar qs_config.cmd
Navigate through the following screens:
Specify a password for your default domain.
Edit the Domain Location. By default, the domain will be created at ORACLE_HOME
Review the port numbers.
This screen allows you to see the progress of the configuration.
End of Configuration
This screen appears when the installation is complete. Take note of the information on this screen.
You can leave the option to launch your new domain unchecked if you want to launch it manually from the domain location listed on this screen.
Click Finish to exit the wizard.
If you chose not to launch the domain automatically after creation, you can launch your standalone manually by using the command line to navigate to the domain home and to launch the
Domain configuration will take several minutes. When you see the following message appear in the terminal, the WebLogic Server has launched and your standalone domain has been created successfully.
SOA Platform is running and accepting requests
Your standalone domain is already configured with Oracle Business Process Management Suite and Oracle SOA Suite runtime components.
Launch Oracle JDeveloper with the appropriate command.
cd $ORACLE_HOME/jdeveloper/jdev/bin ./jdev
CD %ORACLE_HOME%\jdeveloper jdeveloper.exe
Select Window from the top menu, and then choose Application Server from the drop-down menu. Alternatively, use the keyboard shortcut
Ctrl-Shift-G. This will open the Application Server Navigator in the left-hand pane.
Right-click on Application Server in the Application Server Navigator. Select New Application Server from the drop-down menu to launch the Create Application Server Connection wizard.
Make sure Standalone Server is selected.
Name and Type
Specify an intuitive Connection Name for your server.
Leave WebLogic 12.x selected as the Connection Type.
Input the Username and Password you created during of domain configuration.
Input the standalone domain's name. Then click Next without changing anything else on the screen.
Click the Test Connection button at the top. If any of the tests fail, you should press Back to the Connections or Authentication screens to make sure you inputted everything correctly.
If everything passes, click Next.
The Finish screen tells you how to launch your new connection, covered in the following task. Click Finish.
Expand the connection node beside Application Servers in the Application Server Navigator. You should see your standalone domain listed by the Connection Name you specified on the Name and Type screen.
Right-click on your standalone domain's name and choose Launch Administrative Console.
Log into your administrative console. If you log in successfully, then you can begin creating applications. See Section 4.8 for the next steps you can take.
This section contains a few basic things you need to know to manage Oracle JDeveloper. This includes the following:
You can learn more about using Oracle JDeveloper by referring to "Working with Oracle JDeveloper" in Developing Applications with Oracle JDeveloper.
If you started the Integrated WebLogic Server from inside Oracle JDeveloper, you can simply close out of Oracle JDeveloper to end a running server.
If you do not want to close out of JDeveloper for any reason, you can also click the red stop button in the ribbon menu.
If you have launched an independent WebLogic Server, you should do the following:
cd DOMAIN_HOME/bin ./stopWebLogic.sh
CD %DOMAIN_HOME%\bin stopWebLogic.cmd
If you have closed Oracle JDeveloper and need to reopen it, you can use the following commands:
cd ORACLE_HOME/jdeveloper/jdev/bin ./jdev
CD %ORACLE_HOME%\jdeveloper jdeveloper.exe
When you install multiple Quick Start distributions on the same machine, each Quick Start Oracle home has its own unique instance of Java DB. All Java DB instances on the same machine initialize on the same port. For these reasons, you cannot perform the following actions:
You cannot simultaneously launch two Integrated WebLogic Servers from different distributions.
You cannot access your Oracle SOA Suite runtime environment by launching the Integrated WebLogic Server from your Oracle Business Process Management Suite Oracle home.
You cannot access your Oracle Business Process Management Suite runtime environment by launching the Integrated WebLogic Server from your Oracle SOA Suite Oracle home.
If you want to switch between different servers using Java DB on the same machine, you need to take the following steps to ensure you are launching the desired development environment:
If you have not done so already, decide on separate user directory home locations for each of your JDeveloper distributions. The user home directory will contain subdirectories for your domain files and your user-generated application files.
For example, you may want to install and use both an Oracle Business Process Management Suite JDeveloper and an Oracle SOA Suite JDeveloper on the same machine. You could designate the user home directory for your Oracle SOA Suite JDeveloper to be located at
C:/jdev12cworkarea/soa, while your Oracle Business Process Management Suite user home directory could be located at
Set the environment variable
JDEV_USER_DIR to the preferred location of the user directory home for the JDeveloper distribution that you want to use.
In the example given in the previous step, set
C:/jdev12cworkarea/bpm if you want to use the Oracle Business Process Management Suite environment.
JDEV_USER_DIRwill also change the default save location for your application projects. If you already launched and used JDeveloper without defining
JDEV_USER_DIR, you may have saved applications in the default application home. By default, the application home is located at the user's root directory under
Go to the JDeveloper home of the distribution you want to use.
For example, if you want to use your Oracle Business Process Management Suite environment, go to your Oracle Business Process Management Suite Oracle home and navigate to
Launch the JDeveloper executable from there.
You must reset the
JDEV_USER_DIR variable every time you switch between distributions using Java DB.
Once you have verified your installation, you can then perform any of the following tasks:
|Configure your installation for Enterprise Scheduler, Managed File Transfer, B2B, or Business Activity Monitoring.||You will have to create an Oracle database and standalone compact domain in order to use these components. See Chapter 5 of this book for detailed instructions.|
|Make or test an application of your own.||See "Working with Oracle JDeveloper" in Developing Applications with Oracle JDeveloper.|
|Delete your installation.||If you have tested your installation out and are done, see Chapter 8 of this book.|