| Component | Logs | ||
| ALUI Portal | $PT_HOME/ptlogging/logs/portal/*.spy | ||
| Automation | $PT_HOME/ptlogging/logs/portal/automationserverwrapper.log | ||
| Document Repository | $PT_HOME/ptdr/6.1/logs/drLogs.txt | $PT_HOME/ptdr/6.1/logs/wrapper.log | |
| Search | $PT_HOME/ptsearchserver/6.1/adminui/logs/wrapper.log | $PT_HOME/ptsearchserver/6.1/[$SearchNode]/logs/logfile-trace-yyyy-mm-dd | $PT_HOME/ptsearchserver/6.1/[$SearchNode]/logs/logfile-event-yyyy-mm-dd |
| Publisher | $PT_HOME/ptcs/6.4/logs/service.log | $PT_HOME/ptcs/6.4/logs/container.log | $PT_HOME/ptcs/6.4/logs/boot.log |
| Collaboration | $PT_HOME/ptcollab/4.2/logs/collaboration_log.yyyy-mm-dd.txt | $PT_HOME/ptcollab/4.2/settings/logs/collaboration.log | $PT_HOME/ptcollab/4.2/settings/config/wrapper.log |
| Notification | $PT_HOME/ptnotification/4.2/settings/logs/notification.log | $PT_HOME/ptnotification/4.2/settings/logs/wrapper.log | |
| Analytics | $PT_HOME/ptanalytics/2.1/logs/analyticsui.log | $PT_HOME/ptanalytics/2.1/logs/asmanagerui.log | $PT_HOME/ptanalytics/2.1/logs/configurator.log |
| Studio | $PT_HOME/ptstudio/2.2/logs/wrapper.log | $PT_HOME/ptstudio/2.2/logs/ptstudio_log.yyyy-mm-dd.txt |
Friday, June 11, 2010
ALUI Log File Locations
Thursday, April 29, 2010
******* Adieu *******
Hmmm!!!!!
Writing a farewell mail is a tough job you know. At least for first timers like me. Sadly Google miserably fails to help!! Well I just kept staring at my monitor wondering how all the 4.5 years have passed like a flash. I never thought this day would also come. But here it is……
Still remember my first day vividly, I came here as a boot camper, wide eyed with a starlit gaze and scared about the corporate world. Employee ID – 53280 that’s what I was branded. Life on Earth became Heaven on Earth for me when I received my first paycheck here. Honestly the first think I did was take out the whole salary from the ATM machine and stare at it the whole night. I didn’t know how to spend so much money (pun intended, my salary was not much). :)
IPL season 3 has just ended and today I stand Not Out after completing my half century in Birlasoft. Yes, I have completed 52 months in Birlasoft. I started off as an MCA trainee, today as I look back I have treaded a long and arduous path.
Frankly, it is difficult for me to end this relationship with Birlasoft. Today, I am what I am because of Birlasoft.
I gained some of my best buddies here.
I gained the love of my life and now my wife here.
I gained the best mentors here.
I gained the best team members here.
I gained all my knowledge here.
Thanks are in order for a lot of people who have made an indelible impression on my life @ Birlasoft. Starting with Abhishek Gupta and Mandip Vats who selected me from Campus. The journey wouldn't have been possible without the great support from all my Managers / Mentors, R. Srikanth, Samrat Choudhury, Augustine Sunand and Ashutosh Goyal who had the trust and faith on me that I could achieve and deliver beyond their expectations.
I can probably write another 2000 words on my experiences with Birlasoft. Don’t worry guys n gals, I won’t bore you with it. I would reserve it for my blog. But they say, Duniya Gol Hai……kya pata kab …..kaha….kaunse mod par hum dobara milenge…….. :)
Until then wish all of you all the very best for all your endeavors, be it personal or professional. :) :)
I will share my new mobile number as soon as I get it. I can always be reached on srinammisra@gmail.com
Writing a farewell mail is a tough job you know. At least for first timers like me. Sadly Google miserably fails to help!! Well I just kept staring at my monitor wondering how all the 4.5 years have passed like a flash. I never thought this day would also come. But here it is……
Still remember my first day vividly, I came here as a boot camper, wide eyed with a starlit gaze and scared about the corporate world. Employee ID – 53280 that’s what I was branded. Life on Earth became Heaven on Earth for me when I received my first paycheck here. Honestly the first think I did was take out the whole salary from the ATM machine and stare at it the whole night. I didn’t know how to spend so much money (pun intended, my salary was not much). :)
IPL season 3 has just ended and today I stand Not Out after completing my half century in Birlasoft. Yes, I have completed 52 months in Birlasoft. I started off as an MCA trainee, today as I look back I have treaded a long and arduous path.
Frankly, it is difficult for me to end this relationship with Birlasoft. Today, I am what I am because of Birlasoft.
I gained some of my best buddies here.
I gained the love of my life and now my wife here.
I gained the best mentors here.
I gained the best team members here.
I gained all my knowledge here.
Thanks are in order for a lot of people who have made an indelible impression on my life @ Birlasoft. Starting with Abhishek Gupta and Mandip Vats who selected me from Campus. The journey wouldn't have been possible without the great support from all my Managers / Mentors, R. Srikanth, Samrat Choudhury, Augustine Sunand and Ashutosh Goyal who had the trust and faith on me that I could achieve and deliver beyond their expectations.
I can probably write another 2000 words on my experiences with Birlasoft. Don’t worry guys n gals, I won’t bore you with it. I would reserve it for my blog. But they say, Duniya Gol Hai……kya pata kab …..kaha….kaunse mod par hum dobara milenge…….. :)
Until then wish all of you all the very best for all your endeavors, be it personal or professional. :) :)
I will share my new mobile number as soon as I get it. I can always be reached on srinammisra@gmail.com
Some News
Long time no see...... Well there's some news from my end..... I have finally decided to call it quits at Birlasoft. I had been associated with Birlasoft for 4.5 long looong loooooong years. It was a mixed bag for me......I had some very good as well as some unfortunate experiences over there.....Well the experiences will make the content of another blog post......but sometime later.....
Currently I am going to enjoy this sabbatical away from work with some cooking.......reading.....travelling.....
Currently I am going to enjoy this sabbatical away from work with some cooking.......reading.....travelling.....
Thursday, April 15, 2010
Recommended Portal Server Reboot Order
I work in a project where we also have control over the servers. Each time patches are installed or for some godforsaken reason if the portal environment shows signs of breathing its last.......What do we do ?......
Voila!!! Restart the servers so that we delete all connection pools and have an environment as good as new. In medical parlance....restarting the servers is like giving CPR to a dying person....
Oh!! By the way, recently I had seen a man performing CPR on a monkey that was eloctrucuted infront of our office.
Coming back to the CPR procedure.....I mean the server reboot order, Oracle WCI/BEA ALUI/Plumtree has a specific order to it which unfortunately is not present in any of the Admin guides available. Thats the reason I decided to document it for your benifit.
Shutdown
Startup
My personal experience with portals says that, one should shut down the main portal server first but refrain the temptation of restarting it first. The main portal server should be started up the last with the other component servers being turned on before that.
Voila!!! Restart the servers so that we delete all connection pools and have an environment as good as new. In medical parlance....restarting the servers is like giving CPR to a dying person....
Oh!! By the way, recently I had seen a man performing CPR on a monkey that was eloctrucuted infront of our office.
Coming back to the CPR procedure.....I mean the server reboot order, Oracle WCI/BEA ALUI/Plumtree has a specific order to it which unfortunately is not present in any of the Admin guides available. Thats the reason I decided to document it for your benifit.
Shutdown
- Portal server
- Other component servers
- Database server
Startup
- Database server
- Other component servers
- Portal ServerPortal servers depend on the database server being up.
My personal experience with portals says that, one should shut down the main portal server first but refrain the temptation of restarting it first. The main portal server should be started up the last with the other component servers being turned on before that.
Monday, March 22, 2010
What is Quiesce ?
What in God's name is Quiesce???No, Quiesce doesn't mean the same user online can't do anything or a new user can't access the SharePoint site.
I have collated the following information and hopefully this will help you to understand how Quiesce works.
Quiescing comes into the limelight especially where long running sessions are required. Not all features in your portal environment are affected when you Quiesce your farm. There are two primary features that make use of Quiescing: Microsoft Office InfoPath Forms Services (IPFS) and Microsoft Office Excel Services. Many other features and operations do not need to use Quisecing because they do not have long running sessions where users enter data over multiple server requests without having to save information. For instance, when editing an item in a SharePoint list, SharePoint handles that in a single transaction to the database, storing the information, so no Quiescing needed here.
However, in IPFS, a form filling session may require several communications with a server as the form posts back for server-side data processing for operations such as view switching. Data from the session is usually not saved until the very end when a user submits or saves the form that he or she is filling. Voila!!! Quiescing comes into the picture here.
If an administrator takes the farm offline while some users were already filling it out, the users would lose all of the data they have been trying to input so far in their session and you would be recieving lot of HATE MAIL in your inbox for doing this ;-)
Therefore, if an administrator is going to bring the farm offline, in order to preserve their customer data, they would make a plan of action and first quiesce the farm. This prevents new requests from coming in to start filling out new forms, but it allows existing form filling sessions to continue. When the sessions are all completed, or when an administrator-specified time elapses, the farm enters the quiesced state where no new requests are accepted. The farm can then be safely taken offline at this point without causing any data loss for users and lets be fair, you gave a fair deal of time for end users to fill in thier data in thier forms.
Hope this was helpful.
I have collated the following information and hopefully this will help you to understand how Quiesce works.
Quiescing comes into the limelight especially where long running sessions are required. Not all features in your portal environment are affected when you Quiesce your farm. There are two primary features that make use of Quiescing: Microsoft Office InfoPath Forms Services (IPFS) and Microsoft Office Excel Services. Many other features and operations do not need to use Quisecing because they do not have long running sessions where users enter data over multiple server requests without having to save information. For instance, when editing an item in a SharePoint list, SharePoint handles that in a single transaction to the database, storing the information, so no Quiescing needed here.
However, in IPFS, a form filling session may require several communications with a server as the form posts back for server-side data processing for operations such as view switching. Data from the session is usually not saved until the very end when a user submits or saves the form that he or she is filling. Voila!!! Quiescing comes into the picture here.
If an administrator takes the farm offline while some users were already filling it out, the users would lose all of the data they have been trying to input so far in their session and you would be recieving lot of HATE MAIL in your inbox for doing this ;-)
Therefore, if an administrator is going to bring the farm offline, in order to preserve their customer data, they would make a plan of action and first quiesce the farm. This prevents new requests from coming in to start filling out new forms, but it allows existing form filling sessions to continue. When the sessions are all completed, or when an administrator-specified time elapses, the farm enters the quiesced state where no new requests are accepted. The farm can then be safely taken offline at this point without causing any data loss for users and lets be fair, you gave a fair deal of time for end users to fill in thier data in thier forms.
Hope this was helpful.
Thursday, March 11, 2010
Recuperating Lost Collab Documents
Seldom does everything work out fine in life. It might so happen that one fine day you wake up and you find that some how something screwed up and some of your collab projects have done a dissapearing act. And for some reasons which sometimes even the mighty Oracle analysts is not able to find, the documents in the collab projects have been lost. How to restore them back to the working environment?
Solution:
The deleted files can be restored back to the production environment by using the migration utility of Plumtree.
1. Restore the backup of the production portal and collab database for that particular date in the "Recovery" environment as well as also the "PTDR" folder. "PTDR" folder is actually the repository for all the collab documents.
2. Configure the Portal in the "Recovery" environment for the restored portal and the collab database.
3. Once steps 1 and 2 is completed, Test the portal to be functioning similar to the Production environment since all the related files and database have been restored.
4. Using the migration utility of the Plumtree portal, select the Projects which have lost their files and opt for the "export "option.
Once you initiate the migration utility, what it does is it creates an export file which can be imported to any other portal environment.
5. On successful execution of Step 4, Log into the migration utility of the Target (Production in this case) portal environment and select the "Import" option. That will import the collab project details back to the target environment.
6. As a crosscheck measure, log into the target portal and check the collab project for the lost files. If they are present then everything is in order. If not then need to proceed further to Step 7.
7. This step can be carried out after completion of step 1 and 2. Query the Collab database in these tables [CSFOLDERS][CSFILES][CSFILEHISTORY] to figure out the deleted files based on the inputs from the user/business as to what all files or projects have been affected.
On querying the tables, detailed information about the Projects and their corresponding documents can be obtained such as which is the Parent folder for the Project and also the different versions of the document.
8. Based on the information procured on step 7 with reference to the lost files, open windows explorer and access the "PTDR\ documents\PTCollab\Active" from the recovery environment and copy the
Subscribe to:
Posts (Atom)
