milonz (mylesjohnson)'s Public Profile in the Diigo Community

More »

Tags

Recent Tags:	websphere(0), spring(0), websphere-deploy(0), vaccination(0), java(0), autism(0), ubuntu(0), log4j(0), install(0), funcspec(0), uml(0), jms(0), hibernate(0), orm(0), ubuntu-networking(0), logging(0), debug(0), formbackingobject(0), axis2(0)
Top Tags:	websphere(8), spring(11), vaccination(4), websphere-deploy(4), autism(3), java(5), hibernate(2), jms(2), uml(2), orm(2)

More »

Recent Bookmarks and Annotations

Of the world's 100 largest economic entities, 51 are now corporations and 49 are countries (2000) on 2008-05-18
Chapter 19. JMS on 2008-05-18
- JMS 1.0.2
  and 1.1 API
Jarhoo on 2007-10-28
Unable to mount smbfs using mount from command line (gnome connect to server works) [Archive] - Ubuntu Forums on 2007-10-25
- sudo mount -t smbfs -o username=$username,password=$password,uid=$UbuntuU sername,gid=$Ubuntuusername //$serverip/$sharename /mnt/fileserver
IBM WebSphere Portal (2006 - Articles, Tutorials) on 2007-10-22
O'Reilly - Safari Books Online - 0738498513 - IBM WebSphere Portal V5 A Guide for Portlet Application Development on 2007-10-22
- 2.6. Portlet deployment
  When a portlet is installed into the portal server, the deployment information is contained in two deployment descriptors. The Web.xml deployment descriptor is used by the WebSphere Application Server to register the portlets being deployed. The application server is not aware of the portlet hierarchy and is simply installing a Web application containing servlets. The portlet.xml deployment descriptor is used by the portal server to retrieve parameters and to set the initial configuration.
  When the portlet application is deployed, it is deployed as a Web archive (war), not an enterprise application (ear). When the war file is deployed, the portal server actually creates an associated ear folder in the WebSphere\AppServer\installedApps directory. The new ear folder will contain the original name of the war file with _WPS_PA_191.ear appended to the end of the name of the war file. The last number indicates the order in which the portlet application was installed.

Building SOA composite business services, Part 6: Automate build and deployment steps on 2007-10-22

However, many of these build and export steps in Rational Application Developer and Websphere Integration Developer, as well as deployment steps in WebSphere Portal Server and WebSphere Process Server, are manual GUI point-and-click steps. In this article, you'll learn how to automate these manual steps.
- WebSphere Portlet Factory Ant scripts for packaging portlets into WAR files
- earExport for packaging Web services and EJB components into EAR files along with dependent JAR files
3 more annotations...

Listing 4. Exporting a WebSphere Portlet Factory portlet Eclipse project into a WAR file

				
<target name="exportWPFWar" depends="importAllProject">
   <ant dir="${src.portal}/J2BWPFPortlets/WEB-INF/bin/deployment/jsr168" 
             antfile="${src.portal}/J2BWPFPortlets/WEB-INF
             /bin/deployment/jsr168/build_deployment.xml">
       <property name="output.location" value="${dist}"/>
       <property name="rootDirectory" value="${src.portal}/J2BWPFPortlets/WEB-INF"/>
       <property name="warfile" value="J2BWPFPortlets.war" />
       <property name="webxmlFile" value="./web.xml" />
   </ant>
	.
	.
</target>

Portal themes and skins are often used to provide a unique look for portals belonging to different enterprises (Resources for a link to "Deploying Customized Themes and Skins"). You can deploy portal themes and skins automatically using Ant, as Listing 11 shows.

Listing 11. Deploying themes and skins into the WebSphere Portal Server using Ant scripts

				
<target name="checkout" unless="USE_CVS">
<svn> 
    <checkout url="${urlRepos}/installation/InstallationFiles/ThemesSkins" 
         destPath="${temp}"/>
