Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December...

50
Configuring your solution with WebSphere Portal, WebSphere Application Server and WebSphere MQ December 2003 Configuring your Solution with WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version 1.0 Authors: Jennifer Heins Brent Miller Har Puri Sherry Shavor

Transcript of Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December...

Page 1: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Configuring your solution with WebSphere Portal, WebSphere Application Server and WebSphere MQ

December 2003

Configuring your Solution with WebSphere Portal, WebSphere Application Server, and WebSphere MQ

Document version 1.0

Authors:

Jennifer Heins

Brent Miller

Har Puri

Sherry Shavor

Page 2: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Contributors:

The author team would like to thank the following people who contributed their time, expertise, and review comments:

Kristen Balhoff, Michele Chilanti, Jeffrey Hoy, Steve Ims, Venkata Nagalla, David Ogle, Chris Parsons, Helen Rehn, Chin Sahoo, Lisa Speaker, and Ruth Willenborg

2

Page 3: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Contents Configuring your Solution with WebSphere Portal, WebSphere Application Server, and WebSphere MQ ........... 1

Document version 1.0 ................................................................................................................................ 1 Figure List................................................................................................................................................... 4

Introduction.............................................................................................................................................................. 5 Goal of this paper ....................................................................................................................................... 5 Conventions ............................................................................................................................................... 5

Configuration challenges......................................................................................................................................... 7 Specialized skills ........................................................................................................................................ 7 Varying methods of configuration............................................................................................................... 7

High level architecture view..................................................................................................................................... 9 Explaining the solution ............................................................................................................................... 9 Planning considerations ............................................................................................................................. 9

Common usage scenarios..................................................................................................................................... 10 eGovernment scenario ............................................................................................................................. 10 Mergers and acquisitions scenario........................................................................................................... 10 Stock purchase scenario .......................................................................................................................... 10 Simplified scenario ................................................................................................................................... 12

Overview of products............................................................................................................................................. 13 Operating system used ....................................................................................................................... 13 Products used ..................................................................................................................................... 13 Supporting products used or mentioned............................................................................................. 14 Portlets used ....................................................................................................................................... 14

Configuration activities .......................................................................................................................................... 15 Preparing your operating system ............................................................................................................. 15 Installing WebSphere Portal, including WebSphere Application Server.................................................. 17 Setting the WebSphere Portal Configuration Database........................................................................... 18 Configuring security.................................................................................................................................. 19

Authentication ..................................................................................................................................... 19 Authorization ....................................................................................................................................... 20

Updating the WebSphere Application Server for embedded messaging support.................................... 22 Install embedded messaging .............................................................................................................. 22 Run the sample setup scripts.............................................................................................................. 26

Administering portlets............................................................................................................................... 31 Special notes for installing MDBPortlet............................................................................................... 35

Configuring messaging............................................................................................................................. 36 Overall architecture ............................................................................................................................. 36 JMS configuration parameters ............................................................................................................ 39 Messaging troubleshooting checklist .................................................................................................. 40

IBM’s future configuration strategy........................................................................................................................ 41 Autonomic computing............................................................................................................................... 41

Overview of autonomic computing...................................................................................................... 41 Autonomic computing architecture...................................................................................................... 42 Integrated Solutions Console.............................................................................................................. 45

Summary ............................................................................................................................................................... 45 Authors .................................................................................................................................................................. 47 References ............................................................................................................................................................ 48

Page 4: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Figure List Figure 1 Inconsistent configuration data 8 Figure 2 WebSphere Portal, WebSphere Application Server, and WebSphere MQ solution 9 Figure 3 Topology of WebSphere Portal and WebSphere Application Server administration 11 Figure 4 Messaging sample portlet 12 Figure 5 Update WebSphere Application Server 23 Figure 6 Custom installation of WebSphere Application Server components 24 Figure 7 Installation of Embedded Messaging support 25 Figure 8 Installed Message-driven beans sample 26 Figure 9 Sample queues 27 Figure 10 Deployed MDBSamples application 27 Figure 11 Installing the MDB sample portlet 32 Figure 12 Confirming the MDBPortlet installation 32 Figure 13 Selecting the MDBPortlet portlet for Installation 33 Figure 14 Entering text on a portlet 34 Figure 15 Portlet with reply message 34 Figure 16 Overview of the messaging architecture 36 Figure 17 JMS providers 37 Figure 18 Messaging queues 37 Figure 19 Messaging with a topic 38 Figure 20 Migration to common configuration parameters 43 Figure 21 Example configuration property XML schema 44

4

Page 5: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Introduction

Goal of this paper Creating applications that provide a web front-end to a set of enterprise backend systems involves installing and configuring several products to work together. This paper examines the challenges when configuring a solution with WebSphere Portal, WebSphere Application Server (WAS), and WebSphere MQ. In this solution, we are using Portal to provide the web front end, WAS as the application server and WebSphere MQ to provide the messaging layer to the other enterprise back-end systems. In addition to providing helpful advice, this paper also describes IBM’s autonomic computing efforts with respect to configuration and how this work will make configuration easier in the future.

First, let’s define the term configuration. In this paper, the term configuration is used to refer to the setting of attributes of software product/components to run the application optimally in a given platform such as Windows, AIX or Solaris etc. This is typically done at the time of installation or post-installation. Configuration is often done by administrators who are setting attributes of application servers. Administrators need to configure resources such as memory, processes, threads, and connections, as well as deployment tasks, such as creating instances to meet operational or business objectives.

In this paper, we first examine some of the challenges in configuring solutions using WebSphere version 5 products including WebSphere Portal, WebSphere Application Server, and WebSphere MQ. For illustrative purposes, we will use a simple scenario that leverages the message driven beans sample that is shipped with WebSphere Application Server. Finally, we will look at IBM’s plans and strategies to make this easier.

This paper is separated into several sections to assist you with building an environment with WebSphere Portal, including WebSphere Application Server, and WebSphere MQ.

o Configuration challenges

o High level architecture view

o Common usage scenarios

o Configuration activities - including a working sample

o IBM’s future configuration strategy

Conventions This paper uses the following conventions to illustrate various types of information.

o Variables are shown in italics and/or within brackets <machine name>

o The following variables are used to indicate a default root installation directory:

o WebSphere Portal root installation directory: <wp_root> or wp_root AIX: /usr/WebSphere/PortalServer Linux and Solaris: /opt/WebSphere/PortalServer Windows: c:\Program Files\WebSphere\PortalServer\

5

Page 6: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

o WebSphere Application Server root installation directory: <was_root> or was_root AIX: /usr/WebSphere/AppServer Linux and Solaris: /opt/WebSphere/AppServer Windows: c:\Program Files\WebSphere\AppServer\

o Filenames, directories, and commands are shown in the following font and format and should be typed exactly as shown, including letter case.

Type this exactly – This command should be typed as though on a single command line. If part of the line is already present, do not type it. For example, the drive d :\> may already be displayed in the command prompt and there is no need to type it again. install.bat d:\

o To illustrate the file extension choices based on the appropriate operating system, the file extension will be within curly braces:

WPSconfig.{bat | sh} create-local-database-db2

6

Page 7: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Configuration challenges Through customer satisfaction surveys, customer engagements, analysis of service calls, and beta programs, we have collected data from customers about the complexity of configuring multiple software products that make up a solution. Often these solutions include WebSphere Portal, WebSphere Application Server, and a messaging system such as WebSphere MQ. Let’s briefly examine these configuration challenges.

Specialized skills The complexity of developing and deploying e-business applications in a middleware environment requires the use of many different technologies, such as portals, portlets, application servers, JNDI, JMS, JAAS, and JDBC. Each technology may require a specialized set of skills to use them. However, the following factors should be considered:

o The size of your company may limit the availability of these specialized skills.

o Diverse technologies place increasing strain on technical expertise.

o Specialized skills are increasingly difficult to obtain and maintain.

Large companies typically are staffed with administrators who have specialized skills. For example, skills often required include database administrators (DBA) and application server administrators. Each of these administrators is focused on one aspect of the solution rather than the deployment of the whole solution. As a result, specialized administrators may not see the whole picture and how configuring one aspect of the solution can impact another aspect. For instance, configuring your solution parameters to MQ may affect the performance of WebSphere Portal.

Small companies are typically structured with one administrator handling more than one area. This structure requires the administrator to have a broad breadth of knowledge in J2EE technology. Given the vast sum of technologies required to configure the solution, this is a tall order. Whether a company is small or large, the diverse set of technologies places a strain on technical expertise and makes these specialized skills increasingly difficult to maintain.

Varying methods of configuration The way you configure your solution greatly depends on the particular deployment scenario you are going to use and the products included. The default installation and configuration values provided are not always the best values to accept for your solution. One set of configuration values does not fit all solutions or all hardware specifications. WebSphere customers expressed this as one of the leading complexities of solution deployment.

