rajesh: Rajesh's Weblog

Problem: Cannot make Sun Portal Server to work with Sun Messaging Server (specifically Address Book)

Legend :  Sun Portal Server comes with a Address Book provider channel wherein you can get sun UWC messaging server's address book details pertaining to each users.

Solution: To get it working with Sun Portal Server , do as below:

-o Login to sun portal server psconsole -> Create a new Channel based on Address Book JSP Provider [Note: Let the channel use the  default SUN-ONE-ADDRESS-BOOK sso adapter template]

-o Now click on SSOAdapter tab in psconsole  -> Go to GENERIC_TEMPLATE
-o Select SUN-ONE-ADDRESS-BOOK and provide appropriate details of your UWC server as mentioned in the below screencast
-o You can use /opt/SUNWmsgr/sbin/configutil | grep <sun-one-address-book-textboxfields>
to get the values for each of the text fields while editing the SUN-ONE-ADDRESS-BOOK template

[Note: This forum link was useful]

Problem: The CMS workflow portlets in Sun Portal Server 7.2 release depends on Java CAPS installation . Sometimes if the LDAP of JCAPS is not running , then the CMS portlets will throw the below the error: "Exception while invoking JCAPS API"

Solution: Stop JCAPS Appserver >> Start LDAP >> Now start Appserver again

Background info : Sun Portal Server 7.2 release has a JSR 170 based Content Management System(CMS) portlets in it. The CMS portlets has a workflow capabilities which is provided by Java CAPS.

After Portal Server Installation , if you are getting problems accessing /portal then check for whether the installation itself has successfully completed or not. Here I will cover up some of the typical cases which will indicate that the installation was not successful.

 
Case I : After portal server installation, the ps console comes up fine , the web server(container) comes up. However, the /portal does not come up

While the container startsup, the below message indicates that the portal was not deployed properly.

[21/Jan/2008:19:09:00] failure (22091): WebModule[/portal]PWC1275: Exception sending context initialized event to listener instance of class com.sun.portal.community.notification.impl.NotificationManagerFactoryImpl
java.lang.ExceptionInInitializerError
    ..
Caused by: java.lang.RuntimeException: failed to get properties
    ... 14 more
Caused by: java.io.FileNotFoundException: /opt/SUNWportal/lib/ps_util.jarcommunitymgmnt.properties (No such file or directory)

More installation and portal configuration related info can be found in portal fabric and admin logs
Relevant logs are /var/opt/SUNWportal/logs/fabric/portal.fabric.0.0 and /var/opt/SUNWportal/logs/admin/portal.0.0.0

 

The format of a Fully Qualified Sun Portal Server URI is  myhost.india.sun.com:8080/portal

where,

(1) myhost.india.sun.com is the FQDN

(2) 8080 is the container port where the portal is deployed

(3) portal is the URI

Take the example of Sun Portal Server. By default installation, you will be accessing the main page of the portal as "http://hostname:port/portal/dt".  The element "/portal/dt" is quite sun-ish and will be available for all sun portal server installation as long as you leave it untouched (of Course you can change /portal/dt to /myportal/mydt)

Now lets say that you want to know about all are the public sites hosted using sun portal server (assuming they have /portal/dt implentation) then you can use google's inurl features.

You will be happy to see that search results shows publicly hosted sun portal server .  Google, hats off!!

Check out more google search operators

Thanks ajit kamble for this interesting observation !!

Older versions of  JSPWiki (say JSPWiki v2.2.28) have some serious back door which if you are not aware will allow any users to cause serious damage to your wiki. Sun Portal Server 7.0 / 7.1 customers should be aware of this issue and make sure that portal server wiki portlet is secure . For sites hosted on independent JSPWiki system, they should make sure that external users cannot access the below files:

(a)/../wiki/Install.jsp     (b)/../wiki/admin/SecurityConfig.jsp

 In a portal server deployment scenario, if the wiki system is not made secure , any user can access the /wiki/Install.jsp web page directly and bring it down. Below is a worse case:

Suppose you set up a portal server as http://abc.india.sun.com/portal . Assuming its a default installation where you wont do much of a changes, now access the URL,  http://abc.india.sun.com/wiki/Install.jsp
2. The Install.jsp file is a form which allows any user to update its contents (say users can change Application Name: , Base URL: , File storage: , Work directory: etc )
3. After updating this form, now click on configure button and restart the container. Try to access wiki within portalserver 

