Appreciations accepted

Vladlen Litvinov, the author: If you have some job offer for me, I'm ready to discuss it. View Vladlen Litvinov's profile on LinkedIn


Wednesday, September 25, 2013

How to open FileNet Global Configuration Data without any accounts (Part 2)

Yesterday I wrote about opening a GCD configuration.
But, the Object Store was not availble (We have only rights for reading as Authenticated Users).
Continue our exploring.

The fact is security descriptors of object stores are being located in the another database of FileNet - OSD (object store database).

1. Open this database and (secret de Polichinelle) look the table "SecurityDesc".
Again the descriptors were stored in blobs.

Use our old method:

Declare @sql varchar(500)
SET @sql = 'bcp OSD.dbo.SecurityDesc out c:/temp/sd.xml -N -T -S localhost'
select @sql
EXEC master.dbo.xp_CmdShell @sql

But the output file is not xml. It is binary!

2. Try to look into it.  We have to use some HEX editor.
Certainly we find a lot of traces of our old friend - the SID of our GCD administrator.
Replace this SID to our NEW SID using editor and save the file.

3. We need to delete all of old rows in the table "SecurityDesc" and execute the import:

Declare @sql varchar(500)
SET @sql = 'bcp Filenet.dbo.SecurityDesc in c:/temp/sd.xml -N -T -S localhost'
select @sql
EXEC master.dbo.xp_CmdShell @sql

4. After WebSphere starting, we can edit all the objects of our Object Store (and add documents too).

Used: Windows Server 2008 R2, SQL Server 2008, IBM FileNet Content Engine 5.1 and skillful hands.

No comments:

Post a Comment