In fact, in many enterprise environments, one set of configuration values is not enough. In some cases, businesses may slow down their systems at certain times for business and operational reasons. Therefore, systems need to handle changes to the configuration values.

Each product has its own configuration properties which are not necessarily consistent in terminology, data format, and administration interface. The underlying configuration data is product specific. Each product may store configuration information in its own format. Figure 1 shows an example of inconsistent configuration data. For example, configuring the location for the Java runtime is called JAVA_HOME in one product, JDK_PATH in another, and JAVA_DIR in yet another.

7

Page 8: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Figure 1 Inconsistent configuration data

The interface of application development tools may also be different from server interfaces used for administration. For example, application development tools use an Eclipse-based IDE with property pages for configuration, but the WebSphere Application Server products use a browser based administrative console with XML files for configuration. Other products use different types of administrative consoles. The section on IBM’s strategy for configuration will address what IBM is doing to gain consistency in specifying and administering configuration data.

To help work through these challenges this paper focuses on one scenario, but also provides pointers to other sources of information and provides a list of configuration activities. We hope the hints and tips provided in the Configuration Activities section, for configuring a solution based on WebSphere Portal, WebSphere Application Server, and MQ help make this task easier.

8

Page 9: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

High level architecture view

Explaining the solution This solution combines WebSphere Portal, WebSphere Application Server, and WebSphere MQ. WebSphere Portal serves as an interface to the back-end information. WebSphere Portal runs on WebSphere Application Server and WebSphere Application Server communicates through embedded messaging to WebSphere MQ. A user logs in via the WebSphere Portal interface and submits a request for information. The information request, or message, is placed on a queue for processing by the back-end system. If we are using the message listener service, the application handles the message and a reply is placed on another queue. A message driven bean listens for the reply and communicates the update to WebSphere Portal.

Figure 2 WebSphere Portal, WebSphere Application Server, and WebSphere MQ solution

Planning considerations When designing your solution, there are many architectural decisions you may need to make that will influence the configuration tasks you need to complete.

One important architecture point is how your application will handle security. What security methods will be used to protect access to the back-end resources? This will be addressed in more detail in the section, Configure Security.

9

Page 10: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Another important decision point is to understand how your solution will support the synchronous nature of the portal user interface with the asynchronous nature of the messaging system. For example, how long will your user interface wait for a reply. If a reply is not received within the specified time, how should the portal reflect this to the user? The messaging aspects are discussed in more detail in the section called, Configure for Messaging.

Common usage scenarios WebSphere Portal, WebSphere Application Server, and MQ work well together when building a unified, integrated Web interface to various legacy systems, where the access to information needs to be restricted. For example, an architecture may have various back-end systems that belong to different organizations such as different agencies within the US government. A usage scenario may be to create a set of portlets to leverage the various agency systems while providing the government employee a consistent web interface. Based on the role of the employee, the person will have access to a set of information. Another common usage scenario that will lead to a solution combining these three products is a merger or acquisition of two companies. For this paper, we include a more simplified scenario for illustrative purposes.

eGovernment scenario The IBM On-Demand Computing Solution Center implements many different scenarios as proof of concept demonstrations for customers. This center implemented a scenario showing how several different government agencies can collaborate and share data to improve their effectiveness. The scenario involved agencies located in different regions. It integrates role based authorization to private data and messaging services. That is, users are required to log in, and based on the role associated with their name, they are allowed to access or are denied access to data. The scenario involves a cargo ship coming into port. The port authority checks the cargo and alerts other government agencies such as the Emergency Management Agency and the Health Agency of its findings. Portlets are used as the interface to the various business systems that are accessed.

Mergers and acquisitions scenario The IBM System House organization prototyped a customer scenario involving insurance claims and quotes by a fictional company who has just experienced a merger. This involved various databases and transaction systems that were accessed as an integrated system with a Web interface. In this particular scenario, portlets were not used, but it did require the configuration of WebSphere Application Server to work with messaging products such as MQ.

Stock purchase scenario Another scenario for combining these products involves a customer who purchases stock. The customer access the portlet that allows the user to enter the data to submit the purchase request. The request is forwarded to the back-end systems for processing. The customer doesn’t wait to see the result, but logs on to the secure portlet later to view the results of the purchase action. Whether it is the purchase of stock or an online purchase of medicine or any other product, you can use Portal for your web front-end, the application server and MQ for the messaging layer to various back-end data repositories. As the web business grows, additional enhancements can be made to the front-end.

1 0

Page 11: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Regardless of the scenario, as you see in , there is configuration work that must be done to configure the portal administration and the application

server.

Figure 3 Topology of WebSphere Portal and WebSphere Application Server administration

Figure 3 Topology of WebSphere Portal and WebSphere Application Server administration

1 1

Page 12: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Simplified scenario For this paper, we include a more simplified scenario for illustrative purposes. Let’s begin with a simple scenario leveraging the samples that are installed with the WebSphere Application Server Embedded Messaging component. In this scenario, we created a new portlet that we added to the portal welcome page. This portlet is shown in Figure 4 Messaging sample portlet.

Figure 4 Messaging sample portlet

In the Messaging sample portlet, you are able to enter some text and press the submit button. When the text is submitted, it puts the text message on a queue. The queue is processed and a reply message is returned. The portlet is updated to display the response.

In this sample, we use the embedded WebSphere MQ as the JMS provider and the message driven bean sample that is supplied with WebSphere Application Server Enterprise edition. Leveraging this simple scenario, we can illustrate the basic configuration steps necessary to combine the WebSphere Portal interface with a messaging service in the back-end.

There are two types of messaging - point to point and publish / subscribe. This portlet example only deals with point to point messaging. As pointed out above, a full WebSphere Application Server Enterprise installation includes samples. The sample we are interested in is the Message Driven Bean (MDB) Point-to-Point messaging sample. It listens on a queue for an input message string and upon receiving one, echos the message to another queue.

In a more advanced scenario, we could introduce Enterprise JavaBeans (EJBs) to the architecture. In this case, the message driven bean listens for a reply and collaborates with the Enterprise JavaBean. The Enterprise JavaBean encapsulates the business logic, while the message driven bean encapsulates the asynchronous messaging. When a

1 2

Page 13: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

reply message is received, the information in the message is passed back through the Enterprise JavaBean to be reflected in the portlet. Though a more advanced scenario would typically involve several distributed machines, the basic configuration activities covered in this paper will still apply.

Overview of products Let’s look at the products and components referenced in this paper and understand why they are important to the solution.

Operating system used

Windows 2000 Server with Service Pack 3

Windows was used as the operating system for this paper, but other operating systems can also be used.

Products used

WebSphere Portal for Multiplatforms Version 5.0

WebSphere Portal is a J2EE(TM) application that runs on WebSphere Application Server Enterprise Edition v5.0.1. WebSphere Portal consists of middleware, applications (called portlets), and development tools for building and managing secure business-to-business (B2B), business-to-consumer (B2C), and business-to-employee (B2E) portals. A portal is a Web site that provides end users with a single point of access to Web-based resources by aggregating those resources in one place and by requiring that users log in only to the portal itself, and not to each portlet they use. WebSphere Portal can deliver Web content to WAP-enabled devices and i-Mode phones, as well as to various Web browsers.

WebSphere Portal serves as a simple, unified access point to Web applications, including valuable functions like security, search, collaboration, and workflow. WebSphere Portal serves as the Web interface, communicating through MQ, to back-end data in this solution.

Note: At the time of writing this paper, the WebSphere Portal 5.1 plans include deleting the WebSphere Application Server samples from the installation. Doing a full install of Portal does not imply installation of WebSphere Application Server samples.

WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1

IBM WebSphere Application Server is a J2EE1.3 compliant Web application server that provides J2EE services for the WebSphere Portal environment. It executes the Java portlets, JavaServer(TM) Pages (JSP) files, and Enterprise JavaBeans used by WebSphere Portal. This server product is the platform on which WebSphere Portal runs. Please note that version 5.0 fix pack 1 is required. WebSphere Portal version 5.0 will not run without the fix pack 1 and a few interim fixes for WebSphere Application Server.

WebSphere application server supports asynchronous messaging as a method of communication based on the Java Message service (JMS) programming interface. The support enables the exchange of messages by using JMS topics or queues.

1 3

Page 14: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

IBM WebSphere MQ Version 5.3

Optionally you may install WebSphere MQ as the JMS provider. Make sure you are using a compatible version of MQ with the messaging support provided with the application server. The application server enterprise edition includes copies of MQ with a restricted license. If you want to use the original WebSphere MQ 5.3 release without the restricted license, you may need to install the CSD01 update. See the IBM WebSphere Application server, Version 5: J2EE Resources documentation.

Supporting products used or mentioned

DB2 Universal Database Enterprise Edition Version 8.1 Fix Pack 1

DB2 Enterprise Edition is a Web-enabled relational-database management system. In the WebSphere Portal environment, Portal can store configuration, access control and user data in a DB2 database.

