WebSphere packaged web applications and deployment options

sponsored links
WebSphere packaged web applications and deployment scenarios, the original quote from:

http://www.hashei.me/2009/07/websphere-application-compact-for-deployment.html

This paper describes the use of WebSphere packaged web applications and deployment options


Find assembly.bat and setupCmdLine.bat these two documents, the following diagram:

WebSphere packaged web applications and deployment options


One assembly.bat file is used to start the application assembly tool; setupCmdLine.bat is used to configure the startup parameters, located in the file at the beginning of the two possible (if it is copy over a) the need to configure:

SET WAS_HOME = D: \ WebSphere5 \ AppServer

SET JAVA_HOME = D: \ j2sdk1.4.2_03

WAS_HOME: Webshpere 5 installation directory or Webshpere 5 copies of directory;

JAVA_HOME: jdk directory, defaults to $ (WebSphere5) \ AppServer \ java directory, but not necessarily valid, you can try to point to your jdk common directory;

Parameters configured, run assembly.bat document, after the end of the process interface, the application assembly tool to show the main interface, the following diagram:

WebSphere packaged web applications and deployment options


[Process interface]

WebSphere packaged web applications and deployment options


[The main interface]

WebSphere packaged web applications and deployment options


Will open the following interface:

WebSphere packaged web applications and deployment options


Where the red coil painting named after the package name of your ear, and then right-click on the left side of the directory tree [Web module] and click [New], the following diagram

WebSphere packaged web applications and deployment options


Pop up its configuration interface, the following diagram:

WebSphere packaged web applications and deployment options


Naming a good file name (war package name) and the context root and click [OK] button, and then expand [Web modules] directory tree, get the next map interface:

WebSphere packaged web applications and deployment options


The following steps more crucial, including:

1, configuration WebSphere packaged web applications and deployment options


Delineation of some of the red line to make the following modifications:

WebSphere packaged web applications and deployment options


Its meaning is used to define the data connection in the pool, there are other roles that you see at a glance. Then, click [bound] Tab page, the following figure:

WebSphere packaged web applications and deployment options


The key here is to write your database connection pool JNDI name in the application after the release will be defined in detail, and good, by definition, I have written is as follows:

At this point we have a database connection resource reference defined finished, click [OK] button bar!

WebSphere packaged web applications and deployment options


Open the following interface:

WebSphere packaged web applications and deployment options


Note that the red part of the concept of the coil set, a brief explanation, we generally use a directory such as the following diagram:

WebSphere packaged web applications and deployment options


In this opensrc is your root directory or archive. Click [Browse] button, select the folder the following figure, after opensrc:

WebSphere packaged web applications and deployment options


In the left tree expand WEB-INF directory select the classes directory, and then under the right side of the content on the display all the contents of the classes, as follows:

WebSphere packaged web applications and deployment options


The right to select all the contents, click [Add] button, the following diagram:

WebSphere packaged web applications and deployment options


You can also go to get rid of some unwanted content, such as we often use the VSS of the resulting "vssver.scc", is selected and click [Remove] button, okay completed click [OK] button.

WebSphere packaged web applications and deployment options


You can click on the red line delineated in the [expansion] head, sort, select all need to remove the files, and then press the keyboard [DEL] key to delete. Such files are added to finish.

2, configuration jar file

Add a jar file and add the class file operations identical, but in the directory tree on the left select "WEB-INF/lib" directory, it is noteworthy to add certain if the "jar" file, if not, such as the spring of the "spring-beans . dtd "file, the tool will remind you, do not ignore it, and as long as [OK] on the line.

3, configuration resource file

Add a resource file in two steps:

Ø In the directory tree on the left select the "root" directory, in this is the "opensrc" directory, it is noteworthy that the choice to remove the right of the contents of note "WEB-INF" directory, the following figure:

WebSphere packaged web applications and deployment options


Ø In the directory tree on the left select "WEB-INF" directory, it is noteworthy that the choice to remove the right of the contents of note "classes" and "lib" directory, the following figure:

WebSphere packaged web applications and deployment options


Click [OK] button, everything OK, Oh! Wrong, how the list is not "struts-config.xml" and other documents, I do not know why, the tool did not show them up, but you rest assured that they have been included entered.

Next we must configure all of the servlet and servlet mapping, you can control the original web.xml file one by one added to the "web component" and the servlet mapping to go, pay attention to configure a number of initialization parameters and other attributes.

The application's web.xml control may also need to add some other configuration information to its new WebSphere packaged web applications and deployment options


Tool shows preservation process:

WebSphere packaged web applications and deployment options


Then happy to pop-up:

WebSphere packaged web applications and deployment options


HA HA ! 're Done! Do not worry, we have to check the use of RAR will be ". Ear" open the packet

WebSphere packaged web applications and deployment options


Oh! The original is the case, to further open the "META-INF" directory:

WebSphere packaged web applications and deployment options


This is the WebSphere packaged web applications and deployment options


"Struts-config.xml" and other documents are in operation. Note that the directory level of war will not confuse the bag, a mess in general to re-package the resource file, be sure.
  • del.icio.us
  • StumbleUpon
  • Digg
  • TwitThis
  • Mixx
  • Technorati
  • Facebook
  • NewsVine
  • Reddit
  • Google
  • LinkedIn
  • YahooMyWeb

Related Posts of WebSphere packaged web applications and deployment options

  • RoR explained

    ROR is Ruby on Rails. Ruby is a well-known has been very good dynamic language It's dynamic language. Simple and easy. Dynamic languages are interpreted, but the performance may make a discount, but not absolute, because the application is complex, th

  • Spring + Hibernate to use Glassfish Database Connection Pool

    applicationContext.xml file content <? xml version = "1.0" encoding = "UTF-8"?> <beans xmlns = " http://www.springframework.org/schema/beans " xmlns: xsi = " http://www.w3.org/2001/XMLSchema-instance " ...

  • What is the appfuse

    First, Appfuse brief introduction Matt Raible are Appfuse developed a guiding entry-level J2EE framework, how to integrate its popular Spring, Hibernate, ibatis, struts, Xdcolet, junit, etc. give the basic framework of the model, the latest version 1.7 is

  • JAVA EE JSP_JNDI

    dsfdsa http://lindows.javaeye.com/admin/blogs/213348 Tomcat 6 with the connection pool data source configuration http://www.blogjava.net/ec2008/archive/2008/07/19/216063.html project: test Driver path: D: \ workspace \ test \ WebRoot \ WEB-INF \ lib ...

  • Hibernate connection pool configuration

    Hibernate connection pool configuration <! - Jdbc -> <property name="connection.driver_class"> oracle.jdbc.driver.OracleDriver </ property> <property name="connection.url"> jdbc: oracle: thin: @ 10.203.14.132:15

  • Learn Java flow

    Related Articles: J2EE without EJB Introducing to Spring Framework (English revised edition) J2EE without EJB caused consider Recommend circles: reading space More related recommend Java Learning Path (1), tools, articles First, JDK (Java Development Kit)

  • hibernate to use the principle of

    The use of hibernate, implementation of data persistence. Has the following several processes. One configuration database connection information. Hibernate.config 2 configuration mapping. 3 use: the use of the process are the following steps: 3.1: Ge ...

  • spring struts2.0 hibernate environmental structures .. despair carried out more than one hour only with good.

    http://www.qqread.com/java/2008/06/f413762.html Look here. . Note added myeclipse support spring when necessary add the commons-dbcp database connection pool package. And to add hibernate support. . Finally add struts2 support. . Oh the lazy point. . . fu

blog comments powered by Disqus
Recent
Recent Entries
Tag Cloud
Random Entries