Portal Server Administration Link Missing...

I have recently experienced the an issue with IBM Portal Server 5.1. I have installed the Portal server and it was working fine, after few days i was experimenting with the theme which cost me a lot. After changing the theme when i came back to 'my portal', the administration link was no more available. After lods of google and other search, finally i found the solution to this issue. Sharing with you so that this could help you, if you are in similar situation. The solution is to Reset the theme setting using XMLAccess of the portal server.

Steps are as follows to reset the theme setting of Portal Server:
1. Start the portal server.
2. Go to command prompt \PortalServer\bin
3. Create a xml file inside the same folder (easy to use)
export.xml (export all administration label and pages) the content should be:

On command promt use:
command promt>xmlaccess.bat -in export.xml -user wpsadmin -user wpsadmin -url http://localhost:9081/wps/config -out adminpage.xml
Note:URL you need to replace with your system specific.

4. Next, modify the same export.xml replace the content with.







5. Execute following command
command prompt> xmlaccess.bat -in export.xml -user wpsadmin -user wpsadmin -url http://localhost:9081/wps/config -out themeSetting.xml
Note:URL you need to replace with your system specific.

6. Now search for content-node in adminpage.xml and then for wps.administration then change themeref to default theme object id.
7. Open the themeSetting.xml change the wps.theme.webSphere as default=true and make other theme as default=false.
8. Import both xml to server using following commands.
command prompt> xmlaccess.bat -in adminpage.xml -user wpsadmin -user wpsadmin -url http://localhost:9081/wps/config

command prompt> xmlaccess.bat -in themeSetting.xml -user wpsadmin -user wpsadmin -url http://localhost:9081/wps/config
Note:URL you need to replace with your system specific.

9. Re-start you portal server, you could see you administration link is back.

All the best !! and leave your comments.

Migrated to Subversion 1.3.2..

The motivation behind writing this blog is that after using one of our project on subversion without a proper migration we had serious concern over subversion that shall we go ahead with it so we should stop using it and back to Microsoft Visual SourceSafe (VSS) or some other configuration tool; because we were struggling to do the proper migration from VSS to subversion repository. The reasoning behind selection of subversion was the features of subversion. My PM; Mr. Suryatej asked me to do some R&D on this issue to check whether it is possible to migrate (With complete revision History of file in VSS) to Subversion with my regular work for client 401J.

After sourcing the Internet for a good VSS to Subversion migration tool, I came up with few Perl and Python scripts. I found the script written by Brett is suitable to my requirements. He had exactly same requirements for his firm. Well! I got some a starting point. Here I want tell you that I am novice in Perl script J

Day 1
Now task to customize the migration script according to our setup. As usual, initial failures the subversion guy who gave us the training didn’t configure the subversion for different projects, there was many things to set before this script to run such as project wise authentication and authorizations.

Day 2
The migration script written by Brett need few modules to be installed for Perl; which are not mentioned.Modules are: * DBI * Time::ParseDate (install "Time-modules" from PPM) * File::Path * Win32::TieRegistry

Here need to mention that the log file (migrate.log) generated by the migration script helped me to fix the issue the customization issues.

Another issue: The migration script is using command line checkout from VSS. We never ever used command line to check out a file from VSS.

The command to get file from VSS used by script:

"\ss.exe" get -GTM -W -I- -GL"" -V1 /"

Got the help from MSDN on ss command where as for more options like –GTM and –GL went further deep in to MSDN itself. Add new environment variable SSDIR with the VSS repository location.

Very first time I have seen a inital success when the files started getting from VSS and were trying to add in to subversion repository. Failed with authentication error because I had created user with all lower case where as script was trying with Sentence case. Huh! I got a smile and started looking for a function in Perl which will convert user name to lower case.

Day 3
Got it J very small thing for the Perl champs but for me getting the function lc EXPR which actually Returns a lowercased version of EXPR, solved the issue.
Change in script:

1. $user = lc $user;

2. svn --non-interactive checkout --username $user --password $user \"$REPOS/$basedir\" \"./work/$basedir\""

3. svn commit --non-interactive --non-recursive --username $user --password $user --message $comment \"$'\"";

Before I tell you the migration result, I should mention that there are four primary phases in the migration run:

A. Building Directory Hierarchy

Determines the directory structure of the project in VSS

