Before you can use any object you must instantiate it first. This means that you must create the memory for object. See the Wikipedia for more information.
The instantiation applies to both regular PeopleTools objects and custom Application Packages. Here is an exploration or documentation of how you would do it.
I found a great link showing how to use the Oracle Linux DVD as a repository for yum. Although the post mentions using the DVD, you could probably setup 6 repositories with the 6 CDs to make it would for the CDs too.
Having Yum is very powerful because it figures out the prerequisites for installing software. That is one thing I definitely miss as I am working with Unbreakable Linux. I think next time I might try Ubuntu or Fedora just for experimenting around because the repositories are already setup and software installation is easier.
Customer Connection is set to migrate to MetaLink3 not this weekend but the next. Currently, you should be logging into the new MetaLink3 and making sure that you have access. That way you are ready for the change.
Change is always exciting, and I am hoping that this new site provides users an easier-to-use interface. I always had trouble searching through the old Customer Connection. Currently, it is hard to tell because none of the customer connection information exists in the new system.
I haven’t read all of the documentation yet, and so, I probably shouldn’t be commenting yet, but I first thought that Oracle was combining MetaLink and Customer Connection. But, why do we have two separate systems? From what I can tell, I will have to access MetaLink for my Oracle patches and MetaLink3 for PeopleSoft patches.
Another thing I found funny was that the Customer Connection Login page does not have a note or warning about the change. Since the change is only a couple of weeks away, I would have thought I would see something reminding me.
I did find a thread going for comments on the changes. Please share your comments.
We had an issue with taking a SQL database offline, and we found that the SQL allowed more control for rolling back in-progress transactions. Here is the article that listed the SQL.
I think our problem had something to do with the SQL Agent. We ended up having to kill the process that was accessing the database, and I am pretty sure it was a SQL Agent process. Then, the database went offline, and we able to restore it.
Peter Slager posted a new article about “What’s new in PeopleTools 8.50”. From the screenshots he posted, it looks very exciting. I am anxious to get in and try it out!
I read several posts about it coming out in late 2009. That is a long time to wait!