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.
Java CAPS 6.2 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 “software 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 Sun 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.5.1 ML, with all JBI-based Java CAPS components packaged with the initial installation including the following:
Service Engines
BPEL Service Engine
Enterprise Data Mashup Server Engine
Intelligent Event Processor (IEP) Service Engine
Java EE Service Engine
XSLT Service Engine
Data Integrator Service Engine
Binding Components
Database Binding Component
File Binding Component
FTP Binding Component
HTTP Binding Component
JMS Binding Component
LDAP Binding Component
Scheduler Binding Component
Sun GlassFish Enterprise Server 2.1, Patch 2, including
Sun JMS IQ Manager
UDDI Server
Enterprise Manager
One default domain (domain1)
Java CAPS core products.
Sun Enterprise Service Bus
Sun Business Process Manager
Sun Composite Page Designer
Sun Adapters, which enable communication with specific external systems or OTD libraries.
Sun Adapter for Batch/FTP
Sun Adapter for DB2 Connect
Sun Adapter for e-Mail
Sun Adapter for File
Sun Adapter for HTTPS
Sun Adapter for JDBC/ODBC
Sun Adapter for Oracle
Sun Adapter for SQL Server
Sun Adapter for Sybase
You can download the executable file for the Java CAPS Installer from the Sun Download Center 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
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 the Sun Download Center 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 15 provides Release 5.1.3 component names and what they have changed to for Release 6.
Table 15 Component Name Comparison
Release 5.1.3 Component Names |
Release 6 Component Names |
---|---|
Sun SeeBeyond eGate Integrator |
Sun Enterprise Service Bus |
Sun SeeBeyond eInsight Business Process Manager |
Sun Business Process Manager |
Sun SeeBeyond eVision Studio |
Sun Composite Page Designer |
Sun SeeBeyond eTL Integrator |
Sun Data Integrator |
Sun SeeBeyond eView Studio |
Sun Master Index |
Sun SeeBeyond eIndex Single Patient View |
Sun Master Patient Index |
Sun Java Message Grid |
Sun Java Message Service Grid |
Sun SeeBeyond eWay Adapter for SAP ALE |
Sun Adapter for SAP ALE |
Sun SeeBeyond eWay Adapter for SAP BAPI |
Sun Adapter for SAP BAPI |
Sun SeeBeyond eWay Adapter for Oracle Applications |
Sun Adapter for Oracle Applications |
Sun SeeBeyond eWay Adapter for SWIFT Alliance Gateway |
Sun Adapter for SWIFT Alliance Gateway |
Sun SeeBeyond eWay e-Mail Adapter |
Sun Adapter for e-Mail |
Sun SeeBeyond eWay TCP/IP Adapter |
Sun Adapter for TCP/IP |
Sun SeeBeyond eWay LDAP Adapter |
Sun Adapter for LDAP |
Sun SeeBeyond eWay COM/DCOM Adapter |
Sun Adapter for COM/DCOM |
Sun SeeBeyond eWay SNA Adapter |
Sun Adapter for SNA |
Sun SeeBeyond eWay TCP/IP HL7 Adapter |
Sun Adapter for TCP/IP HL7 |
Sun SeeBeyond eWay Adapter for MSMQ |
Sun Adapter for MSMQ |
Sun SeeBeyond eWay Adapter for Oracle |
Sun Adapter for Oracle |
Sun SeeBeyond eWay Adapter for SQL Server |
Sun Adapter for SQL Server |
Sun SeeBeyond eWay Adapter for DB2 Universal Database |
Sun Adapter for DB2 Universal Database |
Sun SeeBeyond eWay JDBC/ODBC Adapter |
Sun Adapter for JDBC/ODBC |
Sun SeeBeyond eWay Adapter for DB2 Connect |
Sun Adapter for DB2 Connect |
Sun SeeBeyond eWay Adapter for Sybase |
Sun Adapter for Sybase |
Sun SeeBeyond eWay Adapter for VSAM |
Sun Adapter for VSAM |
Sun SeeBeyond eWay Adapter for Informix |
Sun Adapter for Informix |
Sun SeeBeyond eWay Adapter for Sun Java System Application Server |
Sun Adapter for Sun Java System Application Server |
Sun SeeBeyond eWay Adapter for WebLogic |
Sun Adapter for WebLogic |
Sun SeeBeyond eWay Adapter for WebSphere MQ |
Sun Adapter for WebSphere MQ |
Sun SeeBeyond eWay Development Kit |
Sun Adapter Development Kit |
Sun SeeBeyond eWay Adapter for CICS |
Sun Adapter for CICS |
Sun SeeBeyond eWay Adapter for IMS |
Sun Adapter for IMS |
Sun SeeBeyond eWay File Adapter |
Sun Adapter for File |
Sun SeeBeyond eWay Adapter for Siebel EAI |
Sun Adapter for Siebel EAI |
Sun SeeBeyond eWay Adapter for PeopleSoft |
Sun Adapter for PeopleSoft |
Sun SeeBeyond eWay Batch Adapter |
Sun Adapter for Batch/FTP |
Sun SeeBeyond eWay HTTPS Adapter |
Sun Adapter for HTTPS |
Sun SeeBeyond eGate API Kit |
Sun Enterprise Service Bus API Kit |
Sun SeeBeyond HL7 OTD Library |
Sun Message Library for HL7 |
Sun SeeBeyond SWIFT OTD Library |
Sun Message Library for SWIFT |
Sun SeeBeyond OTD Library for ASC X12 |
Sun Message Library for ASC X12 |
Sun SeeBeyond OTD Library for HIPAA |
Sun Message Library for HIPAA |
Sun SeeBeyond Alert Agent |
Sun Alert Agent |
Sun SeeBeyond SNMP Agent |
Sun SNMP Agent |
Sun SeeBeyond COBOL Copybook Converter |
Sun COBOL Copybook Converter |
Sun SeeBeyond Protocol Manager for ASC X12 |
Sun Protocol Manager for ASC X12 |
Sun SeeBeyond Protocol Manager for HIPAA |
Sun Protocol Manager for HIPAA |
The Sun 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.
Periods, spaces, and other punctuation are not valid characters for any Java CAPS user name, password, or component name.
The default user name and password for the Sun Enterprise Service Bus are admin and adminadmin.
After you complete a Project, you need to define an Environment and deploy the Project to the Environment. An Environment is a collection of domains (also known as logical hosts) that house Project components and information about external systems. A deployment Environment can include:
Domain (an instance of the Sun 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.