IBM Cloudscape

Cloudscape is a lightweight, Java-based embeddable object-relational database engine. By default, WebSphere Portal stores configuration, access control, and user data in IBM Cloudscape.

IBM Directory Server Version 5.1

IBM Directory Server is a Lightweight Directory Access Protocol (LDAP) directory that runs as a stand-alone daemon. WebSphere Application Server and Portal collaborate to store, update, and retrieve user-specific data related to authentication, such as user IDs and passwords.

IBM HTTP Server Version 1.3.26.1

IBM HTTP Server, powered by Apache, is a Web server based on the Apache Web server developed by the Apache Group (http://www.apache.org). The IBM HTTP Server includes several functions not available in the Apache Web server:

o Secure Sockets Layer (SSL) secure connections support o Dynamic content generation with FastCGI o Simultaneous installation of the IBM HTTP Server in multiple languages on all platforms o Web server LDAP authentication protection through an LDAP module

Portlets used

MDBPortlet portlet

In this paper, we use a portlet called MDBPortletPortlet, written by the author team and packaged in the MDBPortletLocalhostDirectLookup.war file.

The portlet creates an instance of MDBPortletPortletSessionBean. The session bean class contains the JMS code that creates the sender and receiver queues. This class references the JMS resources (queues and connection factory) created by the MDBSamples. The MDBPortletPortlet class and the MDBPortletPortletSessionBean class collaborate to send a message when the submit button is pressed and display the reply text.

1 4

Page 15: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Configuration activities Though this paper focuses on configuration, it also highlights a few installation “gotchas” you may face when installing these products. The installation and configuration steps we will follow are listed below and are described in the following sections.

1. Preparing your operating system by setting the appropriate values for the installation of the WebSphere products

2. Installing WebSphere Portal, including WebSphere Application Server

3. Configuring WebSphere Portal to use a larger, more scalable database for configuration data

4. Configuring security to ensure only those authorized and authenticated have access to the portal

5. Updating the WebSphere Application Server installation to include Embedded Messaging support

6. Portlet administration tasks including installing portlets and adding them to the appropriate Web page

7. Configure messaging resources by setting the JMS configuration parameters

Preparing your operating system Before you install WebSphere Portal, there are some preparatory tasks you should perform to ensure that your machine is ready for installation. Some of these tasks include checking user ID access rights and permissions, checking your network setup, planning for required disk space, and checking operating system level.

Configuration challenge

On Windows, we found that many users received the following message during WebSphere Portal installation. The WebSphere Portal installation program checks to see if the system logon user ID you specify has the proper access rights defined. If not, the installation program changes the settings for you and displays the following message.

EJPI0002E The specified user has insufficient rights. In addition to the administrator rights, the user requires the advanced user right "Act as part of the operating system" and the advanced user right "Log on as a service". To view or modify the user rights go to Start > Programs > Administrative Tools > Local Security Policy and double-click on Local Policies then double-click on User Rights Assignment. If you make any changes, log out and log back in to the system to make the updated changes. The installation has added the required permissions to the user; however, you must log out and log in to the system to refresh user rights.

If you see this message, you must cancel the installation program and log off and back on to your machine. However, to ensure the settings are correctly updated, it is recommended that you actually reboot your machine instead of just logging out. Then, restart the installation program. You do not have to manually change the settings because the installation program did it for you.

1 5

Page 16: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Working through this challenge

The following preparatory steps should be followed to avoid having to stop and restart the install program.

You must check that the system logon user ID that will be used during installation has the following permissions and rights:

o The user ID must already exist prior to installation.

o Must be a local Windows user ID that is in the Administrators group.

o Must have specific security access rights.

To determine if a user ID exists and is a member of the administrative group, perform the following steps:

1. Select Start > Programs > Administrative Tools > Computer Management

2. Expand Local Users and Groups and select Groups.

3. Open the Administrators group to see what members belong to it.

During the installation of WebSphere Application Server, you can choose to run WebSphere Application Server and IBM HTTP Server as services. In this case, you must provide the system logon user ID and password and the user ID must have the following security access rights:

o Act as part of the operating system: Windows designates this user right as a privilege for the user account.

o Log on as a service: Windows designates this user right as a logon right for the user account.

To determine if a user ID has the appropriate security access rights, or to modify access rights, perform the following steps:

1. Select Start > Programs > Administrative Tools > Local Security Policy.

2. Double-click Local Policies and then double-click User Rights Assignment.

3. Locate and open Act as part of the operating system to determine if this user right is enabled. If it is enabled, go to the next step. If it is not enabled, enable it.

4. Locate and open Log on as a service to determine if the user right is enabled. If it is enabled, go to the next step. If it is not enabled, enable it.

5. If you made any changes log off and then log on to activate the changes. It may be necessary to reboot the system to activate the required privileges.

For more information

The Windows help system provides extensive information about user rights and security options that are available. See the Windows help system for more information on setting user rights. Also, refer to [1], the WebSphere Portal InfoCenter: Installing, WebSphere Portal, and Preparing your operating system, for more information and additional guidance for other operating systems.

1 6

Page 17: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Installing WebSphere Portal, including WebSphere Application Server The WebSphere Portal installation program installs WebSphere Portal and its required components, including WebSphere Application Server Enterprise, IBM HTTP Server, and Cloudscape database. The installation program also performs basic configuration of WebSphere Application Server and other components.

Configuration challenge

We found that performing a full installation of WebSphere Portal, including a new instance of WebSphere Application Server, typically takes a few hours. This is due to the number of files being installed and set up on your machine.

Working through this challenge

The duration of installation can be shortened by following some of these guidelines:

o Install from a CD-ROM drive or a local copy of the installation files.

o Install on a high performing machine. The faster the processor and memory the quicker the installation will go.

Configuration challenge

We found it difficult to install WebSphere Portal over the network. The installation proceeded slowly or not at all. This of course depends on the server the images are on and the speed of the network.

Working through this challenge

It is highly recommended that you do not install over the network given the volume of files that are written. It is recommended for faster installations you choose one of the following methods of accessing the installation files:

o Install from the product CDs, in the machine’s CD-ROM drive

o Install from a local copy of the product CDs, copied to the hard drive

o Install from a remote copy of the product CDs, copied to a high performing remote server

Verify the installation

Once you have successfully installed WebSphere Portal and its required components, you can launch your portal and log in using the administrative user that was created during installation.

To launch your portal and log in:

1. Open a Web browser and go to the following URL: http://hostname.yourco.com:9081/wps/portal

2. Log in using the administrator user ID and password you enter during the installation.

For more information

Refer to [1], the WebSphere Portal InfoCenter: Installing, WebSphere Portal for more information and additional guidance for installing and configuring WebSphere Portal.

1 7

Page 18: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Setting the WebSphere Portal Configuration Database Once you have installed WebSphere Portal we recommend you do some additional configuration.

Configuration challenge

By default, WebSphere Portal stores configuration, access control, and user data in IBM Cloudscape. Cloudscape provides a small footprint, is self tuning, and ideal for solutions where the database must be hidden. However, Cloudscape may not be a large enough database for your environment. When clustering portal servers, you cannot use Cloudscape as a shared database for configuration data. Also, in many environments where WebSphere MQ is used, there may be existing databases that you want to use instead of Cloudscape.

Working through this challenge

WebSphere Portal provides scripts to transfer data from Cloudscape to another supported database. The example below shows you the high level steps involved in transferring data to DB2. Refer to [1], the WebSphere Portal InfoCenter: Installing, Database, and Configuring databases, for detailed information about transferring data from Cloudscape to another database.

To transfer data to DB2:

1.

2.

3.

Make sure DB2 is installed and setup. For this example, we are using a local copy of DB2 as our database.

Setup DB2 to work with WebSphere Portal. If you use a remote DB2 server, you must manually create the databases required by WebSphere Portal before transferring data from Cloudscape to DB2. If you use a local DB2 server, WebSphere Portal creates and sets up the required databases for you. In this case, we will assume a local DB2 server is used. Refer to [1], the WebSphere Portal InfoCenter, for information about manually creating WebSphere Portal databases on a remote DB2 server.

Configuring WebSphere Portal involves invoking a text editor to edit configuration values stored in a properties file called, wpconfig.properties. When you have completed editing the file, you should validate it using the WebSphere Portal configuration program file called, WPSconfig.{bat | sh}. Then, invoke the WebSphere Portal configuration program file again to actually run the configuration task. This program reads the configuration values stored in the properties file. The WebSphere Portal configuration program is used to transfer data from Cloudscape to DB2.

a. Enter your environment specific information in the <wp_root>/config/wpconfig.properties file using a text editor and save it.

b. To create the databases for our local DB2 server, issue the following command from <wp_root>/config: WPSconfig.{bat | sh} create-local-database-db2 Note: If you are using a remote DB2 database, ensure that your databases have been created and continue to the next step.

c. Enter the following commands to validate the information you entered in the properties file before transferring data. WPSconfig.{bat | sh} validate-database-connection-wps WPSconfig.{bat | sh} validate-database-connection-wmm WPSconfig.{bat | sh} validate-database-connection-wpcp WPSconfig.{bat | sh} validate-database-driver

1 8

Page 19: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

d. Enter the following commands to run the configuration task: WPSconfig.{bat | sh} database-transfer-import

e. Change to directory <was_root>/bin, and enter the following commands to start the WebSphere_Portal application server: startServer.{bat | sh} WebSphere_Portal

4. Verify that the WebSphere Portal application server is running by opening the following URL in a browser: http://<hostname.yourco.com>:9081/wps/portal, where hostname.yourco.com is the fully-qualified host name of the machine where WebSphere Portal is running and 9081 is the HTTP transport port created by WebSphere Application Server.

For more information

Refer to [1], the WebSphere Portal InfoCenter: Installing, Database for more information and additional guidance for installing, setting up, and configuring a database with WebSphere Portal.

Configuring security Security is important in all production environments. Therefore, we recommend you configure WebSphere Portal security to prevent unauthorized users from gaining access to any part of your Web site. WebSphere Portal supports various forms of authentication and authorization.

Authentication

Authentication refers to who is the user? This means that users have to identify themselves to gain access to the system. Users can identify themselves immediately upon entry to the system or they can be challenged by the system when they try to access a protected resource such as a portlet before identifying themselves. WebSphere Portal depends upon WebSphere Application Server for establishing the user’s identity. The user ID/password combination on a HTTP form is the most common method of identifying a user.

When configuring for security, you should consider the following questions:

1. What type of authentication management should be used? By default WebSphere Portal uses WebSphere Application Server to prompt users for identity. Alternately, the system can be configured for third-party authentication (via an external security manager such as Tivoli Access Manager (TAM)) or Secure Sockets Layer (SSL) Client Authentication for encrypted data between the browser and portal server.

2. What type of user registry will be used for authentication? A user registry holds profile information about registered users, groups, and available applications. WebSphere Application Server and WebSphere Portal support four types of user registries:

o Member Manager database

o Lightweight Directory Access Protocol (LDAP) accessible directories

o Custom User Registry interface: used to access non-LDAP user registries that are plugged into WebSphere Application Server authentication. The WebSphere Portal (WPS50) database is an example.

1 9

Page 20: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

o Third-party authentication using Trust Association Interceptors (TAIs). The third-party authentication provider determines the challenge mechanism and authentication method.

WebSphere Portal contains a component called Member Manager that can register users and groups and save profile information to a database. If your enterprise is already using an LDAP server, you can configure Member Manager to use it to authenticate a user. For more information, see the WebSphere Portal InfoCenter, Member Manager and Mapping LDAP attributes.

The authentication process flow starts with WebSphere Application Server. If the user is not found in the user registry, authentication fails. If the user is found, then the member services database is searched. If the user is found, then the portal login is successful. Otherwise, it fails.

S i n g l e s i g n o n a n d c r e d e n t i a l va u l t

When a user signs on to a portal or portlet, the authentication is done by the Application Server using the Java Authentication and Authorization Service (JAAS) API and optionally a third party authentication provider. The application server may be configured to use several third party authentication schemes.

WebSphere Portal stores the user ID and password for multiple resources that the user wants to access directly or through portlets in the credential vault. Each of these resources could have different userids and passwords. For example, in our scenario a portlet wants to access a back-end application. That access requires a user ID and password, which will be retrieved from the credential vault. The user ID and password to access the other resources could be globally shared, scoped to a user, or scoped to a specific portlet for a specific user.

How is the credential vault is used to achieve Single sign on? Once authenticated by WAS, the JAAS Security object can be populated with the credential vault slot id which contains the Credential object. There are active and passive credentials. Passive credentials allow a portlet to extract the userid and password to send to the back-end application. Active credentials do not allow a portlet to extract the credential's secret. However, active credentials can be sent to the back-end application to be used as is, provided the applications were written to use them.

Authorization

Authorization refers to what the user is allowed to do and see. This is sometimes referred to as access control. Authorization determines what interactions a user is permitted to have with resources like pages, portlets, and documents. Administrators configure access to portal resources by assigning roles to users and groups. Authorization can be controlled through the Users and Groups and Resource Permissions portlets and stored in the WebSphere Portal database by default. Alternately, you can configure an external security manager, such as Tivoli Access Manager, to protect resources. WebSphere Portal includes the following forms of authorization:

Role based access control

Roles are a set of permissions that determine what a group of users is allowed to do. The predefined roles are Administrator, Security Administrator, Delegator, Manager, Privileged user, and User. You can add users to roles and pick whether the permissions can be propagated or inherited.

Member Manager

Member Manager stores user profile information like users email address preferences and group membership. The member manager works in collaboration with the authentication mechanism. It stores the user profile and associated user data but not the user ID and password if WebSphere Application Server security is turned on. If WebSphere Application Server security is turned off, then Member Manager also stores the user ID and password. By default, Member Manager stores this information in the Cloudscape database, but it can be configured to use an LDAP server entirely or partially.

2 0

Page 21: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Configuration challenge

As stated above, there are many security options that can be configured with WebSphere Portal. One of the common configuration challenges is that WebSphere Portal stores user data in a Member Manager database, by default. However, your company may have an existing LDAP server storing user data that you want to use with WebSphere Portal.

Working through this challenge

WebSphere Portal provides scripts to configure Member Manager to use an existing LDAP sever to authenticate users. The example below shows you the high level steps involved in configuring WebSphere Portal to use an existing LDAP server, it is not intended to be a complete set of instructions. Refer to [1], the WebSphere Portal InfoCenter: Installing, LDAP, and Configuring LDAP, for detailed information.

To configure authentication with LDAP:

1. Make sure your LDAP server is installed and setup. For this paper, we are using IBM Directory Server.

2. Make sure there is an existing user who can also serve as the portal administrative user.

3. Create a user to use for portal administration.

4. The WebSphere Portal configuration program is used to configure communication between WebSphere Portal and LDAP.

a. Enter your environment specific information in the <wp_root>/config/wpconfig.properties file and save it.

b. WebSphere Application Server must be running and the WebSphere_Portal application server must be stopped to complete the next steps. Change to directory <was_root>/bin, and enter the following commands to start and stop the servers:

i. startServer server1

ii. stopServer WebSphere_Portal

c. Enter the following command to validate the information you entered in the properties file before configuration. Issue the following command from <wp_root>/config WPSconfig.{bat | sh} validate-ldap

d. Enter the following commands to configure authentication with LDAP: WPSconfig.{bat | sh} enable-security-ldap Note: These steps assume that you installed WebSphere Application Server when you installed WebSphere Portal. If you installed WebSphere Portal on an existing instance of WebSphere Application Server, these steps may be slightly different. Refer to [1], the WebSphere Portal InfoCenter, for more information.

e. Restart WebSphere Application Server and start the WebSphere_Portal application server. Change to directory <was_root>/bin, and enter the following commands to stop and start the servers:

2 1

Page 22: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

i. stopServer server1

ii. startServer server1

iii. startServer WebSphere_Portal

5. Verify that the WebSphere Portal application server is running by opening the following URL in a browser: http://<hostname.yourco.com>:<port_number>/wps/portal, where hostname.yourco.com is the fully-qualified host name of the machine where WebSphere Portal is running and port_number is the transport port created by WebSphere Application Server. By default the port number is 9081.

For more information

Refer to [1], the WebSphere Portal InfoCenter: Installing, LDAP for more information and additional guidance for installing, setting up, and configuring an LDAP server with WebSphere Portal. Also, refer to the Member Manager and Mapping LDAP attributes topics in the InfoCenter.

Updating the WebSphere Application Server for embedded messaging support Configuration challenge

When you follow the steps for a full installation of WebSphere Portal, WebSphere Application Server Embedded Messaging and the related messaging samples are not installed. This decision was made to reduce the default installation size.

Working through this challenge

Follow the steps below to install Embedded Messaging and related messaging sampes manually after WebSphere Portal is installed.

Instal l embedded messaging

1. On WebSphere Portal CD1-1 find the install program /cd1-1/was/win/Install.exe and start it.

2. Select a language and click Next.

3. Click Next on the Welcome panel.

4. Select I agree on the License panel and click Next.

2 2

Page 23: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

5. Select Add to the existing copy of WebSphere Application Server and then click Next.

Figure 5 Update WebSphere Application Server

2 3

Page 24: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

6. Select Custom to do a custom install and click Next.

Figure 6 Custom installation of WebSphere Application Server components

2 4

Page 25: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

7. On the feature selection screen, uncheck everything except the Embedded Messaging group. You may not be able to uncheck some items because they are already installed on your system. These items will appear grayed out.

Figure 7 Installation of Embedded Messaging support

8. Click Next when all Embedded Messaging is selected.

9. Select an installation directory and click Next.

10. On the summary panel click Finish to begin installation of Embedded Messaging. The installation should take 10 to 15 minutes.

11. When the server is restarted, you will have the embedded JMS support and the MDB sample installed.

2 5

Page 26: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Run the sample setup scripts

A normal WAS base install installs and configures samples. The sample we are interested in is the Message-Driven Bean (MDB) point to point messaging sample. It listens on a queue for a string and upon receiving one, sends the string back on another queue. To verify that the sample was installed, check the WebSphere Samples Gallery as shown in F . igure 8 Installed Message-driven beans sample

Figure 8 Installed Message-driven beans sample

2 6

Page 27: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

You also should verify that the Queue Connection Factory and queues were created. Open the WebSphere administration console and verify that the resources are there as shown in . Figure 9 Sample queues

Figure 9 Sample queues

To verify that the samples application was deployed to the WebSphere Application server, view the WebSphere Administration console as shown in . Figure 10 Deployed MDBSamples application

Figure 10 Deployed MDBSamples application

If you do not see the samples on your WebSphere administrative console after the Mesaging support and samples installation, you can manually configure them using steps 1 and 2 below.

1. To ensure that you have the JMS connection factories and queues created to run the MDBSamples, run the mdbSamplesSetup script. This script will create the Messaging queues and connection factory.

2 7

Page 28: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

a. To run the script change to the following directory: c:\Program Files\WebSphere\AppServer\util

b. From a command line run the script: c:\Program Files\WebSphere\AppServer\util>..\bin\wsadmin –conntype none –f mdbSamplesSetup.jacl <machine_name> You should see the following information on the screen. In this example dsra is the machine name.

C:\WebSphere\AppServer\util>wsadmin -conntype none -f mdbSamplesSetup.jacl dsra WASX7357I: By request, this scripting client is not connected to any server proc ess. Certain configuration and application operations will be available in local mode. samplesConfig: Configure MDB samples resources samplesConfig: Create JMS Queue Connection Factory samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Queue Connection Factory SampleJMSQueueConnectionFacto ry samplesConfig: Create JMS Queue samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Queue Sample.JMS.Q1 samplesConfig: Create JMS Queue samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Queue Sample.JMS.Q2 samplesConfig: Create JMS Topic Connection Factory samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Topic Connection Factory SampleJMSTopicConnectionFacto ry samplesConfig: Create JMS Topic samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Topic Sample.JMS.listen samplesConfig: Create JMS Topic samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Topic Sample.JMS.news samplesConfig: Create JMS Topic samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Topic Sample.JMS.sport samplesConfig: Create JMS Topic samplesConfig: Get ID for built in JMS provider for dsra server1 samplesConfig: Create JMS Topic Sample.JMS.weather samplesConfig: Create Listener Port samplesConfig: Get the Message Listener Service samplesConfig: Create Listener Port SamplePtoPListenerPort samplesConfig: Create Listener Port samplesConfig: Get the Message Listener Service samplesConfig: Create Listener Port SamplePubSubListenerPort samplesConfig: Create Queue Name samplesConfig: Get the JMS Server samplesConfig: Create Queue Name Sample.JMS.Q1 samplesConfig: Create Queue Name

2 8

Page 29: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

2. Start the samples by running the sample startup script, startMDBSamples.

a. To run the script change to the following directory: c:\Program Files\WebSphere\AppServer\bin

b. Run the sample startup script from a command line: c:\Program Files\WebSphere\AppServer\bin>wsadmin –f ..\samples\bin\MessageDrivenBeans\startMDBSamples.jacl – serverName server1 –nodeName <machine_name> You should see the following information on the screen. In this example dsra is the machine name.

C:\WebSphere\AppServer\bin>wsadmin -f ..\samples\bin\MessageDrivenBeans\startMDBSamples.jacl -serverName server1 -nodeName dsra WASX7209I: Connected to process "server1" on node dsra using SOAP connector; The type of process is: UnManagedProcess WMSG0400I: WebSphere Application Server Message Driven Bean samples setup script WMSG0402I: Connected to an unmanaged application server WMSG0421I: Setting the JMS server initialState to START WMSG0422I: Setting the initialState of the SamplePtoPListenerPort to START WMSG0411I: Setting the initialState of the SamplePubSubListenerPort to START WMSG0403I: Saving the configuration WMSG0408I: The Application Server must be restarted for the changes to take effect. Do you want to stop the Application Server? Enter the number associated with the following options: WMSG0409I: [1] Stop the Application server. WMSG0410I: [2] Don't stop the Application server. 1 WMSG0406I: Shutting down server WASX7337I: Invoked stop for server "server1" Waiting for stop completion. WMSG0404I: Server has shutdown. Please start the server. C:\WebSphere\AppServer\bin>startserver server1 ADMU0116I: Tool information is being logged in file C:\WebSphere\AppServer\logs\server1\startServer.log ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is 2752 C:\WebSphere\AppServer\bin>

2 9

Page 30: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

3. Important: There is a problem in this version of WebSphere Application Server. Usually the listener port gets created automatically as part of the script, but in this version of WebSphere Application Server it fails because of a last minute name mismatch. So, you have to set this manually. Refer to the documentation in C:\WebSphere\AppServer\samples50_fp1\readme.pdf for more information. In the above mentioned documentation, go to section 2.3 step 4 and create the listener port as described below.

a. In the Administrative console, expand the Servers and select Application Servers.

b. Select the server1 link.

c. Select the Message Listener Service link and then the Listener Ports link.

d. Click New and enter the following information in the appropriate fields:

i. Name: SamplePtoPListenerPort

ii. Connection factory JNDI name: Sample/JMS/QCF

iii. Destination JNDI name: Sample/JMS/Q1

iv. Maximum sessions: 5

v. Maximum retries: 10

vi. Leave all other fields with the default values.

e. Click Apply and then OK to save the new Listener port.

f. Click Save in the Message(s) box to open the Save to Master Configuration dialog box; then, click Save in the Save to Master Configuration dialog box.

4. Add another Listener port for SamplePubSubListenerPort. Although we do not use it for this demo, we must also create the SamplePubSubListenerPort as described in step 6 of the readme. This is because the MDBSamples will not start without it.

a. Click New and enter the following information in the appropriate fields:

i. Name: SamplePubSubListenerPort

ii. Connection factory JNDI name: Sample/JMS/TCF

iii. Destination JNDI name: Sample/JMS/listen

iv. Maximum sessions: 5

v. Maximum retries: 10

vi. Leave all other fields with the default values.

b. Click Apply and then OK to save the new Listener port.

3 0

Page 31: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

c. Click Save in the Message(s) box to open the Save to Master Configuration dialog box; then, click Save in the Save to Master Configuration dialog box.

d. Restart server1 by issuing the following commands from the c:\Program Files\WebSphere\AppServer\bin directory: stopServer server1 startServer server1

5. Make sure the MD sample application is started. Use the following steps to verify this.

a. Expand Applications and select Enterprise Applications

b. Click Next to go through the pages until you see MDBSamples with a green arrow next to it. If the MDB sample still has a red cross , check that the listener ports are active, they should have a green arrows next to them.

6. Restart server1 and WebSphere_Portal by issuing the following commands from the c:\Program Files\WebSphere\AppServer\bin directory: stopServer server1 stopServer WebSphere_Portal startServer server1 startServer WebSphere_Portal

7. Now proceed with the portlet configuration.

Administering portlets In this paper, we use the MDBPortlet to demonstrate administration. This section explains how to install a portlet and add it to a page.

To install a portlet:

1. Start the portal and select Login.

2. Type the portal administrator User ID and Password.

3. Select Administration in the banner.

4. Select Portlets in the navigation tree.

5. Select Install in the Portlets section of the navigation tree.

6. Browse for the WAR file in the directory in which the portlet is located. Note: The portlet must be stored locally in order for you to install it on the portal. You can download portlets from the Portal Catalog on the Web (http://www.ibm.com/websphere/portal/portlet/catalog), or you can use one you have developed.

3 1

Page 32: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

a. To run the message driven bean sample, select the MDBPortletLocalHostDirectLookup.war file.

Figure 11 Installing the MDB sample portlet

7. Click Next.

8. Verify that the portlet information that appears is correct.

Figure 12 Confirming the MDBPortlet installation

9. Click Install. After the installation has completed, a message should appear at the top of the screen indicating a successful installation.

To add a portlet to a page:

1. Click Log in.

2. Type the portal administrator User ID and Password.

3. Navigate to the page that you wish to add the portlet. In the sample, we will navigate to the Welcome page.

a. Select Portal User Interface > Manage Pages > My Portal > Welcome. Notice the pencil icon next to MyPage and select it.

3 2

Page 33: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

4. Select Add Portlets and page through the list to locate the appropriate portlet, in this case, MDBPortlet. Check (√) the box next to it and then select OK.

Figure 13 Selecting the MDBPortlet portlet for Installation

5. Select Done after you see the success message. You just finished adding the portlet to the Welcome page. Results: A portlet has been installed and added to a page. You can now locate and interact with the portlet.

6. Go to the Welcome page to see the portlet. Select MyPortal > Welcome. In this portlet, see , you are able to enter some text and press the submit button. When the text is submitted, it will put the text message on a queue. The message on the queue is processed and a reply message is returned and the portlet is updated to display the response as shown in

.

Figure 14 Entering text on a portlet

Figure 15 Portlet with reply message

3 3

Page 34: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Figure 14 Entering text on a portlet

Figure 15 Portlet with reply message

7. Verify that the portlet returned the string typed in.

3 4

Page 35: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Special notes for instal l ing MDBPortlet

Some helpful notes to get this simple scenario working on your machine:

o To make any configuration changes server1 must be running. To get the example to work for a base installation of WAS, your server1 MUST BE RUNNING because it is the only Java process that has an embedded JMS component. For a Network Deployment installation, jmsserver runs as a separate application server.

o Any configuration changes on the Portal server will not take effect until it is restarted.

o To uninstall a portlet - uninstall it from the manage applications screen and then restart the portal server. An application is automatically generated during the portlet installation and will prevent reinstallation of the portlet even if you delete the portlet war file. Remember to check that the MDB Application is deleted.

o To check if the Messaging subsystem is active check for these lines in the SystemOut.log for server1 [9/29/03 8:53:40:941 CDT] 2e41f17e JMSEmbeddedPr A MSGS0052I: Starting the Broker [9/29/03 8:53:58:629 CDT] 2e41f17e JMSEmbeddedPr A MSGS0053I: Broker open for business

o To check if the MDB sample queues are active check for these lines in the SystemOut.log for server1 [9/29/03 21:14:19:209 CDT] 10e1afad ResourceMgrIm I WSVR0049I: Binding SampleJMSQueueConnectionFactory as Sample/JMS/QCF [9/29/03 21:14:19:217 CDT] 10e1afad ResourceMgrIm I WSVR0049I: Binding Sample.JMS.Q1 as Sample/JMS/Q1 [9/29/03 21:14:19:222 CDT] 10e1afad ResourceMgrIm I WSVR0049I: Binding Sample.JMS.Q2 as Sample/JMS/Q2

For more information

Refer to [1], the WebSphere Portal InfoCenter: Administering your portal for more information and additional guidance on installing and administering portlets.

3 5

Page 36: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Configuring messaging Overall architecture

When designing your solution, there are many architectural decisions you will need to make that will influence the configuration tasks you need to complete.

Figure 16 Overview of the messaging architecture

The messaging configuration required is dependent on the architecture decisions that are made and require a solid understanding of JMS. The administrator interface is a thin veneer over the command line options available when configuring J2EE. The configuration considerations include:

1. How do you want to handle the message processing?

a. Explicit poll – will your application create Enterprise JavaBeans that have to explicitly poll message queues.

b. Message listener service – will you leverage the message listener services in WebSphere Application Server to listen for messages. This choice leverages message driven beans (MDBs) and JMS listeners and has the advantage of clearly separating your business logic from the message infrastructure.

c. Extended messaging – will you use the additional function provided by IBM for extended messaging including additional types of message beans and connection pooling. For example, you may select this option if the sender bean is not going to wait for an immediate response, but instead the response is considered deferred until the client using the sender bean decides to ask for the response. For more information about extended messaging see, [12] “WebSphere Application Server Enterprise version 5 Extended Messaging Tutorial, http://www.ibm.com/websphere/developer/registerd/tutorials/0303_cox/cox.htm #download.

2. Which JMS provider(s) will you use?

a. You need to specify whether you are using the embedded MQ provider that is packaged with WebSphere Application Server, or you may already have WebSphere MQ installed at your enterprise, and select the WebSphere MQ provider, or you may want to use a JMS provider by

3 6

Page 37: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

another vendor and select a generic JMS provider. A typical installation of a WebSphere Application Server includes a light version of the IBM MQ series server. You will also need to configure the JNDI parameters for lookup. Note that you can use the WebSphere Application Server Administrative console to configure the JMS provider resources, but to administer MQ security; you need to use WebSphere MQ. For more information on selecting the appropriate JMS provider, see [6] “Selecting the most appropriate JMS provider for your application”, by Jamie Roots.

Figure 17 JMS providers

3. What type of messaging will be used, point to point or publish / subscribe will indicate whether topics or queues need to be configured.

Point-to-Point

A message is consumed by only one receiver. A message is on the queue until it is consumed by a receiver or time expires. A receiver acknowledges the successful processing of a message. A sender and a receiver of a message have no timing dependencies. The receiver can fetch the message whether or not it was running when the client sent the message.

Figure 18 Messaging queues

3 7

Page 38: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Publish-Subscribe

Publishers and Subscribers are anonymous. They address messages to topics. The messaging system distributes the messages arriving from a topic's publishers to the topic's subscribers. A message could be consumed by more than one subscriber. In other words, each message may have multiple consumers. Publishers and subscribers have a timing dependency. A client that subscribes to a topic can consume only messages published after the client has created a subscription, and the subscriber must continue to be active in order for it to consume messages. This timing dependency can be overcome by using durable subscriptions. A durable subscription allows a subscriber to receive messages that were sent when it is not running. Durable subscriptions provide the flexibility and reliability of queues but still allow clients to send messages to many recipients. A durable subscription can have only one active subscriber at a time.

Figure 19 Messaging with a topic

If you decide to use publish / subscribe, you will also need to provide a broker to handle this. WebSphere MQ Event Broker or WebSphere MQ Integrator products provide this support.

Using the WebSphere Application Server Administrative console, you can define the queues for point to point messaging and topics for publish/subscribe messaging. The typical way to use messaging is to write a Message-driven bean (similar to stateless session bean) which contains the business logic to execute when called. Session and Entity beans allows J2EE applications to send and receive messages synchronously where as message-driven beans allow J2EE applications to process messages asynchronously. A message-driven bean is a message listener that can reliably consume messages from a queue or a durable subscription.

The MDB subscribes to the topic or queue and waits for a message to arrive. A client has to put a message on the queue. The client can be a Java, CICS, C or any other program that can put a message on the queue using its native API which for Java is JMS.

4. How will your Portal user interface reflect the asynchronous nature of the messaging system?

Keep in mind that messaging systems operate asynchronously and Web applications operate synchronously. If you place the Web application in a wait state until the message system completes the requested task, you could be in trouble because the messaging system doesn’t guarantee delivery within a specific time frame. As you architect this type of system, make sure you take into account that a message may take a long time to process or return with an error. A helpful technique may be to create a table, as in

, showing the possible messaging combinations and the interface you will show back through the portal. In this case, we are communicating with multiple back-end messaging systems which are likely to occur in the case of a merger or acquisition of two companies.

Table 1 Message reply combinations

3 8

Page 39: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Table 1 Message reply combinations

Message System 1

Valid Valid Valid Invalid Invalid Invalid No response

No response No response

Message System 2

Valid Invalid No response

Valid Invalid No response Valid Invalid No response

Outcome Customer provided info

Customer provided info

Customer provided info

Customer provided info

Customer informed thatit has not been possible to provide info at this time

Customer informed that it has not been possible to provide info at this time

Customer provided info

Customer informed that it has not been possible to provide info at this time

Customer informed that it has not been possible to provide info at this time

5. What tools will be used to develop the message-driven beans?

WebSphere Studio Application Developer (WSAD) provides integrated tooling to generate the code for the message-driven beans and test them. For more information, see the article, [7] “JMS Applications with WebSphere Studio version 5 – Part 3: Developing a publish-subscribe message-driven bean”, by Andy Wilkinson and [13] “Developing and Testing Message-driven Bean Applications with the MQ Simulator for Java Developers in WebSphere Application Developer Version 5.0” by Sheldon Wosnick.

6. How will the application developer communicate configuration information to the administrator?

It is recommended that the application developer create administration scripts to configure the various messaging configuration values. As done in the message driven beans sample, a JACL script file is included to set these values. An alternative, though more error prone, is to provide the administrator detail instructions on what needs to be set through the administrator console. To understand what needs to be configured, we will briefly examine the JMS configuration parameters.

JMS configuration parameters

1. Configure Connection Factories and Destinations

Given the JMS provider you selected, you need to configure the resources used to communicate with the messaging backend. If you chose the point to point architecture, you need to create a Queue connection factory and define the queue destination. A connection factory is used to create connections between the JMS provider and a specific JMS queue or topic. Each factory must have a unique name within the WebSphere Application Server administrative domain. If you chose the publish/subscribe architecture, then you need to create a Topic connection factory and define the topic destination. In the case of the MDBSample, you must create three resource references. The connection factory is Sample/JMS/QCF. The client uses queues named Q1 and Q2. In addition to defining the input queue, Q1, you also need to define the output queue or the one that is used for the reply, called Q2. In the MDBSample, the output queue named SampleOutputQueue is bound to Sample/JMS/Q2.

3 9

Page 40: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

2. Configure Listener Port You need to configure the listener ports for the message driven beans by using the WebSphere Application Server Administrative console and selecting: Servers > Applications servers > serverName > Message Listener Service > Listener Ports The definitions for the listener ports require you to enter values (Strings) for the Connection Factory JNDI name and the Destination JNDI name. These values must correspond to the values defined for the queue connection factory and destination queues on the WAS admin console Resources option. If not, the Listener Port definition is invalid and the start up of the MDB applications fails. In the case of the MDBSample, the MDB named PtoPSampleMDB is bound to the listener port named SamplePtoPListenerPort and queue named Q1. You can view this by selecting Enterprise Applications > MDBSamples > Provide ListenerPorts for Messaging Beans.

3. Configure JMS server

You need to make sure the configuration for the application server includes the location of the JMS server. Configure the connection factory properties to have the server name of your machine if you are running locally, otherwise if the server is running as part of a network deployment, and then use jmsserver. You should also enter the nodename. You can also do configuration using the clientConfig command from the command prompt.

4. Deploy Application on WebSphere Application Server

To install the application ear file, select Install new application from the admin console. Select the ear file to install. Stop and restart the application server. Remember that you always need to restart the server when you modify your JMS configuration parameters.

5. Performance Tune the Configuration

Once you have your application running, you will want to tune your configuration parameters for performance. The application server pools connections and sessions with the JMS provider to improve performance. To be able to configure your connection pool settings, we recommend you fill out the worksheets and follow the advice in the book, [3] “Performance Analysis for Java Websites” by Joines, Willenborg, and Hygh. Another good resource that illustrates tuning patterns is an article titled, [15] “The Go-ForIt quest continues, Part 7: Go-ForIt performance and capacity” by Marlon Machado. This aspect of configuration requires performance tuning skills and is dependent on the particular software and hardware in use.

Messaging troubleshooting checklist

If you are having problems getting your messaging to work, you may want to look into the following:

o Check that WebSphere Messaging function is installed

o Check that the JMS server has started. For a base installation, make sure that server1 is started as jmsserver is embedded with this server.

o Check that all JMS resources have been created and all references to them have been typed correctly (no misspellings)

o If security is enabled, make sure that the username and password is valid and exists in the security domain.

4 0

Page 41: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Futher configuration challenges

In this paper we focused on configuring Embedded Messaging on Windows, which is simpler because the WebSphere Application Server installation program creates an MQ user automatically. However installing MQ on UNIX platforms is moderately complicated. In particular, there are additional user IDs that need to be created manually and disk partitions that need to be sized appropriately.

For more information

Refer to [17], the WebSphere Application Server InfoCenter for additional details on configuring Embedded Messaging on UNIX platforms. Some of the topics you may want to review include, but are not limited to:

o Tips for installing the embedded messaging feature

o Installing WebSphere embedded messaging as the JMS provider

o Tips for troubleshooting WebSphere Messaging

IBM’s future configuration strategy The complexity involved in configuration management was addressed earlier. Complexity in today’s e-business solutions continues to be a system-wide concern for information technology users and administrators. IBM’s autonomic computing initiative is designed to address the complexity in today’s e-business systems by enabling those systems to be more self-managed, thus decreasing the administrative costs and burden.

Autonomic computing Overview of autonomic computing

IBM uses the term autonomic computing to describe systems that take on much of the burden of managing themselves, rather than requiring human administrators to attend to the many details associated with keeping an information technology system up and running in a safe, optimal manner. Autonomic computing is designed to act like the human autonomic nervous system, which regulates involuntary functions such as breathing, pupil dilation, heart rate, body temperature and so on, allowing humans to focus on higher-order tasks. Similarly, autonomic computing systems take on many mundane administrative chores, allowing administrators to focus on tasks with higher business value.

In [2] Autonomic Computing, IBM describes autonomic computing in this way:

Imagine a world where computers fix their own problems before you even know something is wrong. IBM is building that world with a range of autonomic computing capabilities across all of our product lines, helping you control an increasingly complex and expensive IT environment with computing systems that are self-managing, resilient, responsive, efficient, and secure.

4 1

Page 42: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

The self-managing aspects of autonomic computing include:

o Self-configuring: The ability to dynamically adapt to changing environments increases system responsiveness.

o Self-healing: The ability to detect and diagnose problems and act to prevent disruptions improves business resiliency.

o Self-optimizing: The ability to tune resources and balance workloads to maximize the use of system resources promotes operational efficiency.

o Self-protecting: The ability to anticipate, detect, identify and protect against attacks leads to secure information and resources.

IBM views autonomic computing as an evolutionary process, moving from highly manual processes to systems that can recommend administrative actions to systems that can take those actions on their own, according to business needs that are expressed as policies.

As described earlier, system configuration is at the root of several customer pain points. Self-configuring systems can help to alleviate some of this customer pain. Moreover, autonomic computing systems that can configure themselves can enable the other aspects of autonomic computing: self-healing, self-optimization and self-protection.

The IBM autonomic computing architecture, described next, includes configuration architecture that is intended to enable self-configuring autonomic systems.

Autonomic computing architecture

IBM’s autonomic computing architecture specifies a foundation for common data representation and operations that enable autonomic computing capabilities to be integrated into IBM products. In [10] An architectural blueprint for autonomic computing, a fundamental part of this architecture is described:

The autonomic computing architecture starts from the premise that implementing self-managing attributes involves an intelligent control loop. This loop collects information from the system, makes decisions and then adjusts the system as necessary.

One type of information that can be collected and adjusted in an autonomic computing system is configuration data. IBM’s autonomic computing architecture includes specifications for a common representation of configuration data and common operations that can be used to manage configuration information.

Figure 1 illustrated the problem of inconsistent configuration data, which points out the need for a common representation for this data. IBM’s autonomic computing configuration architecture addresses this requirement by specifying a common format for configuration properties, a canonical (that is, conforming to a specific set of rules) set of configuration properties, and standard operations used to manage these properties. This enables an intelligent control loop, called an autonomic manager, to collect system configuration data, make decisions based on an analysis of that data and adjust the configuration (or other aspects of the system) to achieve self-configuring, self-healing, self-optimizing and self-protecting goals for the system. illustrates this concept.

Figure 20 Migration to common configuration parameters

4 2

Page 43: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Figure 20 Migration to common configuration parameters

C o n f i g u r a t i o n p r o p e r t y a r c h i t e c t u r e

IBM’s autonomic computing architecture for configuration includes a common format for configuration properties, a canonical set of configuration properties and operations used to access and manage these properties.

The configuration property format uses an XML schema to define a common representation for configuration properties. Configuration properties are expressed as XML elements, with the schema defining the name, value and other attributes of the configuration property. An example of a configuration property definition is summarized in Table 2. Figure 21 contains a sample XML fragment that illustrates how such properties might be defined, using examples from Figure 20. (these properties would conform to a corresponding XML schema that is not shown). Note that the table and figure are illustrative only since IBM’s architecture for common configuration properties is still under development.

4 3

Page 44: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Table 2 Example elements of a configuration property

Configuration Property Element Description

Name Element name of the configuration property

Type Data type for the property value

Value Instance data for the configuration property

Units Units of measure for the property, if applicable

<configurationProperties name=”myConfiguration” type=”ConfigurationProperties”>

<homeLocation>C:\userdir</homeLocation>

<javaHomeLocation>C:\java</javaHomeLocation>

<adminServer>myAdminServer.ibm.com</adminServer>

<logMessageLevel>2</logMessageLevel>

<logLocation>C:\logFiles\myLogDir</logLocation>

</configurationProperties>

Figure 21 Example configuration property XML schema

A configuration property element such as that illustrated in Table 2 and Figure 21 is simple and straightforward. Each property has a name and type (the type could be a simpleType or complexType). Optionally, the property may specify its units of measure (bytes, seconds, and so on). When the property is instantiated in an XML document, the property takes on a value. Other aspects of configuration management must be addressed in autonomic computing configuration architecture, but these are outside the scope of this document. Configuration properties can extend a basic common property format such as the one just illustrated.

As described earlier, many products use different methods, representations, and names to represent similar information. A study of the configuration data associated with many products led to the identification of numerous configuration properties that occur frequently. These frequently occurring configuration properties have been categorized and distilled to a set of property names and associated data types. This canonical set of configuration data helps to ensure that the same configuration information is specified not only in a common format, but also with common property names and associated values, across products. For example, products today use numerous methods to represent paths and locations (files such as log files, documentation and so on). The autonomic computing configuration architecture describes a common way to specify the name of these configuration properties and their associated data types, so that the same property uses the same name in multiple products. Many other canonical configuration properties also are specified in the architecture. Although not all configuration properties can be specified in this manner (many product-specific configuration properties exist and will continue to exist), many can, and a canonical definition of these properties facilitates programmatic management of them.

The autonomic computing architecture also defines standard operations that the autonomic manager (illustrated in ) can use to query and set the configuration properties,

making use of the common format and content just described. For example, Web services interfaces can be used to retrieve and set configuration property values. An autonomic manager might retrieve a set of configuration properties that affect system performance and update those properties to tune the system. These standard operations, coupled

Figure 20 Migration to common configuration parameters

4 4

Page 45: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

with standard data representation and content, could allow autonomic managers to manage the configuration of multiple products and components in harmony with each other, rather than in an isolated fashion, thus improving the overall system’s self-management capabilities.

Integrated Solutions Console

The Integrated Solutions Console (ISC) enables common system administration. ISC is a portal-based technology that allows product administration portlets to be developed. These portlets are used within the ISC framework to provide a common look and feel for a single administrative console that can be used to administer multiple products. By providing one consistent administrative user interface across the product portfolio, ISC can help to address the challenge of administering product configuration data (as well as other aspects of product administration) from multiple consoles that was noted earlier.

A u t o n o m i c c o m p u t i n g a r c h i t e c t u r e d e p l o ym e n t

As stated earlier, the purpose of the autonomic computing architecture is to provide a foundation for introducing autonomic computing capabilities into IBM’s products. This process will occur over time in an evolutionary manner, proceeding toward more automated systems. IBM has already introduced many products with autonomic computing capabilities, including hardware (IBM eServerTM, ThinkPad® notebooks, IBM desktops, accessories, and IBM TotalStorage® products) and software (Tivoli®, Lotus®, WebSphere® and DB2® products). Detailed product information is available from the IBM autonomic computing Web site [2]. In addition, IBM offers an Autonomic Computing Toolkit that includes several IBM autonomic computing core technologies, such as the ISC, described earlier. The toolkit is available at IBM’s developerWorks Web site [19].

A major part of IBM’s autonomic computing architecture deployment involves open standards. The architecture is based on open standards such as XML, and IBM is playing a leading role in pursuing new autonomic computing standards through open standards bodies such as the Distributed Management Task Force (DMTF), the Organization for the Advancement of Structured Information Standards (OASIS) and others. Open standards allow our customers to integrate components from multiple vendors, and IBM believes that open standards are critical to the success of autonomic computing.

Summary It is difficult today to configure multi-product solutions because of the broad set of skills required. Administrators and application developers are required to have a solid foundation in many Java technologies. The lack of consistency in the configuration programs and data across the products compounds this problem.

This paper discusses some of the challenges customers face today as well as shows some of the steps involved in installing and configuring a solution with WebSphere Portal, WebSphere Application Server and WebSphere MQ. In summary, you need to:

1. Install WebSphere Portal, including WebSphere Application Server

2. Configure WebSphere Portal

a. Transfer configuration data from Cloudscape to DB2

b. Configure users and groups for authentication and authorization

3. Upgrade WebSphere Application Server to include Embedded Messaging support

4 5

Page 46: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

4. Configure WebSphere Application Server for messaging including:

a. Configure connection factories and destinations

b. Configure the JMS server

c. Tune the connection pooling parameters for performance

5. Add portlets

IBM’s on-demand strategy and the autonomic computing architecture address the complexity of configuration by designing systems that are self-configuring, self-healing, self-optimizing, and self-protecting systems.

Specifically, the autonomic computing configuration architecture includes:

o Common configuration property specification: the configuration architecture uses XML as a well understood method of expressing architecture that maps easily to implementations

o Automated configuration management: the configuration architecture enables programmatic management of product configuration data, which includes tracking the history of configuration values and automatically adjusting them when necessary. This helps to alleviate customer pain in product configuration administration.

o Solutions based on open standards: IBM’s autonomic computing architecture is helping to drive open standards for autonomic computing, including the common specification for configuration data. You benefit from open standards through their ability to integrate components from multiple vendors, thus protecting their information technology investments.

o IBM’s leadership role: IBM is producing the necessary architecture, technology, products, and offerings to make autonomic computing, including self-configuring systems, a reality today. You can realize the benefits of reduced administration complexity through self-managing systems that incorporate IBM products with autonomic computing capabilities.

This paper concludes with a list of references including a rich set of articles, Web sites, and books that the authors found helpful. It is our intent that this will help hone your search for configuration guidance.

4 6

Page 47: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

Authors

Jennifer Heins WebSphere Portal Information Development Architect Research Triangle Park, NC

Brent Miller Autonomic Computing Architect Research Triangle Park, NC

Har Puri Mid Market Runtime Development, Staff Software EngineerRochester, Minnesota

Sherry Shavor Senior Software Engineer Research Triangle Park, NC

4 7

Page 48: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

References WebSphere Portal InfoCenter, IBM Corporation, http://www.ibm.com/websphere/portal/library/ [1]

Autonomic Computing, IBM Corporation, http://www.ibm.com/autonomic [2]

Performance Analysis for Java Web Sites by Stacy Joines, Ruth Willenborg, and Ken Hygh, Addison-Wesley, 2003.

[3]

[4] IBM WebSphere Application Server v5.0 System Management and Configuration WebSphere Handbook Series, International Technical Support Organization, April 2003, SG24-6195-00, http://www.ibm.com/redbooks

System Administration for WebSphere Application Server V5 – Part 1: Overview of V5 Administration, by Leigh Williamson, IBM WebSphere Developer Technical Journal, January 2003.

[5]

[6] Selecting the most appropriate JMS provider for your application, by Jamie Roots, June 2003. G325-2318-00, http://www.ibm.com/redbooks

JMS Applications with WebSphere Studio version 5 – Part 3: Developing a Publish-Subscribe Message-driven Bean, by Andy Wilkinson, http://www7b.software.ibm.com/wsdd/library/techarticles/0307-wilinson/wilkinson3.html, August 2003.

[7]

Mergers and Acquisitions Scenario, System House, http://w3.systemhouse.raleigh.ibm.com [8]

[9] eGovernment Scenario, On-Demand Solution Center, http://integration.raleigh.ibm.com/odsc

An architectural blueprint for autonomic computing, IBM Corporation, http://www-3.ibm.com/autonomic/pdfs/ACwpFinal.pdf

[10]

The making of MetroSphere, Part 13: Install an existing Portlet, by Nicolas Chase, June 2003, http://www-106.ibm.com/developerworks/ibm/library/i-metro13

[11]

[12] WebSphere Application Server Enterprise version 5 Extended Messaging Tutorial, http://www.ibm.com/websphere/developer/registered/tutorials/0303_cox/cox.htl#download

Developing and Testing Message-driven Bean Applications with the MQ Simulator for Java Developers in WebSphere Studio Application Developer Version 5.0, January 2003. http://www7b.software.ibm.com/wsdd/techjournal/0301_wosnick/wosnick.html

[13]

MQ Series, http://www-3.ibm.com/software/ts/mqseries/library [14]

The Go-For It quest continues, Part 7: Go-ForIt performance & capacity, by Marlon Machado, August 2003, http://www-106.ibm.com/developerworks/ibm/library/i-2extreme7/

[15]

[16] Portal education materials developed by the Education Team at WebSphere Technology and Training, Rochester, Minnesota.

4 8

Page 49: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

WebSphere Application Server InfoCenter, IBM Corporation, http://www.ibm.com/software/webservers/appserv/was/library/

[17]

Online Prescriptions, by Alan Cohen, PC Magazine, August 2003 http://www.pcmag.com/article2/0,4149,1204843,00.asp

[18]

[19] IBM developerWorks, http://www.ibm.com/developerworks

4 9

Page 50: Configuring your Solution with WebSphere Portal, · PDF fileServer and WebSphere MQ December 2003 ... WebSphere Portal, WebSphere Application Server, and WebSphere MQ Document version

®

© Copyright IBM Corporation 2003 IBM United States of America Produced in the United States of America All Rights Reserved The e-business logo, the eServer logo, IBM, the IBM logo, OS/390, zSeries, SecureWay, S/390, Tivoli, DB2, Lotus, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries or both. Lotus, Lotus Discovery Server, Lotus QuickPlace, Lotus Notes, Domino, and Sametime are trademarks of Lotus Development Corporation and/or IBM Corporation. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries or both. Other company, product and service names may be trademarks or service marks of others. INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PAPER “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. Information in this paper as to the availability of products (including portlets) was believed accurate as of the time of publication. IBM cannot guarantee that identified products (including portlets) will continue to be made available by their suppliers. This information could include technical inaccuracies or typographical errors. Changes may be made periodically to the information herein; these changes may be incorporated in subsequent versions of the paper. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this paper at any time without notice. Any references in this document to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation 4205 South Miami Boulevard Research Triangle Park, NC 27709 U.S.A.