After following the steps in this section, you will be able to test applications using the Integrated WebLogic Server and Java DB.
This is where you are in the Quick Start installation and configuration roadmap.
Plan your installation.
You used Chapter 1 to decide which distribution and configuration path suits your goals.
Download and install a Quick Start distribution
You downloaded and installed Quick Start for Oracle SOA Suite or Oracle Business Process Management Suite.
Configure a default or standalone domain.
You are configuring a default domain or a standalone domain for your developed applications.
Develop or test an application.
You will develop or test an application.
About Quick Start Domains
There are two supported ways to configure a domain with Quick Start. All domains will be pre-configured with IDE plug-ins for the Oracle Business Process Management Suite components of your choice.
Use the following table to decide which domain best suits your needs.
|Suggested Use Case||Method||Description|
Configure the Integrated WebLogic Server's default domain in JDeveloper.
Launch the Integrated WebLogic Server from inside JDeveloper to 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.
Development with an Oracle Database
Configure a compact domain.
You can configure your Quick Start installation to use an Oracle database with an external compact domain.
Oracle recommends you to choose this option, which is compatible with Enterprise Scheduler, Managed File Transfer, B2B, Healthcare, Human Workflow, or BAM components.
Any other method of creating a domain is not recommended.
Preparing to Launch the Integrated WebLogic Server
Follow steps to prepare your environment before launching the Integrated WebLogic Server.
Setting the JDEV_USER_DIR Environment Variable
You can set the
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.
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.
Oracle recommends a directory structure similar to the one shown below, where
config shows the location of the user home directory.
Figure 7-1 Recommended Oracle Fusion Middleware Directory Structure
Description of "Figure 7-1 Recommended Oracle Fusion Middleware Directory Structure"
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/system126.96.36.199.0.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\system188.8.131.52.0.x.x.xxxx\DefaultDomain. Your default application home will be created at
Once you have set
JDEV_USER_DIR, the domain home and application home will be collocated as subdirectories under the defined location. For example, on a UNIX system, the domain home will be located in
JDEV_USER_DIR\system184.108.40.206.0.x.x.xxx. The application home will be located in
Setting the ORACLE_HOME Environment Variable
You can set the
ORACLE_HOME environment variable to simplify navigating to the various directories when you are running installation and configuration commands.
setenv ORACLE_HOME $HOME/Oracle/Middleware/Oracle_Home export ORACLE_HOME
Checking Entropy for Oracle Linux
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"
Configuring JDeveloper's Default Domain
You can configure JDeveloper's default domain by launching the Integrated WebLogic Server.
Starting the Integrated WebLogic Server
- Start JDeveloper.If you have set the
ORACLE_HOMEenvironment variable to your Oracle home, you can enter commands similar to the following examples:
cd ORACLE_HOME/jdeveloper/jdev/bin ./jdev
cd ORACLE_HOME\jdeveloper jdev.exe
As Oracle JDeveloper starts, you will get three prompts.
When prompted, select Studio Developer as your role and click OK.
When prompted, click 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 click OK.
JDeveloper has fully started at this point.
- For UNIX
- Start the Integrated WebLogic Server by selecting Run from top menu bar, then Start Server Instance.
- The first time you start the server instance, you will be prompted to enter a password for your default domain.
The Administrator ID, Listen Address, Listen Port, and SSL Listen Port should already have values. Review them and make any appropriate changes.
- Starting 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
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.
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 started successfully.
[SOA Platform is running and accepting requests [IntegratedWebLogicServer started.]
Verifying Your Domain
Your default domain is already configured with Oracle SOA Suite and Oracle Service Bus runtime components. To verify your domain installation:
- Access the Enterprise Manager Fusion Middleware Control, which is located at a URL following this format:
The default port for the Integrated WebLogic Server should always be
7101unless you changed it during configuration.
Sign in using the username and password that you specified when starting 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.
- Alternatively, if you plan to develop projects using the Oracle Service Bus console, you can check to see if Oracle Service Bus is running.
The Oracle Service Bus console is located at an URL with the following format:
Log in using the username and password that you specified when creating your standalone domain.
For more information on using the Oracle Service Bus console, see Getting Started with the Oracle Service Bus Console in Developing Services with Oracle Service Bus.
Disabling Secure Sockets Layer (SSL)
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 as follows:
- Go to the Administrator Console at
- Log in with your credentials.
- Select Environments, then Servers, then Admin Server.
- Uncheck SSL Listen Port Enabled.
- Restart the Integrated WebLogic Server.
About Basic JDeveloper Functions
You should be familiar with basic Oracle JDeveloper functions to manage JDeveloper effectively.
You can learn more about using Oracle JDeveloper in Working with Oracle JDeveloper in Developing Applications with Oracle JDeveloper.
Stopping the Integrated WebLogic Server
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.
DOMAIN_HOMEenvironment variable to your Oracle home, you can enter the following commands to stop an independent WebLogic Server:
cd $DOMAIN_HOME/bin ./stopWebLogic.sh
cd %DOMAIN_HOME%\bin stopWebLogic.cmd
Managing Multiple Installations on the Same Machine
When you install multiple Quick Start distributions on the same machine, each distribution has its own JDeveloper that runs 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 start two Integrated WebLogic Servers from different distributions.
You cannot access your Oracle SOA Suite runtime environment by starting the WebLogic Server from your Oracle Business Process Management Suite Quick Start Oracle home.
You cannot access your Oracle Business Process Management Suite runtime environment by starting the WebLogic Server from your Oracle SOA Suite Quick Start Oracle home.
Switching Between Quick Start Distributions
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 starting 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_DIRto the location of the user directory home for the JDeveloper distribution that you want to use.
For the example in the previous step, set
C:/jdev12cworkarea/soaif you want to use the Oracle SOA Suite environment.
JDEV_USER_DIRchanges the default save location for your application projects. If you already started and used JDeveloper without defining
JDEV_USER_DIR, you may have saved applications in the default application home. The default 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 SOA Suite environment, go to your Oracle SOA Suite Oracle home and navigate to
- Start 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 perform any of the following tasks:
Configure your Quick Start installation to use an external Oracle database and standalone compact domain.
Make or test an application of your own.
See Working with Oracle JDeveloper in Developing Applications with Oracle JDeveloper.
Delete your installation.