Sign in or 
Share this
Cloud Development Scenario A
Remote / debugging and deployment on the cloud - work in progress (DRAFT)
For slow network connections or if VNC is not working for you, this section reviews an alternate model for cloud development -- using remote debugging and deployment with no local server. However, the majority of corporate firewalls may not allow communications on default ports that remote debugging runs on, so both JDeveloper and Enterprise Pack for Eclipse allow you to configure the debug port. Whatever port you are intending to use, spend a moment verifying that they will work before considering this alernative.
1.Make sure your security group settings in elasticfox or in the AWS console to allow the default remote debugging ports for both JDeveloper (default is 4000) and Enterprise Pack for Eclipse (default is 8453) . The defaults are listed here, and the CIDR data will obviously be different for your network.
or in the AWS console:
2. For JDeveloper users the following documentation will enable you to use the existing instance of WLS that is running on the Amazon Cloud.
3. For Enterprise Pack for Eclipse users, you must add arguments to the server start script (startweblogic.sh) to enable debug mode.
In startWeblogic.sh, just before the call of setDomainEnv.sh, add
debugFlag=true
DEBUG_PORT=8888 (Optional, debug is 8453)
The debugFlag enables debug in setDomainEnv.sh:
if [ "${debugFlag}" = "true" ] ; then
JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
export JAVA_DEBUG
JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
export JAVA_OPTIONS
else
Then start the server via the command line (startweblogic.sh). Then in Enterprise Pack for Eclipse, In the Java EE Perspective -> Servers tab, create a new server configuration. Select a Remote Server Type and enter the connection information to the remote host.
Oracle Enterprise Pack for Eclipse supports remote deployment and debugging to Weblogic Admin Servers, Managed Servers, and Clusters. The server configuration screen enables additional options for module deployment such as use of Deployment Plans, undeploying existing modules, and launching the Weblogic Server Administrative Console (right click the server configuration in the Servers tab and select Open).
Useful links:
http://download.oracle.com/docs/cd/E14545_01/help/oracle.eclipse.tools.weblogic.doc/html/conFeatureOverview.html#remoteDep
http://download.oracle.com/docs/cd/E12840_01/wlw/docs103/guide/ideuserguide/servers/conWebLogicServer.html#DebugRemote
Note: Enterprise Pack for Eclipse includes a Web browser to let you access the Internet from within the IDE. If your machine is located inside of a network, which requires a proxy to access outside resource such as the Internet, you typically define this using the Eclipse IDE's Window > Preferences > General > Network Connections, proxy settings.
These settings may impact the deployment of Java EE application from local IDE to a remote Oracle WebLogic Server located in the same network: the WebLogic deployer might not be able to upload the Java EE application to the remote instance of Oracle WebLogic Server, if the server host is not explicitly specified in the No Proxy for list of the Preferences > General > Network Connections dialog. This condition occurs with Oracle WebLogic Server versions 11gR1, 10gR3, and, possibly, some earlier versions. To eliminate this condition, add the remote Oracle WebLogic Server host name to the No Proxy for list.
For slow network connections or if VNC is not working for you, this section reviews an alternate model for cloud development -- using remote debugging and deployment with no local server. However, the majority of corporate firewalls may not allow communications on default ports that remote debugging runs on, so both JDeveloper and Enterprise Pack for Eclipse allow you to configure the debug port. Whatever port you are intending to use, spend a moment verifying that they will work before considering this alernative.
1.Make sure your security group settings in elasticfox or in the AWS console to allow the default remote debugging ports for both JDeveloper (default is 4000) and Enterprise Pack for Eclipse (default is 8453) . The defaults are listed here, and the CIDR data will obviously be different for your network.
or in the AWS console:
2. For JDeveloper users the following documentation will enable you to use the existing instance of WLS that is running on the Amazon Cloud.
- Create a ADF Domain into the server : Official Install Guide Doc:http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/ojdig.htm#BDCGEFFF
Unofficial summary:http://one-size-doesnt-fit-all.blogspot.com/2009/01/configuring-weblogic-server.html
- Deploy your application into the ADF Domain: Unofficial guide for Linux and Windows:http://blogs.oracle.com/raghuyadav/2008/11/how_to_deploy_adf_application.html
- This guide will guide you through the instruction on how to set up remote debugging on WLS if needed:http://www.oracle.com/technology/products/jdev/howtos/weblogic/remotedebugwls.html
3. For Enterprise Pack for Eclipse users, you must add arguments to the server start script (startweblogic.sh) to enable debug mode.
In startWeblogic.sh, just before the call of setDomainEnv.sh, add
debugFlag=true
DEBUG_PORT=8888 (Optional, debug is 8453)
The debugFlag enables debug in setDomainEnv.sh:
if [ "${debugFlag}" = "true" ] ; then
JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
export JAVA_DEBUG
JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
export JAVA_OPTIONS
else
Then start the server via the command line (startweblogic.sh). Then in Enterprise Pack for Eclipse, In the Java EE Perspective -> Servers tab, create a new server configuration. Select a Remote Server Type and enter the connection information to the remote host.
Oracle Enterprise Pack for Eclipse supports remote deployment and debugging to Weblogic Admin Servers, Managed Servers, and Clusters. The server configuration screen enables additional options for module deployment such as use of Deployment Plans, undeploying existing modules, and launching the Weblogic Server Administrative Console (right click the server configuration in the Servers tab and select Open).
Useful links:
http://download.oracle.com/docs/cd/E14545_01/help/oracle.eclipse.tools.weblogic.doc/html/conFeatureOverview.html#remoteDep
http://download.oracle.com/docs/cd/E12840_01/wlw/docs103/guide/ideuserguide/servers/conWebLogicServer.html#DebugRemote
Note: Enterprise Pack for Eclipse includes a Web browser to let you access the Internet from within the IDE. If your machine is located inside of a network, which requires a proxy to access outside resource such as the Internet, you typically define this using the Eclipse IDE's Window > Preferences > General > Network Connections, proxy settings.
These settings may impact the deployment of Java EE application from local IDE to a remote Oracle WebLogic Server located in the same network: the WebLogic deployer might not be able to upload the Java EE application to the remote instance of Oracle WebLogic Server, if the server host is not explicitly specified in the No Proxy for list of the Preferences > General > Network Connections dialog. This condition occurs with Oracle WebLogic Server versions 11gR1, 10gR3, and, possibly, some earlier versions. To eliminate this condition, add the remote Oracle WebLogic Server host name to the No Proxy for list.
phumphrey |
Latest page update: made by phumphrey
, May 27 2009, 3:00 PM EDT
(about this update
About This Update
Edited by phumphrey
47 words added 2 words deleted view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
There are no threads for this page.
Be the first to start a new thread.
