Thursday, July 9, 2015

DRM Configuration Console on Windows 2012

You may not be able to save configuration changes using configuration console on Windows 2012 server even if you have admin access.

I order to save changes, start the configuration console as administer. i.e. right click on configuration console shortcut and select run as administrator.

Monday, July 6, 2015

DRM 11.1.2.4 - username cannot contain . (period)

 Oracle DRM for some reason does not allow username to contain . (period). This may not be an issue for most of the implementations but if you are one of the users who happen to integrate DRM with LDAP and you use firstname.lastname in your LDAP, this could be an issue.
I personally dont know if this is a BUG or Feature. If it is a Feature how does it handle the above scenario.
More update on this will be provided as soon as i receive.

:-) -- This is Tom Tucker from Channel 5 News -- :-)

Wednesday, May 21, 2014

4mb file size limit for DRM Imports

There is a 4mb limit on import file by DRM. This limit is only if the file is located on a client machine and not on the server.  so to address this limitation we have two choices

1. put the file on the server and using external connection use it in the import profile.
2. If you have DRM 11.1.2.2 then you can import from a database table or view. In the import profile select the database in source and set the tables/views information.

Note: You'll need one table/view per section. i.e. one for version, hierarchy,node,relation and hierarchy node.


Friday, May 16, 2014

Exporting Sequence Number from DRM

In DRM Version 11.1.2.2. there is a special category called Export Specific Category. This category is only visible in Export. This category has some auto generated properties that can come handy in special situations.

One such situation would be to send a auto-generated sequence number from an export. in order to do this

1. Create an export.
2. in the Column tab, select the Export Specific category and select the [Record ID] property.
3. set the filters/target and run the export.

Output from export should now have a auto-generated sequence numbers.

There are some other properties in the category too that i found in 11.1.2.3 (not sure if these are available in 11.1.2.2 ) 

1. Calculated Level  {0} -> Exports Level Numbers of the node starting with '0'. i.e. Top Node will be Level 0.
2. Calculated Level {1} -> Same as above but starts with '1'. i.e. Top Node will be Level 1.
3. Calculated Parent -> Automatically finds the parent node.

Give it a shot.

Thursday, March 6, 2014

Setting up Weblogic batch file as service

If you have configured shared srvices and weblogic to work with DRM (EBS integration) then you might have notices that to start/stop weblogic we have to run a batch file. 
running it manually is kind of pain so we wanted to see if we can run it as a service instead.

we used a utility called NSSM which can be used to add any batch file as service.

Give it a shot (but make sure your infrastructure allows you to use such utility first).

Thursday, February 13, 2014

Running DRM Batch file using Control-M Agent and DRM credentials utility

Here is a situation i got myself into and out. I created a batch file to run a simple export. I mapped drm user to windows user using drm credentials utility, this way i dont have to hardcode username and password for batch.

Issue: when the batch wass run manually it works just fine but it fails when it is executed by Control-M agent.
the error indicates batch failed because one of the required parameter username is not supplied.

Fix:
on the box where drm and control-m agent is installed, do the following


  1. Goto Administrative Tools->Services
  2. Select the Control-M/Agent Service
  3. Right Click->Properties
  4. Click Logon Tab
  5. Change the Logon as from "Local System Account" to "This Account"
  6. Enter the DRM windows username and password.
  7. Click Apply
  8. Click OK
  9. Restart the services.


Tuesday, February 11, 2014

Error while trying to communicate with DRM API Adapter at http://localhost:5240/oracle/drm/adapter?wsdl

Here is a fix for the above issue.. it took me 4 days to figure out what was happening....

1. Check if the url and port for the api adapter is correct. to test it just copy/paste the url in browser.














2. Check if you setup the api adapter in DRM configuration console. 
















3. Check if  you have created an external user in DRM and a user with the same name in shared services and a user with the same name and password in weblogic.