|
|
1.
Introduction
MyEclipse Blue Edition provides support for deploying
applications to remote WebSphere 7.0, 6.1 and 6.0 installations.
This includes initial application deployment as well as
deployment of incremental changes as you work.
This document will outline how to configure MyEclipse to work
with your WebSphere Application Server instance using these
advanced features.
|
|
2.
System Requirements
This tutorial was created with MyEclipse Blue Edition. However, if younotice that
portions of this tutorial appear different from the screens you
are seeing, please
let us know and we will make sure to
resolve any inconsistencies.
|
3.
Configure
the Remote WebSphere Connector
Support for deployments to remote WebSphere instances begin with
the
Remote WebSphere connector available in MyEclipse
Blue and found under the
Servers > WebSphere - Blue Connectors
preference node:
Setting the
WebSphere home directory is the key to providing
MyEclipse with the libraries it needs from a WebSphere
installation in order to connect to your remote WebSphere
instances.
At first glance it might look like you need a local install of
WebSphere to set here in order to connect to a remote instance --
that would surely work, but isn't the case necessarily. The
WebSphere home directory needs to point to a
local folder on your hard drive that contains
one of the following installed pieces of
software:
Pointing the connector's home directory to any of these installed
pieces of software will enable MyEclipse to deploy to remote
WebSphere instances.
After you have set this value, you can setup the profile(s) on
the remote server that you want to deploy to. You can start the
profile wizard by clicking the
Add button at which point MyEclipse will ask you
for the connection details for the remote server:
On this screen you will want to fill out the following
information:
-
Name: The name of the profile you want to
manage deployments to. This must match a name of an existing
profile on the remote server.
-
Host: The hostname (or IP address) of the host
machine that WebSphere is running on.
-
Port: The "SOAP Connector Address"
port (see "
Finding the Right WebSphere
Port Numbers" below)
-
Security: If you have administrative security
enabled on this remote profile, please be sure to include the
necessary credentials here so MyEclipse can connect to that
profile.
After filling out the connection information for the server and
the profile, click
Next and you will be asked for the
Node information that you want to setup:
We would highly recommend starting off by clicking the
Automatically Detect from Server button right
away as most times MyEclipse can read these values from the
connection and profile information you've entered on the previous
screen and load them here for you automatically. If you know the
values and just want to type them in, go ahead.
To enable remote debugging of classes and JSPs, be sure to check
Enable remote debugging and setup the remote
debug port for the WebSphere server that MyEclipse can connect
it's debugger to. Please be sure to check out the section "
Configure
WebSphere to Support Remote Debugging" below to make sure
remote debugging is enabled on your WebSphere server so you can
debug from inside MyEclipse.
Lastly, entering in the
Admin Port and
HTTP Port are not required for successful
deployments, but will enable some addition facilities in
MyEclipse Blue's Remote WebSphere connector for you if you
provide them.
After you are done, hit
Finish and you are ready to start deploying
applications to your remote WebSphere instance and developing
inside of MyEclipse Blue!
|
4.
Configure
WebSphere to Support Remote Debugging
In order to successfully debug your Java EE applications on your
remote WebSphere server from inside MyEclipse Blue, your
WebSphere server must be setup to run the Debug Service that
MyEclipse needs to connect to.
To enable debugging on the remote WebSphere server, you will
first want to launch the Administrative Console for the WebSphere
install:
Now click on "WebSphere application servers" entry on
the left menu:
Now do the following:
-
Select your server in the list by clicking its name
-
Click on
Debugging service on the bottom fo the
Configuration tab
-
Write down (or remember) the
JVM debug port (you need to provide this to
MyEclipse's profile configuration)
-
Check the
Enable service at server startup checkbox and
hit
Apply
-
Click the
Save link that appears at the top of the screen
and restart your server.
Now your remote WebSphere instance is ready to provide debugging
services to MyEclipse Blue, if necessary, go back to your Profile
configuration under the
Remote WebSphere connector in MyEclipse, edit
it, and enter in the debug port information you recorded from
Step #3 above.
Now you can easily debug applications deployed to the remote
server by selecting the server and clicking the
Debug button in the MyEclipse Blue
Servers view in order to connect MyEclipse
Blue's debugger to the remote server:
|
5.
WebSphere Thin
Client Installation
WebSphere's install media provides a few different types of
installable software - one of which is the Thin Client
installation. This installation provides all the JARs required by
MyEclipse Blue for Remote WebSphere support.
If you don't want to create a complete local install of WebSphere
on your machine, you can install just the Thin Client and setup
the
Remote WebSphere connector as mentioned above to
point to the thin client's install directory and you should be
all set.
You can install the thin client software by running the
Launchpad WebSphere installation software
(launchpad.exe on Windows) and selecting the
Application Clients installation target:
During the installation you will want to make sure to add the
Stand-alone Thin Clients and Resource Adapters
to the list of software to be installed. This is an optional
component and not installed by default.
Once you are done, you can set this as your
WebSphere home directory under the
Remote WebSphere connector as mentioned above:
|
6.
Finding the Right WebSphere
Port Numbers
To enable deployment to remote WAS server you will need several
port numbers. You can find it on your WebSphere administration
console.
-
Login to your administrative console. On local server you can
use application shortcut:
-
Click on
WebSphere application servers entry on the left
menu.
-
Select your server in the list by clicking on its name.
-
Expand
Ports on the
Communications group on the
Configuration tab:
-
Write down following ports from the table that is expanded:
|
SOAP_CONNECTOR_ADDRESS
|
You will need to enter it to the "Port" entry on the first
page of the "Remote Server" wizard
|
|
WC_adminhost
|
This value should be entered to "Admin Port" entry on the
second wizard page
|
|
WC_defaulthost
|
This value should be entered to "HTTP Port" entry on the
second wizard page
|
|
7.
Resources
In this section we want to provide you with additional links to
resources that supplement the topics covered in this tutorial.
While this is not an exhaustive list, we do make an effort to
point to the more popular links that should provide you with
diverse, high-quality information.
MyEclipse Blue Edition and WebSphere Tutorials
Additional Popular MyEclipse Blue Tutorials
|
8.
Feedback
We would like to hear from you! If you liked this tutorial, has
some suggestions or even some corrections for us please let us
know. We track all user feedback about our learning material in
our
Documentation Forum.
Please be sure to let us know which piece of MyEclipse material
you are commenting on so we can quickly pinpoint any issues that
arise.
|
