WebSphere Portal v6
Transcript of WebSphere Portal v6
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
Working Draft Last Modified 17.01.2008 16:28:27 Central Europe Standard Time
Printed 13.09.2006 14:10:11 Central Europe Standard Time
CONFIDENTIAL
WebSphere Portal v6
Software Platforms Management
Document
Jan 2008
This report is solely for the use of client personnel. No part of it may be circulated, quoted, or reproduced for distribution outside the client organization without prior written approval from McKinsey & Company. This material was used by McKinsey & Company during an oral presentation; it is not a complete record of the discussion.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
2
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Agenda
Topology
Configuration
Administration
Troubleshooting
Q&A
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
3
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
WebSphere Portal Topology
Please refer to the Visio diagram below
Topology of WebSphere Portal is included in Visio diagram bellow -> WPS Topology
WPS Topology
Topology explanation:
1. Servers hosting WPS are amdc-wps-ux01/022. There is Apache instance on each of them responsible for communication between users and JVMs3. Those servers are in the prdCluster of WebSphere Application Server Network Deployment4. WPS uses 2 different databases, one located on local hosts Cloudscape instance, second on am-oradbprod-ux02 WPS
schema
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
4
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Configuration
*Footnote
Source:Team analysis
WebSphere Application Server Security for Portal
1. WebSphere Portal relies on WAS security settings.2. Global security should be enabled before actual WPS installation process 3. WAS security for WPS is based on ITDS – IBM Tivoli Directory Server 4. Enabling WAS Security ->
Enabling Global Security on WAS for WPS
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
5
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration
WebSphere Portal Administration portlet is available under the following link -> http://amdc-wps-ux01/wps/myportal/AdministrationPlease login as wpsprdbind – admin user.
You might be redirected to the KNOW page. Administration link can be found above search field
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
6
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration
WebSphere Portal is a bunch of components (portlets) that have various responsibilities. If you have followed to administration link and successfully logged in, you should see page looking like below (this is administration portlet)
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
7
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration
Let’s focus on Launch button located on the very top left hand side
Home – this will take you to the homepage which is mapped to know.welcome
Administration – You will be redirected to the main admin page
News – News is not used in our environment it contains e.g. info about stocks, wether, etc.
Documents – provides versioning, organizing, editing etc. capabilities but is not used by McK
Web Content – content management portlet, simillar to any CMS
Messaging – Not used by McK but provides wide range of possibilities including real communication
Domino Integration – Not used by McK
Personalization – Helps to create and manage business rules e.g. different content for different users
Templates –
Search – built in search engine and crawler
Site map – site map
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
8
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – WCM Web Contet Management
Web Content Management technology is included with WebSphere Portal Express by default, including support for syndication and rendering portlets. To get to the WCM click on Launch button and select Web Content. Than select Web Content Management
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
9
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration - WCM Web Contet Management
Here you can create, modify, view and edit static content. WCM portlet gives you renderring capabilities. It means that anything you create will get processed and appear in the assigned place. For this you should use action buttons.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
10
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Personalization portlet - PZN
PNZ portlet offers creation of business rules. This allows to show different content to different users. In the result you can setup rules to show or restrict some information depending on user’s location, position in the company etc. For access click Launch button and select Personalization.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
11
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Personalization portlet - PZN
Here you can add modify or view rules.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
12
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview
Manage Pages – export, create, edit, activate, order and delete pages. Manage exterrnal Web pages and labels.
Themes and Skins – install, delete, edit themes and skins
Web Modules – Install, update, assign access, start application
Applications – Configure, assign access, deploy application WAR files
Portlets – view and configure portlets
WebServices – Web Clipping – identify, extract portion of document for displaying in the portlet
Users and Groups – search, edit, delete existing users and groups
Resource Permissions – set and assign access roles for users and groups.
User and Groups Permissions – assign, view and modify roles and rights
Credential Vault – Resource Policies – manage and view policies for resources adminstration
Global Settings – define what users sees in WPS including language.
URL Mapping – create and manage user friendlu URLs and map them to the pages
Custom Unique Name – assign Unique names for porting resources between portals
Supported Markups – add, edit, delete, determine which markups are recognized
Supported Clients – add, edit, delete, determine which types of devices can access
Import XML – import, export operations e.g. page to xml and move to other instance
Document Libraries – configure versioning, workflows, document locking
Web Content Libraries – add, edit, delete Web content libraries to manage content
Syndicators – create, edit, delete syndicators used to replicate content between WCM
Subscribers – create, edit, delete subscribers used to replicate content between WCM
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
13
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
The Manage Pages portlet allows you to export page configurations in XML, create, edit, activate, order, and delete pages as well as external Web pages and labels. Available tasks depend on which item is selected. Each page can contain multiple pages.
Portal structureThe portal is composed of a hierarchical structure of nodes that can be represented in a parent-child relationship, starting from the content root of the portal. A node is an addressable element in the portal navigation tree belonging to one of the following types:page• Pages display content in the form of portlets. Pages can contain child nodes, including other pages that
provide content. A page can contain column containers, row containers, and portlets. Containers are columns or rows that you can use to arrange the layout of portlets or other containers on the page.
label• Labels do not display any content, but can contain other nodes. They are used primarily to group nodes in
the navigation.URL• URLs can launch any URL-addressable resource, including external Web sites or pages within the portal
site.Nodes are located in a level of the navigation hierarchy relative to the parent node in which they are created. The topmost node in the tree is the content root. After installation, the following nodes are created under the content root. This is only a partial list.Home • A label containing the Welcome and Getting Started pages. By default, this is the first page displayed after
login.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
14
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Administration • A label containing pages with portlets used by portal administrators. A link is provided on the Welcome
page and also in the Main Menu to allow users with administrative privileges to access this content. • Embedded product site areas• These labels are children of content root. They contain pages and portlets that relate to specific functions
or products available in portal. They are peers of the Home and Administration labels, and they are accessible via the Launch Main Menu icon in the portal theme. Each site area contains a Welcome page that describes the function or product as well as one or more content pages that show the function or capabilities of the site area. Examples of the site areas that are shipped with portal are: News, Documents, Messaging, Domino Integration, Personalization, Search, and Templates.
Utility pages• These pages are hidden from the portal navigation and not rendered in the theme. They are accessed
programmatically by explicitly creating URLs to call them, for example through page context menus to edit page properties or layout. Some commonly used utility pages are:
• Page Customizer– A label containing child pages with portlets for manage page content and layout. Direct access to this
node is hidden from navigation. Instead, the portlets in the page customizer are accessed through the page menu available on the tab. To see the drop-down menu, place your mouse pointer anywhere on the tab.
• Page Properties– A page containing the Properties portlet, used for editing the properties of a page, such as locale-specific
titles and description. This page is always hidden from navigation. It is accessed through the Manage Pages portlet in Administration or from the drop-down menu on the page tab. To see the drop-down menu, place your mouse pointer anywhere on the tab.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
15
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Creating pagesTo create a new page, perform the following steps:Click Administration from the main menu. Click Manage Pages directly from the navigation. Click New Page to create a new page. You will leave Manage Pages to create the new page. Type the title of the new page in Title. This is the title for the default locale. Select Theme to determine the look of the new page. This option is available only on a level 1 or 2 page. If you want to allow this page to be bookmarked by other users, check This page can be added to a user's
My favorites list. If a user bookmarks this page, it will be available from My favorites in the banner. Check Other pages can share the contents of this page if you want the contents of this page to be shared by
others. If checked, users can reference this page when they create a new page. For Type of page, select one of the following: Cache scope • If the page is shared among multiple users, selecting Shared cache across users provides the best
performance.Cache Expiration • Use this option to set how long, in seconds, the cache is used. Selecting Cache never expires means
that content will always be retrieved from the cache. Cache Access Control • By default, the portal does not permit shared caching for authenticated pages. Checking Ignore access
control in caches overrides this behavior. However, this could allow an anonymous and potentially malicious user to access secure content from that page.
Click OK to save these settings for the new page and add new content. Click Cancel if you want to return to Manage Pages without creating the new page.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
16
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Creating a labelTo create a new label, perform the following steps:Click Administration from the main menu. Click Manage Pages directly from the navigation. Click New label to create a new label. You will leave to create the new label. Type the title of the new label in Title. This is the title for the default locale. Select Theme to determine the look of the new label. Note: This option is only available when creating a root
page. Continue to the next step to set advanced options. If you do not want to set advanced options, click OK to
save the new label or Cancel to discard the label settings and return to . Click Advanced options to view optional settings in this section. Check supported markup from This page supports. Note: You must select at least one supported markup to
create the label. The default is HTML. Click OK to save these settings for the new label. Click Cancel if you want to return to without creating the
new label.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
17
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Creating a URLTo create a new URL, perform the following steps:Click Administration from the main menu. Click Manage Pages directly from the navigation. Click New URL to create a new URL. You will leave Manage Pages to create the new URL. Type the title of the new URL in Title. This is the title for the default locale. Select the type of URL. You can create an internal or external URL. • For internal URLs, select A link to the following portal page. Internal URLs direct the user to a page
within the portal site. You can select only from pages that are bookmarkable. Also, you cannot create a URL to a top level page. Instead, you must select one of the available child pages.
• For external URLs, select A link to a Web page with the following URL. External URLs direct the user to a location outside of the portal site. Select at least one markup, such as HTML, and the URL for that markup type.
Click OK to save these settings for the new URL. Click Cancel if you want to return to without creating the new URL.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
18
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Ordering pages, labels, and URLs
When you reorder items listed in Manage Pages, you are changing the order of pages, labels, and URLs on the site. You are also changing the order of entries in the main menu.
To reorder pages, URLs, and labels, perform the following steps:Click Administration from the main menu. Click Manage Pages directly from the navigation. Click the Move an item up icon to move an item up one row in the table. Click the Move an item down icon to move an item down one row in the table.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
19
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Assigning access to pages, labels, and URLs
To assign access, perform the following stepsClick Administration from the main menu. Click Manage Pages directly from the navigation. Navigate to the page, label, or URL to which you want to assign or modify access. Click the Set page permissions icon to change permissions for the resource.
Activating or deactivating a page, label, or URL
You must activate it before you or other users can view the resource
To activate or deactivate a page, label, or URL, perform the following steps:Click Administration from the main menu. Click Manage Pages directly from the navigation. Navigate in the table or use the search option to locate the page, label, or URL that you want to make active
or inactive. Click Activate to activate the page or Deactivate to deactivate the page.
Note: You may be prompted to confirm this change.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
20
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Manage Pages
Deleting pages, labels, and URLs
By deleting pages, labels, and URLs, you can remove content and change the site navigation.
To delete pages, labels, and URLs, perform the following steps:
Note: Once a resource is removed, it cannot be restored. All user settings are lost.
Click Administration from the main menu. Click Manage Pages directly from the navigation. Navigate to the resource in the table. Click the Delete icon Confirm the deletion to remove the resource.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
21
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Web Modules
The Manage Web Modules portlet allows you to install new portlets from either a Web service or WAR file or to manage existing portlets, or view a list of portlet applications for a Web module. A Web module is a war file containing portlet applications. E.g. OAViewer portlet
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
22
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Web Modules
Web Modules portlet allows you to start up application in case you can see it started in WAS asdmin console but portal page shows that it is not available.
To poerform this task navigate to Web Modules use search to find desired application and click on Start button that will appear only in case application is not started.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
23
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Applications
The Manage Applications portlet allows you to enable a portlet application as a Web service or to manage existing portlet applications. It displays a list of all Web modules and associated portlet applications installed on WebSphere Portal. You can view and change portlet application settings from this portlet. Tasks include renaming and deleting portlet applications, and modifying configuration parameters.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
24
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Portlets
The Manage Portlets portlet allows you to view or manage existing portlets, or enable portlets as Web services. It displays a list of all installed portlets. Manage Portlets allows you to view and change portlet settings. Tasks include renaming and deleting portlets, and adding, modifying, or deleting portlet configuration parameters
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
25
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Portlets
A Web module represents a Web application. It is used to assemble servlets and JSP files as well as static content, such as HTML pages, into a single deployable unit. Web modules are stored in Web ARchive (WAR) files, which are standard Java archive files. The standard file extension for WAR files is .war. A Web module can contain one or more portlet applications, servlets, JavaServer Pages (JSP) files, and other files. A deployment descriptor, stored in an Extensible Markup Language (XML) file, declares the contents of the modules, information about the structure and external dependencies, and a description of how the components are to be used at run-time.
Portlet applications are created implicitly when a WAR file is deployed. The portlet application holds one or more related portlets that come packaged in the same installation file. These portlets can share resources and send messages among themselves to communicate events. A portlet application may consist of a single portlet or multiple portlets. An example of a portlet application with multiple portlets is Portlet Manager Application, which contains Manage Web Modules, Manage Applications, and Manage Portlets. For additional information on working with WAR files, see the information center for WebSphere Application Server.
You can add portlets to a running system at any time. After installation, the new portlets are immediately available to administrative users. They can assign the appropriate user roles to the desired groups and users so that these can access and use the portlets. Once available, the portlets can be selected for display on the portal pages of users and can be edited as appropriate. Identification information of WAR files is stored in a database for easy deployment in complex server environments with multiple portal servers. By allowing all files associated with a portlet to be packed into a single file, distribution and deployment of new portlets is made easier. Portlets can be distributed in WAR file format through Web sites and other means.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
26
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Portlets
Activating and deactivating portlet applications or portletsBy default, portlet applications and portlets are set to an active state after installation. Pages also have an active and inactive state. You can deactivate a resource to prevent users from accessing it without changing their user roles. When a portlet application or portlet is in the active state, portal users with appropriate access can include it on their personal pages and customize it. Users that have active references to those inactive portlets on a portal page will see a message stating that the portlet is temporarily disabled. If you begin working on a portlet, WebSphere Portal automatically changes the state to deactivated. After completing work on the resource, you must remember to activate it so that others with appropriate permissions can use it.
You can toggle portlet application or portlet states to active or inactive by using the portal XML configuration interface. Below file refers to activate OAViewer Portlet. Please see the syntax of xmlaccess command xmlaccess.sh -in /home/wpsadmin/Activate_Portlet.xml -user wpsprdbind -password password –url http://amdc-wps-ux01.amdc.mckinsey.com/wps/config
ActivatePortlet.xml
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
27
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Users and Groups
The Manage Users and Groups portlet allows you to add, modify and delete uses, groups and its permissions. Navigate to Users and Groups link on the side menu.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
28
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Resource Permissions
Resources are organized in a hierarchy. Resources in the hierarchy propagate their access control configuration to all of their child resources. For example, if a user has the Editor role on the Market News Page, then by default that user also has the Editor role on all pages that are children of the Market News Page.
Resources can appear in different domains depending on the type of resource. JCR nodes are exclusively contained in the JCR domain. User customization data represented by private resources are exclusively contained in the customization domain. The community domain contains resources related to collaborative applications, and the release domain contains all remaining resources. Resources can be administered in the following ways:Protected Resources of the release domain can be managed through the access control administration portlets and through the XML Configuration interface Template and Policy resources are stored in the JCR domain and can also be managed through the access control administration portlets and through the XML Configuration interface Resources in the community domain can only be managed through collaboration application specific administrative portlets. Resources in this domain are not shown in the access control administration portlets The customization domain only holds private resources of users. No role assignments are possible in this domain, so resources in this domain are also not shown in the access control administration portlets
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
29
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Resource Permissions
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
30
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Resource Permissions
A different user interface is provided to administer access control for each type of resource in the JCR domain. The following list shows the path to take within WebSphere Portal to reach the access control portlet for each resource stored in the JCR domain: Access Control Administration User Interface (UI): • Administration > WebSphere Portal > Access > Resource Permissions > Resource
Permissions portlet • Administration > WebSphere Portal > Access > User and Group Permissions > User and
Group Permissions portlet Document UI: Documents > Document Manager > Document Manager portlet Document Libraries UI: Administration > WebSphere Portal > Portal Content > Document Libraries > Document Libraries portlet Personalization UI: Personalization > Business Rules > Personalization Navigator portlet Web Content Libraries UI: Administration > WebSphere Portal > Portal Content > Web Content Libraries > Web Content Libraries portlet IBM Workplace Web Content Management UI: Web Content > Web Content Management > Authoring portlet You can assign roles on virtual resources and on resource instances. Assigning roles on virtual resources reduces the time needed to administer access control because all child resources inherit roles that are assigned to the parent resource by default. Assigning roles to specific resource instances offers more granular access control. You might need to assign roles to specific resource instances to override role blocks that block inheritance
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
31
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Side Menu Overview – Resource Permissions
The following document describes virtual resources. The resources listed could be different depending on other products that might be installed with WebSphere Portal.
virtual resources
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
32
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Syndication Overview
Syndication overview
Syndication is the method used by IBM Workplace Web Content Management to replicate data from a Web content library on one server to a Web content library on another server.To enable syndication, a syndicator and a subscriber must be defined:The syndicator defines a connection to the subscriber and indicates which libraries are to be replicated to the subscriber. The subscriber defines a connection to the syndicator and receives the data replicated from the libraries specified by the syndicator. The relationship between syndicators and subscribers can be both a one-way or two-way relationship.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
33
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Syndication Overview
We are using one-way syndication in McK architecture which means that content can be syndicated only to the higher environment.
Dev Instance QA Instance Prd Instance
Syndicator_QA Subscriber_INT / Syndicator_PRD
Subscriber_QA
INT instance holds only Syndicator that pushes content and settings. QA instance contains Subscriber for integration subscriber and Syndicator_PRD to be able to push config and content files to production environment. Production environment has only Subscriber_QA configured. It means that Production environment can only subscribe content from QA environment.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
34
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Administration – Syndication Overview
To set up a syndication relationship between QA and PRD, complete the following steps.
1. Login to QA WebSphere Portal Administration console2. From Side Menu select Portal Content -> Syndicators3. Click 4. Specify name for the syndicator in the Name field5. Enter additional information about syndicator in the Description field6. Using different browser window, login to PRD WebSphere Portal Administration console7. On the Side Menu select Portal Content -> Subscribers8. Click 9. Specify name for the subscriber in the Name field10.Enter additional information about subscriber in the Description field11.Copy required information from one window to another.
– Copy the subscriber's name, ID, and URL to the syndicator window. – Copy the syndicator's name, ID, and URL to the subscriber window.
12.If you are creating a new syndicator specify which WCM libraries to replicate– Click Add libraries. – Select the libraries for replication. – Click OK.
13.Save the new syndicator or subscriber by clicking OK.
Important: If you are creating the subscriber at the same time as the syndicator, you must save the syndicator before you save the subscriber.
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
35
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Troubleshooting WebSphere Portal
WebSphere Portal is a bunch of application installed on WebSphere Application Server. There is no standard way to approach WebSphere Portal troubleshooting.
In the best case we are able to identify problem without checking all the components running behind the portal.
In case of problems with WebSphere Portal I would perform checks in the document below in the given order.
WPS_Troubleshooting
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
36
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Troubleshooting WebSphere Portal
There are some repetetive scenarios that I would like to address here.
1. ObjectAccess thread utilization is high – Caused by database poor performance – escalate it to DBAs for SAIL_DB checkup– Caused by documentum CS servers are unavailable or poorly responding – Check if there is any
Verity, Documentum alert in your maillbox – Caused by http://amdc-naweb-ux12/firmwide/firmdirext.nsf - escalate it to M&I Team – Caused by OA internal error – Restart application in WAS v6 environment
2. WebSphere JVM is not starting up– Caused by filesystem being utilized in 100% - Cleanup filesystem– Caused by recent configuration changes – Revert back all the changes that were applied– Caused by Network misconfiguration – Please escalate to Unix Team for checkup
3. HTTP Server is responding slowly– Caused by high CPU utilization – restart HTTP Server– Caused by missing assets – please verify missing component and ask AppDev Team for assistance– Caused by recent changes – revert back all the changes have been applied
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
37
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Apendix
APENDIX
Michal HoltorffPRA-CHARGE-YYYYMMDD-XXXXXP1E
38
Wo
rking D
raft - Last M
odified
17.01
.2008
16:28
:27P
rinte
d 13.09
.200
6 14
:10:1
1
Apendix
•WCM portlet – Web Content Management workshop•PZN portlet – How to personalize content•Syndication – Setting up syndication and syndicating content•WPS configuration – Configuring empty portal