Skip Navigation Links | |
Exit Print View | |
Planning for Oracle Java CAPS 6.3 Installation Java CAPS Documentation |
Planning for Java CAPS 6.3 Installation
Java CAPS 6.3 Installed Components
Java CAPS 6.3 Supported Operating Systems
Supported Design-Time Platforms
Java CAPS 6.3 Supported JDK Versions
Interoperability With Oracle Products
Interoperability with Oracle Products
Interoperability with Java Enterprise System
Java CAPS 6.3 Components and Supported External Systems
Additional Information for the JDBC/ODBC Adapter and Database Binding Component
Java CAPS 6.3 System Requirements
Overview of the Installation Process
Overview of the Graphical User Interface Installation Process
Overview of the Command-Line Interface Installation Process
Contents of the Java CAPS Installer and Components Download Files
Java CAPS Installer TAR and ZIP Files
Java CAPS Components ZIP Files
Contents of the Installation DVDs
Troubleshooting the Java CAPS Installation
Certified Oracle Solaris 9 and 10 Patches
Certified SUSE Linux Enterprise Server 10 Daylight Savings Time Patch
This topic provides an overview of the installation process along with a list of what Java CAPS product names were in the past and what they are now. It also provides the location of the product SAR files on the DVDs.
The installation process is different from installations of Java CAPS prior to Release 6, and with this release you can perform a complete or custom installation on any supported platform. You can also perform the installation from a graphical user interface (GUI) or a command-line interface (CLI), with the exception of installing on Macintosh systems which only support the GUI installation.
Caution - Java CAPS 6.3 does not support spaces in the installation directory path. |
The flexible installation of Java CAPS enables you to:
Install more than one Domain on a single system.
Manage multiple Projects on a single environment. The separation of design from deployment makes it possible to use the same components in more than one Project.
Centralize your software distribution.
After uploading software into packages, Administrators select which physical server or groups of physical servers receive the software.
HTTP connections are used to upload and download the software to and from the Repository.
See the following topics for additional installation information:
The installation stores and manages the setup, component, and configuration information for Java CAPS Projects. All JBI-based Java Caps components are installed in the initial installation, but not all repository-based components are installed. After the initial installation, you can install additional Repository-based products, such as Oracle Java CAPS Master Index, the Adapter for TCP/IP HL7, and so on. Use the Java CAPS Uploader to upload and install additional components that are not automatically installed. Once you upload an additional product, you need to use the NetBeans Update Center to complete the installation.
The Java CAPS Installer, run from the command line interface (CLI) or the GUI, will install the following. You can customize the Java CAPS installation.
Java CAPS Repository Server
NetBeans IDE 6.9.1, with all JBI-based Java CAPS components packaged with the initial installation. This includes the following:
Service Engines
BPEL Service Engine
Data Integrator Service Engine
Intelligent Event Processor (IEP) Service Engine
Java EE Service Engine
POJO Service Engine
Worklist Manager (WLM) Service Engine
XSLT Service Engine
Binding Components
Database Binding Component
Email Binding Component
File Binding Component
FTP Binding Component
HL7 Binding Component
HTTP Binding Component
JMS Binding Component
LDAP Binding Component
REST Binding Component
Scheduler Binding Component
COBOL Copybook Encoder
GlassFish Enterprise Server 2.1.1, Patch 9, including
JMS IQ Manager
UDDI Server
Enterprise Manager
One default domain (domain1)
Java CAPS core products.
Oracle Java CAPS Enterprise Service Bus
Oracle Java CAPS Business Process Manager
Oracle Java CAPS Composite Page Designer
Oracle Java CAPS Adapters, which enable communication with specific external systems or OTD libraries.
Oracle Java CAPS Adapter for Batch/FTP
Oracle Java CAPS Adapter for DB2 Connect
Oracle Java CAPS Adapter for e-Mail
Oracle Java CAPS Adapter for File
Oracle Java CAPS Adapter for HTTPS
Oracle Java CAPS Adapter for JDBC/ODBC
Oracle Java CAPS Adapter for Oracle
Oracle Java CAPS Adapter for SQL Server
Oracle Java CAPS Adapter for Sybase
You can download the executable file for the Java CAPS Installer from Oracle downloads or the DVDs from the Media Kit to install Java CAPS. The graphical user interface Java CAPS Installer provides a standard setup wizard where you can specify details about the Java CAPS installation, including the following:
Java Software Development Kit (JDK) directory
Installation location
Repository name and port numbers
Enterprise Manager
Whether to install repository components into NetBeans
Whether to install support for Oracle Advanced Queueing
Whether to install support for Oracle WebLogic JMS
Login credentials and secure port numbers
You can also choose to perform a custom installation or a complete installation. A complete installation is recommended. Once you have completed the initial installation, you can install additional products using the Java CAPS Uploader and the NetBeans Update Center.
The command-line installation provides three different installation options. You can perform a silent installation in which you run a command and do not interact with the installer. This type of installation relies on a properties file that provides the necessary information to the installer, such as installation locations, JDK location, port numbers and so on. The installation process runs in the background and you do not see the progress.
You can also perform a text console installation. In this case, you interact with a text console to provide information about the installation. With the text console, you are prompted to provide the same information as is provided in the GUI (listed above), but the installer is text-based instead of graphical.
Finally, you can launch the GUI Java CAPS Installer from the command line, which uses the setup wizard to guide you through the installation.
If you install Java CAPS using the CLI, you can customize which of the default components are installed. If you decide to add components to your installation at a later time, you need to use the Java CAPS Uploader and the NetBeans Update Center to do so. There is no command-line installer for adding components to an existing installation
For the command-line installations to function correctly you must first download the ISO images from Oracle downloads to your installation directory. With these files you can install any or all of the default Java CAPS components:
With Release 6, the Java CAPS Repository-based components underwent a name change. The SAR files have not been changed to match the new component names. Table 14 provides Release 5.1.3 component names and what they have changed to for Release 6.
Table 14 Component Name Comparison
|
The Oracle Java CAPS Enterprise Service Bus maintains its own list of Repository names and user names; it does not poll the operating system or network to obtain or validate user names or Repository names. To simplify system administration, use your current naming conventions for Repository and user names.
Repository and user names (as well as passwords) are case sensitive, even on Windows systems. Although there is no limitation on the length of the names, you should keep them a reasonable length. Valid characters include all letters and numbers, dashes, and underscores.
Note - Periods, spaces, and other punctuation are not valid characters for any Java CAPS user name, password, or component name.
The default user name for the GlassFish server is admin. You provide the password when you install Java CAPS. You also need to provide a master password for GlassFish during installation. The default user name for the Repository-based tools (the Java CAPS Suite Uploader and Enterprise Manager) is also admin; the default password is adminadmin.
After you complete a Project, you need to define an Environment and deploy the Project to the Environment. An Environment represents the logical containers that house Project components and information about external systems. A deployment Environment can include:
Domain (an instance of the Oracle Java CAPS Enterprise Service Bus runtime environment)
Sun Java System Application Server (GlassFish)
Sun JMS IQ Manager
Sun Java System Message Queue
Unified JMS Resource Adapter
External Systems
Environment names can contain letters, numbers, dashes, and underscores. There is no character limit. Spaces and punctuation marks are not valid characters for Project names.