Search

Agricultural biomass and their bio-residuals always help to mitigate the stress on environment caused by synthetic products particularly in functional materials sector. This work was undertaken to utilize a lignocellulosic biomass Sesbania aculeata, a leguminous crop which is cultivated for green manuring purpose, later employed for extraction of a quality textile fibre through biological retting method from its stalks. S. aculeataproduced a green biomass of 387 quintal per hectare (q/ha), dry biomass of 50.5 q/ha, and produced 4 weights percentage of fibre over the weight of green plants. Moreover, the two months old S. aculeatagave the input of 143.9 kg/ha of nitrogen, 28.3 kg/ha of phosphorous, and 54.3 kg/ha of potassium to the soil. Physical properties revealed that extracted fibre was coarse due to high diameter with the density of 1.26 g/cc. Chemical, mechanical and thermal properties revealed that, the extracted fibre satisfied the desirable characteristics of a fibrous reinforcement for bio-composite development. Moreover, this crop would play a sustainable role as providing nutrient inputs to soil though green manuring along with finding a suitable place in the technical textile industries through its extracted fibre. Hence, promoting and exploring over this crop could help out in reducing carbon footprints and ecological hazards from synthetic fibres in the textile industry.

DB2 UNIVERSAL DATABASE (UDB) FOR Linux, Unix, and Windows version 8.2 supports many types of Java programs, including those used in client applications, in application servers, and in the DB2 […]

The phenomenon of globalization has unearthed a major question. With a huge market of non-English speaking customers, how can we facilitate communication to such a large subset of individuals without […]

JRas is a logging and tracing facility built into IBM WebSphere Application Server (WAS) that relies on JRas as its internal logging framework. Programmers can also leverage this powerful logging […]

The quest for increased application performance is a science in itself. IBM WebSphere Application Server includes a powerful caching technology called the dynamic cache service, which you can employ in […]

WebSphere Studio Application Developer, based on the Eclipse platform, is designed with the Java developer in mind. Extreme programming mandates that Java classes be unit-level tested in an automated fashion. […]

Portlets constitute interactive Web application components whose presentation markup is aggregated and displayed by a portal server like WebSphere Portal. In a previous WebSphere Journal article, we introduced you to […]

The Java Specification Request for the Portlet Specification (a.k.a. JSR 168), articulated by the Java Community Process in October 2003, aims to provide a standard for portlets that the portal […]

The Java Naming and Directory Interface (JNDI) is an Application Programming Interface (API) used to locate resources registered in the naming service of a Java 2 Platform Enterprise Edition (J2EE) […]

Reality check: your code likely exists beyond the confines of your cubicle. In today's world--made smaller via the marvels of modern society--it is likely that your code will transcend borders […]

In today's society, it's second nature to contact family, friends, and colleagues via e-mail. E-mail has become so integral to our daily ritual that we cannot slay away from it […]

We all have our preferences for how we like to have code formatted. Even when working in a team, you commonly see a myriad of coding styles. Manually formatting someone […]

This article presents information on WebSphere Portal Toolkit. The installation process will incorporate a scaled-down version of WebSphere Portal for local testing into WebSphere Studio Application Developer (WSAD). To do this, one has to provide the location for the WebSphere Portal 5.0 installer. One will have to insert WebSphere Portal CD 2 and use the Browse button to point to the location of wpsinstaller.jar on the CD. Complete the installation process, but be aware that it might take a while because it's installing an instance of WebSphere Portal on the machine. Upon invocation, WSAD will detect that there are a number of pending changes to the workbench that have to take place as a result of the WebSphere Portal Toolkit install. When asked to open the Update Manager, go ahead and do so. The Configuration Changes panel will show the changes that need to occur to the workbench. Click on Finish to carry out the changes. Restart the workbench for the changes made to take effect. WebSphere Portal Toolkit helps to create much of the framework code for portlets using wizards. After installing WebSphere Portal Toolkit, one can use it to develop portlets.

The article reports on a web portal. IBM WebSphere Portal 5 persists configuration data to a Cloudscape database by default. If your enterprise organization is large, you might want to consider a more scalable, manageable database, such as IBM DB2 Universal Database. Many enterprises have preferred database vendor products that their employees are trained to support, tune, and manage. WebSphere Portal lets you change the database that houses WebSphere Portal configuration data, which can be a simple task using the scripts that ship with WebSphere Portal.

