Linux X11 Forwarding with SU Switch User

Smart Panda - Linux Console

Linux X11 Forwarding with SU Switch User

Over the years access is often granted to one of the administrative users and then once we are on the server we have to switch user to another account to do the technical services work. This creates a problem with X11 Forwarding and so this is one work around to the problem. X authentication is based on cookies. So the secondary account needs to have access to the same cookies as the original login user.

Here is a nice easy way to do this.  This was done on an AIX 7.1 server:

Before you issue the su or sudo, request the xauth cookies and look for the current DISPLAY that’s connecting to your X server:

$ xauth list
You’ll get something like

somehost.somedomain:10 mit-magic-cookie-1 4d22408a71a55b41ccd1657d377923ae

Then, execute a switch user (su) and add the cookie to that user:

$ xauth add somehost.somedomain:10 MIT-MAGIC-COOKIE-1 4d22408a71a55b41ccd1657d377923ae

(just copy’n-paste the output of the above ‘xauth list’ onto ‘xauth add’) That’s it. Now, you _should_ be able to start any X application.

Oracle SES – Permissions & IB Setup

Well, I have just had my first full exposure to the glory they call Oracle Secure Enterprise Search!  All I can say is damn, that was NOT easy.

The documentation is pretty good that I found, and maybe it is easier on a fresh install but I was doing the setup on an existing environment that I had just upgraded.  The upgrade was for Finance from 8.9 to 9.2.  In the 9.2 application VERITY is no long supported, and the PeopleSoft Search Framework only supports Oracle Secure Enterprise Search (O-SES).  The first trick is to download it from edelivery and in my case I installed the software on my batch processing server.  This install will install a full Oracle database with a webservice that by default runs on port 7777.  There is a bunch of setup that needs to be done to get this working, but the documentation I had for the install was very good for this part.

Some of the next parts I thought were a little difficult to follow, and so the first item is, I used my system start user as my main user, and made sure it had the following roles:

Search Administrator, Search Developer, Search Query Administrator, Search Server

I also have a custom permission list that this user has access to and I made sure that the permission was assigned the search group: PTPORTALREGISTRY.  This appears to be a new security element in the permission lists.

The new Search Framework uses a ton of IB service operations to do all of its work, and one element you need to do is set the Portal Content & Portal URI text fields on the Node for all the local nodes, otherwise the search results will return incorrect content reference paths (extra:  don’t forget the “/” at the end of the URI).

Now, I also inactivated all my integration broker routings for the default local node after the upgrade so no IB would unnecessarily be taking place.  This might have been a bad idea, but old habits are hard to break.  Since O-SES uses the IB for its Search Framework, the following Service Operations need to be active with the routing turned on!






Service: PTFP_FEED – Service Operation: PTFP_GETPREPUBFEED  (not 100% sure on this one, but I turned it on along the way).

Make sure you add the PTPORTALREGISTRY to the Home Page Context Type, I added mine and made it default.  I also found that I was getting no returns and then after a day of thinking about things I tried again and everything appeared to be working fine.  I believe that the system was bounced web and app during that time, so if all else fails that might work!

Good Luck!

Remove a File Lock on Windows 2008R2

Sometimes you need to remove a locked file in a windows environment, and this should do the trick:

Open Administrative Tools -> Share and Storage Management -> Actions -> Manage Open Files

Here you are able to see all locked files and folders on this server.  To clear a lock, select the relevant file and click “Close Selected”. Note that this should only be done if the user definitely is not using the the file, otherwise data loss may occur.

Campus Solutions Patch # Change

Oracle decided to integrate PeopleSoft patching into their main database for patch fix, and in the process the commonly used Update ID, has been change to be associated with what I call the Bug Incident, but they are referring to as the Patchset in ARU.

The ARU is Oracle’s Automated Release Update system and has gone by various other names.  Since I maintain a few patch lists I have some serious updating to do, but at least they made some nice documents to show the old and new numbers.  The new system appears to be clunky and difficult to to use like all new patch systems in the past.  Hopefully it will get easier to use and understand with some more use.  Good luck!

Here is the list for the Campus Solutions 8.9 & 9.0 Campus Bundles:

Campus Solutions 9.0 Bundles

Bundle Number Update ID Patchset (in ARU)
1 682663 Patch 11397795
2 682678 Patch 11397828
3 682679 Patch 11397835
4 682702 Patch 11397868
5 687643 Patch 11404993
6 699734 Patch 11421010
7 701899 Patch 11423745
8 701900 Patch 11423746
9 701903 Patch 11423750
10 739496 Patch 11468844
11 739499 Patch 11468846
12 739503 Patch 11468847
13 739506 Patch 11468848
FP1 792325 Patch 11509618
14 739510 Patch 11468849
15 782226 Patch 11533599
FP2 795777 Patch 11555329
16 782227 Patch 11533601
17 782228 Patch 11533602
18 782229 Patch 11533603
19 782230 Patch 11533604
20 812865 Patch 11585702
21 812867 Patch 11585703
22 812869 Patch 11585704
23 861514 Patch 11701766
24 870591 Patch 12903599
25 877012 Patch 13622672
26 879831 Patch 13892711

Campus Solutions 8.9 Bundles

Bundle Number Update ID Patchset (in ARU)
 1  592864 Patch 11239530
 2  592866 Patch 11239533
 3  611993 Patch 11277406
 4  613404 Patch 11279838
 5  613408 Patch 11279853
 6  613411 Patch 11279867
 7  613681 Patch 11280184
 8  650846 Patch 11337433
 9  711549 Patch 11436520
 10  656272 Patch 11344503
 11  682701 Patch 11397866
 12  687640 Patch 11404988
 13  699733 Patch 11421005
 14  701891 Patch 11423729
 15  701895 Patch 11423737
 16  701896 Patch 11423739
 17  739491 Patch 11468852
 18  739492 Patch 11468853
 19  739493 Patch 11468854
 20  739494 Patch 11468855
 21  739495 Patch 11468857
 22  782234 Patch 11533612
 23  782235 Patch 11533613
 24  782236 Patch 11533614
 25  782237 Patch 11533615
 26  782238 Patch 11533616
 27  812859 Patch 11585698
 28  812863 Patch 11585699
 29  812864 Patch 11585700
 30  869531 Patch 12801464
 31  870589 Patch 12903619
32 877011 Patch 13622645
33 879832 Patch 13892785

Campus Solution / Human Resources Separation Documents

Here are a couple of documents that might help in understanding the CS/HCM Split:
1297158.1 – Campus Solutions to HCM Integation: A Case Study on Integration Using the Owner Subscriber Option
1267773.1 – Campus Solutions CS – HCM Integration Support Released!
1259484.1 – CS Bundle #19 Functional Documentation for Campus Solutions 9.0 & Feature Pack 4
1320568.1 – Campus Solutions Announces Support and Documentation Availability for the Subscriber Only Model of the CS-HCM Separate Instance Integration