</svn>
</target>
	
<target name="copyThemesSkins" depends="clean" >
<copy todir="${destTheme}/SasBankBank1AdminTheme" overwrite="true">
	<fileset dir="${temp}/SasBankBank1AdminTheme" />
</copy>
<copy todir="${destTheme}/SasBankBank1Theme" overwrite="true">
<fileset dir="${temp}/SasBankBank1Theme" />
</copy>
<copy todir="${destTheme}/SasBankBank2Theme" overwrite="true">
	<fileset dir="${temp}/SasBankBank2Theme" />
</copy>
<copy todir="${destSkin}/SasBankBank1Skin" overwrite="true">
	<fileset dir="${temp}/SasBankBank1Skin" />
</copy>
<copy todir="${destSkin}/SasBankBank2Skin" overwrite="true">
	<fileset dir="${temp}/SasBankBank2Skin" />
</copy>
</target>

During the automated build process, portlets are exported into WAR files. You use the WebSphere Portal Server XML configuration interface to deploy portlets and configuration for portlets. This interface expects to find the portlet WAR files in the subdirectory installableApps of the WebSphere Application Server installation directory. You use the Ant script in Listing 12 to place the portlet WAR files in the appropriate directory.

Listing 12. Ant scripts to place the portlet WAR files in the appropriate directory

				
<property name="portalServer" value="Z:\sas\PortalServer"/>
<property name="portalInstallable" 	value="${portalServer}/installableApps"/>

<target name="unZipPack">
	<unzip src="${basedir}/JivaroBankingV2.zip" dest="${temp}/war">
		<patternset>
			<include name="**/*.war"/>
		</patternset>
	</unzip>
</target>

<target name="copyWarToPortal" depends="unZipPack">
	<copy todir="${portalInstallable}" overwrite="true">
		<fileset dir="${temp}/war" />
	</copy>		
</target>

IBM WebSphere Portlet Factory delivers new portlet development capabilities on 2007-10-22
- WebSphere Portlet Factory is a dedicated portlet development environment for rapidly creating,
  customizing, deploying, and maintaining portlets that leverage existing enterprise applications,
  databases, and other IT assets.
- Automated deployments
  
  — Automatically deploy and redeploy portlet war files to WebSphere Portal — without having to
  touch ant scripts or XML deployment descriptors
Leveraging WebSphere Portal V6 programming model: Part 5. Accessing portal content with custom URLs on 2007-10-22
- The latter approach facilitates development work because it does not require server restarts to update a resolver; you can simply redeploy the WAR file.
Leveraging WebSphere Portal V6 programming model: Part 1. Managing portlet configuration using the edit_defaults mode on 2007-10-22
- Portlet configuration and file-based stores
- In stand-alone Java programs, this sort of configuration is often stored in the file system, typically using properties files
- 6 more annotations...
- - For Web applications, particularly portlets, this sort of configuration storage has two major drawbacks:
  - For example,
  - these considerations do not apply to “static” configuration, such as that determined only by the programmer
  - the configuration for application frameworks, such as Struts or Spring
  - You can package those configuration files inside the portlet WAR, and then load them using PortletContext.getResourceAsStream.
  - An update to the configuration effectively constitutes an update of your application version, and requires re-deploying the WAR file. The deployment mechanism ensures that the update is distributed to all cluster nodes.

More »

Bookmark Lists

Spring

More »

Groups

Milonz havn't joined any group yet.

milonz 's Profile

More »

Tags

More »

Recent Bookmarks and Annotations

2.6. Portlet deployment

More »

Bookmark Lists

More »

Groups

Me elsewhere

milonz 's Profile

More » Tags

More » Recent Bookmarks and Annotations

2.6. Portlet deployment

More » Bookmark Lists

More » Groups

Me elsewhere

More »

Tags

More »

Recent Bookmarks and Annotations

More »

Bookmark Lists

More »

Groups