The article focuses on the power of Macromedia ColdFusion FX with IBM WebSphere to give computer users rich, interactive content. In this article, the authors show how to use Macromedia Flash Remoting MX, so one can interact with the ColdFusion and Java objects created by the user. Later, one will see how to create an action script in a Flash document that will interact with the objects. Macromedia Flash MX lets designers and developers deliver rich interactive content to their users. Macromedia ColdFusion MX for IBM WebSphere lets user develop in both ColdFusion and Java, all the while leveraging the power of the J2EE platform. Macromedia Flash Remoting MX lets users communicate between Macromedia Flash and the Web application server. Users can build reusable Flash MX components that interact with applications built using Macromedia ColdFusion MX, Java, Microsoft .NET, and SOAP-based Web services. To understand the concepts portrayed in this article, users have a fundamental knowledge of the tandem relationship of Macromedia ColdFusion MX and IBM WebSphere Application Server.

This article shows how to apply a filter to a resource without ever having to modify the existing Web application. The Servlet 2.3 specification introduces servlet filters to J2EE development. A servlet filter is a component that is invoked when a client requests a resource, such as a URL pattern or a servlet name, to which the filter is mapped. One often use a filter to wrap and manipulate request, response, or header values before or after the original request target executes. One can add servlet filters transparently to Web applications and use these filters to add additional filtering to the request/response handling process. One can also use filters to do such things as convert content to different formats, record information about requests, or redirect access. One can apply the filter processing to the resources the servlet engine serves, including resources such as HTML files, Java Server Pages, and servlets. A filter code reports how long it takes to process an endpoint request.

This article focuses on portlet messaging that can make it easier for applications to interact with each other, creating a better and more efficient user experience. A demonstration has been made how the WebSphere Portal Toolkit Version 5.0.2 makes the incorporation of portlet messaging functionality into portal projects much easier. Portlet messaging involves a sending portlet and one or more receiving portlets. A sending portlet implements the ActionListener interface, which is required to implement the inherited abstract method named actionPerformed. The method captures an action event, which is processed by the sending portlet. A receiving portlet implements the MessageListener interface. Consequently, the portlet must implement the inherited abstract method named messageReceived. This method directs the message to the receiving portlet.

The article presents information on the Unified Modeling Language sequence diagrams. These diagrams illustrate class interactions, which are shown as exchanges of messages over time. In this article, the authors show how to generate sequence diagrams using WebSphere Studio Application Developer's (WSAD) Java Profiler. A Java application whose execution occurs in a single Java Virtual Machine (JVM) uses the Java Profiling Agent. The agent hooks into the JVM where the application runs so the user can see all the interactions that occur in the JVM. This, of course, might be information overload; he can use filters on the information if he only wants to see certain classes and objects in the sequence diagram analysis. If, however, the user is dealing with more complex distributed deployments, he can use the J2EE Request Profiler. The J2EE Request Profiler gathers information from request interception points. After the user acquires the data from these different interception points, he gets a sequence diagram that takes into account the various distributed players of the setup. Note that only the WebSphere Application Server 5.0 runtime environment supports application monitoring that leverages the J2EE Request Profiler.

The article presents information on the speed portlet development with IBM WebSphere Portal Toolkit 5.0.2. The IBM WebSphere Portal Toolkit provides graphical wizards that can speed the process of building, testing, and deploying new portlets. WebSphere Portal Toolkit also makes it easier for the user to learn about many of the WebSphere Portal API's components. WebSphere Portal Toolkit also includes a test environment that the user can use to run and debug portlets, which saves him from the laborious process of having to export and deploy to a full-fledged portal server every time he makes changes to the portlet. WebSphere Portal Toolkit plugs into WebSphere Studio Application Developer (WSAD) 5 or WebSphere Studio Site Developer 5. The Resources sidebar at the end of this article includes a link to the WebSphere Portal Toolkit 5.0.2 Installation Guide. One can install WebSphere Portal Toolkit with either a local or remote debug development environment. The local development environment lets the user use a scaled-down version of WebSphere Portal Server running in WSAD.

This article presents information on Concurrent Versions System (CVS), a powerful and cost-effective software configuration management system. CVS is a free tool that lets the user share files in a controlled, centralized repository. The repository provides a place for programmers to collaborate with other team members. CVS also lets the user go back to previous versions of software artifacts if you decide a rollback is necessary. CVSNT installation is rather straightforward. During the installation, choose the "Typical" installation. The installation gives the user the option to install various protocols. Some of these protocols let the user share his files over secure connections, which is required to work with team members remotely. The user can configure the CVS Server Ports from the Advanced tab. For geographically dispersed development teams, the CVS administrator will have to work with the network administrator to configure the firewall properly. The beauty of the client-server CVS access methods is when it's set up properly, the user can communicate between the CVS repository and client workbenches over local and wide area networks for remote development.