| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Using JBI Components: Configuring and Starting the Java EE Service Engine |
|
Administering JBI Components for Java CAPS
Using the Java EE Service Engine in a Project
About the Java EE Service Engine
Java EE Service Engine Features
Java EE Service Engine Limitations
Java EE Service Engine Use Case Scenarios
Java EE Service Engine as Service Provider and Service Consumer
Java EE Service Engine as a Service Provider
Java EE Service Engine as a Service Consumer
Java EE Service Engine Example Scenario
NetBeans Tooling Support for the Java EE Service Engine
Software Requirements and Installation
Configuring and Starting the Java EE Service Engine
To Start the Java EE Service Engine from the GlassFish V2 Application Server
To Start the Java EE Service Engine from the Admin Console
To Start the Java EE Service Engine Using Command Line Interface
Installing Java EE Service Engine Using Command Line Interface
Other Operations Using the Command Line Interface
Administering the Java EE Service Engine
To View the General Properties
Java EE Service Engine Log Management
Java EE Service Engine Deployment Articrafts
Using the Java EE Service Engine to Create a Composite Application
Using the BPEL Designer and Service Engine
Using the HTTP Binding Component
Processing an Order in a Purchase Order System
XSLT Designer: Simple Transformation Tutorial
Using the File Binding Component
Using the File Binding Component in a Project
Using the JMS Binding Component
Understanding the FTP Binding Component
Using the FTP Binding Component in a Project
Understanding the LDAP Binding Component
Using the LDAP Binding Component in a Project
Using the JAXB Wizard and Code-Seeder Pallete
Understanding the Database Binding Component
Using the Database Binding Component
Migrating From eTL to Sun Data Integrator
Designing Intelligent Event Processor (IEP) Projects
The Java EE Service Engine requires no configuration.
The Java EE Service Engine can be started in three ways. It starts automatically whenever a JBI service assembly which contains a Java EE Service Unit is deployed.
Users who work with the service engine in the NetBeans IDE must start the component from the GlassFish V2 application server.
GlassFish V2
-> JBI -> Service Engines nodes.Start from the pop-up menu.
The following message appears in the Output window:
Engine sun-javaee-engine has been started.
Ensure that the GlassFish application server is running. A green arrow icon next to the server node indicates that the server is running. If the server is not running, right click the server name and choose Start from the pop—up menu.
http://localhost:4848.
The default log in username isadmin, and the password is adminadmin.
The Sun Java System Application Server Admin Console opens in a new browser window.
JBI node expand Components and choose
sun-javaee-engine.
The Java EE Service Engine properties page opens.
Start button on the General tab page to start the
Java EE Service Engine.glassfish-> bin.asadmin.batfile. start-jbi-component sun-javaee-engine.