B. Building File List

Determines the list of all 'live' files in the VSS project

C. Building File Histories

Determines all version information, time/data information, user information, and checkin comments for all files identified in step 2

D. Extract and Import

Extracts files one-by-one, version-by-version, from VSS and checks them into Subversion

Migration Started:

Building directory hierarchy: done (1519 dirs)

Building file list (100%): done (3863 files)

Building file histories (100%): done (4122 versions)

Creating local directories: done

Importing directories: done

Checking out directories: done

Extracting and creating (100%): js (v.1)

and end with sucess....... a big success for me...

Spring 2.0 vs. the Anemic Domain Model

Spring 2.0 vs. the Anemic Domain Model

One of the most interesting aspects (no pun intended) of Spring 2.0 that was discussed this past week at The Spring Experience was the idea of letting Spring configure beans post-instantiation and regardless of how the bean became instantiated. This Spring 2.0 feature helps avoid the Anemic Domain Model" anti-pattern as described by Martin Fowler.

It's very common in Spring to build applications where service objects are injected with DAO objects and use those DAO objects to handle persistence of domain objects. The domain objects themselves, however, are little more than dumb data holders. The problem with this approach is that the interaction between the service object and the DAO object is very procedural. The service object makes one or more calls to the DAO, passing the domain object around like cargo.

Ideally, the domain object would contain behavior to handle its own persistence. If domain objects offered such behavior, then the service object could deal directly with the domain object in a very object-oriented way. Instead of telling a DAO to persist a customer, the service would tell the customer to persist itself. There will still be a DAO, but the domain object will do its own dealing with the DAO, unbeknownst to the service object. In effect, the domain object and the DAO swap positions with relation to the service object.

If the domain object is responsible for dealing with the DAO, then the domain object must have access to the DAO. In Spring, we'd like to do this through dependency injection. But domain objects are typically instantiated outside of Spring (e.g. in Hibernate, iBATIS, or some other persistence mechanism). How can Spring inject a DAO into a domain object when Spring isn't the one instantiating that domain object?

Full article..
http://jroller.com/page/habuma?entry=spring_2_0_vs_the

Room 404: file not found".

Why "404 - Page Not Found "? - Why not " 808 - Page Not Found " ?

The history of 404: Before the beginning of time, when the Internet was still very much under the spell of bare Unix shells and Gopher, before SLIP or PPP became widely used, an ambitious group of young
scientists at CERN (Switzerland) started working on what was to
become the media revolution of the nineties: the World Wide Web,
later to be known as WWW, or simply 'the Web'. Their aim: to create a database infrastructure that offered open access to data in various formats: multi-media. The ultimate goal was clearly to create a protocol that would combine text and pictures and present it as one document, and allow linking to other such documents: hypertext.Because these bright young minds were reluctant to reveal their progress (and setbacks) to the world, they started developing their protocol in a closed environment: CERN's internal network. Many hours were spending on what later became the world-wide standard for multimedia documents. Using the physical lay-out of CERN's network and buildings as a metaphor for the 'real world' they situated different functions of the protocol in different offices within CERN.

In an office on the fourth floor (room 404), they placed the World Wide Web's central database: any request for a file was routed to that office, where two or three people would manually locate the requested files and transfer them, over the network, to the person who made that request. When the database started to grow, and the people at CERN realized that they were able to retrieve documents other than their own research-papers, not only the number of requests grew, but also the number of requests that could not be fulfilled, usually because the person who requested a file typed in the wrong name for that file. Soon these faulty requests were answered with a standard message: Room 404: file not found". Later, when these processes were automated and people could directly query the database, the messageID's for error messages remained linked to the physical location the process took place: "404: file not found".The room numbers remained in the error codes in the official release of HTTP (Hyper Text Transfer Protocol) when the Web left CERN to conquer the world, and are still displayed when a browser makes a faulty request to a Web server. In memory of the heroic boys and girls that worked deep into the night for all those months, in those small and hot offices at CERN, Room 404 is preserved as a 'place on the Web'. None of the other rooms are still used for the Web. Room 404 is the only and true monument to the beginning of the Web, a tribute to a
place in the past, where the future was shaped.

Simple Error 007

Hey! see this link ........... u will surely enjoy.....
http://ncb.ernet.in/~pravin/fake.html