Myeclipse5.5ga: Configure WebSphere v6.1

1. Environment sun jdk1.5.0, myeclipse 5.1.1 ga

 

2. Introduction: myeclipse requires more work than configuring other servers when configuring websphere6;
WebSphere E6 and myeclipse must be installed on the same machine;
WebSphere 6 must use the ibm jdk, which is located in <was-install-dir>/Java;

(Generally in C:/program files/IBM/WebSphere/appserver/Java)
Only the myeclipse enterprise J2EE project can be deployed on WebSphere 6.
3. install and configure WebSphere 6
Step 1-> Program-> IBM WebSphere-> profile management tool

Click "Next" in step 2. The default value is "Application Server". Click "Next"

Step 3: click "Profile" or "Advanced profile creation ";

Here I select "Advanced profile creation ";

In typical creation, "Node" and "cell" are both set as default and set as Windows Services.

Advanced creation defines the "Node" and "cell" names by the user, and can be canceled as a Windows service.

 

Step 4 select the application to be deployed to the WebSphere Application Server environment being created

Select "Next" by default ".

Step 5 enter the name of the summary table (for example, Sophia );
Step 6 select the summary table path D:/IBM/WebSphere/appserver/profiles/Sophia;
Step 7 enter the end name: sophianode, Host Name: 127.0.0.1;
Step 8 enter the port number. The default port is enough.

(Click the "default settings" button. Otherwise, the default 9080 value is set to 9081. In this way, when you access the program later, the port number is not the default one, when I first installed it, I couldn't access it with 9080, that is, I didn't set the default value );

Step 9 is not selected as a Windows Service (otherwise the server will be started every time)
Step 10 is completed;
Step 2 start the server and open the console;
Step 2: Click server-application server, and then click the server name;
Step 2: view the tag "configuration"-> Fault Diagnosis-> record and track;
In step 5, click "JVM log"-> Configure the tag, change "file name" to console, and click "OK;

(Don't be confused. Set $ {system _.... /systemout. log} the original file name of the system is removed and changed to console and system. out and system. the file names in the err columns must be changed to the console. If this setting is not performed, nothing will be displayed when Websphere is started using debug in myeclipse)

Step 1 shows that your local configuration has been changed. Click "save", click "save", and then click "save" on the next page ";
Step 4: exit the console and stop the server;

4. myeclipse Configuration
Step 1 configure WINDOW> preferences> myeclipse> application servers> WebSphere 6.1;

 

Step 2 find the JDK option and click "add". The add JVM dialog box is displayed. Set jdk jre home directory to C:/program files/IBM/WebSphere/appserver/Java, webSphere can only run on ibm jdk;

Step 3: create a web project, such as "sophiatestweb", and then create an enterprise application project, such as "sophiatest ";

(Sophiatestweb stores the project source code, and sophiatest is a secondary project for packaging and publishing. Fill in the project name in the new enterprise application project, and then in the text box below, check "define web project modules. Because EJB is not used for the current project, click" Next ". In" Web project modules "below, check" sophiatestweb "and click" finish ")

 

The following configuration file is generated.

<Application ID = "application_1199258677375" version = "1.4" xsi: schemalocation = "http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
<Display-Name> Sophia </display-Name>
<Module id = "myeclipse.1188813827936">
<Web>
<Web-Uri> sophiatestweb. War </Web-Uri>
<Context-root>/sophiatestweb </context-root>
</Web>
</Module>
</Application>
 

Step 4: Click deploy in the menu bar to deploy myeclipse J2EE project to server;

Step 5 deploy sophiatest and select "packaged Archive" to complete the deployment;

(A sophiatest. Ear file will be generated in the C:/program files/IBM/WebSphere/appserver/profiles/program rv02/installableapps directory)

 

 

Step 7 open the Management Console Application of Websphere E6-> install a new application, and select
D:/IBM/WebSphere/appserver/profiles/cmdrv02/installableapps/sophiatest. Ear, and click Next;

(Enter the context root, for example, "/sophiatestweb". The context root is the port path in the URL when accessing the web.

For example, "http: // 127.0.0.1: 9080/sophiatestweb/index. jsp": "/sophiatestweb" is the context root)

 

Note: The installed application must be named sophiatest, which is the same as the name of the auxiliary project for packaging and publishing.

In step 8, select "enable class reload" and click Next;
In step 9, select "sophiatest. War" and click "Next;
Select "sophiatest. War" in Step 10 and click "Next;
Step 3 prompts "the application sophiatest is successfully installed ." Click "Save to master configuration" and then start the application;
Step 2: delete the previously deployed package, redeploy sophiatest, and select the first "exploded Archive". In the text box below, select the "delete Remote resource before deployment" check box to complete deployment;
 

Step 6 start websphere6 in myeclipse, and wait until "server1 is enabled for e-commerce" appears, that is, the startup is complete;

 

 

 

 

 

 

 

 

 

 

 

Configure websphere6 in myeclipse
1. Environment sun jdk1.4.2, eclipse3.1 myeclipse 4.0
2. Introduction: myeclipse requires more work than configuring other servers when configuring websphere6;
WebSphere E6 and myeclipse must be installed on the same machine;
WebSphere 6 must use the ibm jdk, which is located in <was-install-dir>/Java;
Only the myeclipse enterprise J2EE project can be deployed on WebSphere 6.
3. install and configure WebSphere 6
Step 1: Click create profile );
Step 2 enter the name of the summary table (for example, myeclipse );
Step 3 select the summary table path D: ibmwebsphereappserverprofilesmyeclipse;
Step 4 enter "mydomainsenode", Host Name: 127.0.0.1;
Step 5 enter the port number, which is the default port;
Step 6 does not select Windows service;
Step 7 is completed;
Step 8 start the server and open the console;
Step 9: Click server-application server, and then click the server name;
Step 10: view the tag "configuration"-> Fault Diagnosis-> record and track;
In step 5, click "JVM log"-> Configure the tag, change "file name" to console, and click "OK;
Step 1 shows that your local configuration has been changed. Click "save", click "save", and then click "save" on the next page ";
Step 4 launch the console to stop the server;
4. myeclipse Configuration
Step 1 configure WINDOW> preferences> myeclipse> application servers> WebSphere 6;
Step 2 configure jdk jre home directory to/Java, and WebSphere can only run on ibm jdk;
(WebSphere is known to run on a heavily modified ibm jdk and running it with Sun's JDK, jrockit, gcj or other jdks simply will not work)
Step 3: create a web project such as "ibmtestweb", and then create an enterprise project such as "ibmtest ";
Step 4: Click deploy in the menu bar to deploy myeclipse J2EE project to server;

(Myeclipse deployment manager must be launched by clicking the button on your toolbar as shown in the screenshot below)
Step 5 deploy ibmtest and select "packaged Archive" to complete the deployment;
Step 6 start websphere6 in myeclipse, and wait until "server1 is enabled for e-commerce" appears, that is, the startup is complete;
(Wait for the server server1 open for e-business message as before .)
Step 7 open the Management Console Application of Websphere E6-> install a new application, and select
D: ibmwebsphereappserverprofilesmyeclipseinstallableappsibmtest. Ear. click Next;
In step 8, select enable class reload and click Next;
In step 9, select "ibmtestweb. War" and click Next;
In step 10, select "ibmtestweb. War" and click Next;
Step 3 prompts "the application ibmtest has been installed successfully ." Click "Save to master configuration" and then start the application;
Step 2 Delete the previously deployed package, redeploy ibmtest, and select the first item "exploded Archive". Next, select "delete Remote resource before deployment" to complete deployment;