Websphere installation and Enterprise Application Deployment [application cases] And websphere Application Cases

Websphere installation and Enterprise Application Deployment [application cases] And websphere Application Cases

Example of Websphere installation and Enterprise Application Deployment

Environment

Name	Version
Linux	CentOS-5.6-x86_64
Oracle software	10201_database_linux_x86_64.cpio
Websphere	WASND70_LINX64
Enterprise Application Package	Hyl. ear

**************************************** ********************** **************************************** **

In this article, hyl. ear is used in enterprise applications to avoid sensitive words. The pictures are changed accordingly and only for technical exchanges and sharing.

For more information about the Middleware Theory, see the following articles.

**************************************** **************************************** **************************************** ******

**************************************** ***************************************

* Goal: to install Websphere and deploy applications

* Steps:

* 1. Install Websphere

* 2. Deploy applications

**************************************** ***************************************

[Root @ hyl bin] # java-version -- verify the java version. The java version 1.6 meets the WAS requirements.

Java version "1.6.0 _ 17"

OpenJDK Runtime Environment (IcedTea61.7.5) (rhel-1.16.b17.el5-x86_64)

OpenJDK 64-Bit Server VM (build 14.0-f8, mixed mode)

1. Install Websphere

The Installation Reference is as follows:

Put the second disc as follows:

2. Deploy enterprise applications

Browser Logon: http: // 192.168.56.103: 9060/admin

Deploy enterprise applications

Note: hyl. ear is used as an example for enterprise applications.

Click the Oracle JDBC Driver. On the page that appears, click "Data Source" as follows:

Enter jdbc: oracle: thin: @ 192.168.56.103: 1521: hyl

-- Save and click New

-- Set and save the following operations

-- Create again after completion, as shown below

Test the connection and an error is reported as follows:

To solve the package problem, copy the/home/u01/app/oracle/product/10.2.0/db_1/jdbc/lib/ojdbc14.jar file to the root directory, reconfigure the "JDBC provider", as shown in:

Note: The ojdbc6.jar package should be used for oracle11g, And the ojdbc14.jar package should be used for oracle10g.

Test the connection again as follows:

Start, application: hyl. ear

-- The configuration is successful. Enter the corresponding IP address in the browser.

-- So far, the process of deploying enterprise-level applications using hyl. ear has been described. For example, log on to the browser: http: // localhost: 9080/hyl (or loaclhost is the Host IP address. 9080 is the default port. You can view another article by changing the settings: middleware optimization: Click to open the link)

Summary: Pay attention to the class path setting. If the package path is incorrect and the specified package cannot be found, the connection will fail.

**************************************** *******Statement************************************************ 

Original works, from "Deep Blue blog" blog, welcome to reprint, reprint please be sure to indicate the source (http://blog.csdn.net/huangyanlong ).

Please leave a message if the statement is incorrect. Thank you very much.

Reminder: Click the directory to view the directory.

*****************************************************************************************************

After deploying the application under websphere, the error 500 is reported when you access the page.

The main source is not found.
Com. founder. sm. frame. util. SystemUtil
This class. Check whether there are any jar packages in the tomcat lib directory. You have not deployed them to websphere.
 
How do I change the project name when deploying a project using websphere ??

I used websphere6.1 + myeclipse. I will find the one I summarized for you .. =
I cannot find it. Ask me again.

This article is composed of documents found on the myeclipse official website and content summarized in practice.

1. Download and install WebSphere 6.1. Remember the node name and cell name you set during the installation process.

2. Start eclipse and choose window> preperences> myeclipse> application servers> websphere6.1.
Click Browse... select your eclipse installation directory. I installed it in D: \ webshpere6.1. Then, myeclipse automatically sets Profile Root Directory, Node name, and cell name. you need to confirm. profile Root Directory is a folder under the Profiles Directory under your installation Directory.

My name is D: \ webshpere6.0 \ profiles \ invalid rv01. while node name and cell name are set to the name named after your machine name, change the cell name to the name of the folder under the installedApps directory (D: \ webshpere6.0 \ Profiles \ cmdrv01 \ installedApps) in the RootDirectory of profiles. My name is localhostNode01Cell, change node name to cell name and remove the cell name. select enable. click Apple to save.

3. expand WebSphere 6.1, select JDK, and set JDK to JDK (D: \ webshpere6.0 \ java) under the installation directory of webshpere6.1 ). be sure to set JDK to IBM or websphere cannot run.

4. start websphere (instead of using eclipse, but using websphere's startup server), select the management console, click Server> application server, and select a service, generally, it is server1. in the fault diagnosis, select record and trace-> JVM log, and change the two file names to console. save, log out, and stop the service.

5. create your own enterprise project in eclipse (it must be an enterprise project). If you have a web project, you can set the web modle of the enterprise project to this web project. If not, create a new one.

6. release an Enterprise project (not a web project). Select Packaged Archive for the first release.

7. start websphere with eclipse or websphere, and go to the console. Choose Application> install new application, click \ webshpere6.0 \ profiles \ AppServ01 \ installableApps and select your own published Project name ear file (You may not be AppServ01). Then click next, the only thing to note is to set the context root of the web module and automatically load the changes to the class files and jsp files to be selected.

8. Go back to the console homepage, Application> enterprise application, select your own project, click Start. log out, and stop websphere.

9. click release again in eclipse, delete the newly released project, and click add... select an enterprise project and Exploded Archive. select Delete Remote... item. then release. you can debug the SDK in real time later.

Note: To debug in websphere, you must create... the remaining full text>