Issue :  You will now see that , wiki tab displays error
 (Update 23/aug/2007 : This issue is now fixed in the latest build) 

Just now found out that BigAdmin site has arranged a nice way and put up all the portal server manuals together in one place
For PortalServer 7.1, you can access this link and get all the details of portal server , right from planning to deployment!!

Good News!!!  Sun Java Portal Server is selected as Best Portal Platform by SYS-CON Media Announces 2007 SOA World Reader's Choice Awards ... More can be read here

After deploying jspwiki.war successfully in Sun Web Server, whenever i try to login as admin, i get the below error

 WebPages displays this error:  "Forbidden. Sorry, but you are not allowed to do that. Usually we block access to something because you do not have the correct privileges (e.g., read, edit, comment) for the page you are looking for..."

Jspwiki.log displays error :  INFO com.ecyrd.jspwiki.WikiContext JSPWiki:http://site - User Admin has no access - forbidden (permission=("com.ecyrd.jspwiki.auth.permissions.PagePermission","JSPWiki:Main", "view" ))

Now to make jspwiki work , i had to remove the signedBy "jspwiki" entry from WEB-INF/jspwiki.policy file  and restart the container

After deploying JSPWiki.war :

1. Access the URL (http://localhost:8080/JSPWiki) . If everything is successfully configured, you should see the Main wiki page.

Note: If you get a Login page instead of Main page when you access the above url, then there is some problem with WEB-INF/jspwiki.policy file. See here for troubleshooting

2. There are two ways by which you can proceed from here:

I. Access Install.jsp and get a admin user password configured by jspwiki

(a)Access the Install.jsp file (http://localhost:8080/JSPWiki/Install.jsp)

(b)Set the application name, Pages/Log/Work directories and click Configure button

(c) Note down the password . Login with the admin password and change it to your custom password (MyPrefs >> Set Admin user details >> Save the page)

(d) Your new wiki will be configured successfully . You need to restart the container for this effect to take place

 
II. Else Create Admin user from MyPrefs link

(a) Firstly create a Admin user (MyPrefs >> Set Admin user details >> Save the page)

(b) Now you are automatically logged in as Admin user

Note: Install.jsp file displays jspwiki.properties file contents. Any changes made thru the UI will be updated in the JSPWiki.properties (usually you can see that this entry at the bottom of jspwiki.properties file which overrides the default ones)

Note : Normally once admin user is created , then you cant access
Install.jsp file . To access the Install.jsp again, you need to delete
the admin user details from userdatabase.xml file

When i run /usr/sfw/bin/ant command i get the below exception
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/Launcher

Workaround:

1. Set ANT_HOME=/usr/sfw
2. Set JAVA_HOME=/usr/jdk/entsys-j2se/
3.  /usr/sfw/bin/ant command should run successfully now

Note: On a PortalServer installed on Linux system, ant can be found in /opt/sun/bin/ant
 

This note assumes you have a fair understanding of Sun Java Portal Server InterPortlet Communication. Pls see here for more information about IPC

 (1) IPC portlets generating a event and listening to the same event

For a IPC portlet to generate or listen an event , it should first register this information in sun-portlet.xml file . Say a portlet "HelloWorldPortlet" generates a event "event1" and listen to the same can have the entry as below in its sun-portlet.xml file.

Example 1: A IPC portlet "HelloWorldPortlet" generates a event "event1" and listens to the same event "event1" 

  <portlet>
        <portlet-name>HelloWorldPortlet</portlet-name>
        <deployment-extension>
            <extension-element>
                <session-enabled>0</session-enabled>
            </extension-element>
        </deployment-extension>
        <events>
            <generates-event>event1</generates-event>
            <consumes-event>event1</consumes-event>
        </events>
    </portlet>

(2) IPC portlets generating a event and listening to all the events generated by other portlets (and its own events too)

Example 2:A IPC portlet "HelloWorldPortlet" generates a event "event1" and listens any events generated by other portlets

 <portlet>
        <portlet-name>HelloWorldPortlet</portlet-name>
        <deployment-extension>
            <extension-element>
                <session-enabled>0</session-enabled>
            </extension-element>
        </deployment-extension>
        <events>
            <generates-event>event1</generates-event>
            <consumes-event>*</consumes-event>
        </events>
    </portlet>

Note : If a portlet requests an event which has not been declared in the sun-portlet.xml file, an exception NotRegisteredException will be thrown. Wild cards can not be used for declaring the events that will be generated.