DRM error – Request Operation Sent to net.tcp://Server:port/oracle/drm/engine/jobmgr Did not Receive a Reply Within the Configured Timeout (01:00:00)


1. When running an export via the DRM batch client, the following error is seen:

Error received from DRM Process Manager service using address: net.tcp://server:port/Oracle/Drm/ProcessManager/: This request operation sent to net.tcp://server:port/Oracle/Drm/Engine/JobMgr did not receive a reply within the configured timeout (01:00:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.”

2. The export takes a long time to run.
3. The export saves the results of the export to a local file.

This problem is resolved in 11.1.2.1.00.

Workaround

1. Set up an external connection in the DRM Web Client from Administer > New > External Connection.
2. Modify your export to use the external connection rather than a local file.
3. Make sure that the following have not been configured as they could override the external connection that has been set for the export:
a. The ‘/outfile=’ flag has not been used in the command line export parameters for the batch client.
b. The ‘OutFile=’ parameter has not been used in the configuration file .
5. Run your export via the batch client again.

Thanks,
~KKT~

Advertisements

DRM Web Service Test Fails With Error: “‘PolicySet Invalid: WSM-06102’ But the Policy Does Exist”


Testing the DRM web service in Enterprise Manager fails with an error like the following where the referenced security policy is a valid policy:

java.lang.Exception:
oracle.sysman.em.SDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI “oracle/wss11_saml_token_with_message_protection_client_policy” is not valid.

The security polices can be validated by accessing the following URL if wsm-pm has been deployed to the FoundationServices cluster, is using the default port and you are testing from the admin server machine:

http://localhost:28080/wsm-pm/validator

Reason – The Oracle Web Service Policy Manager (wsm-pm application) may not be started or may not be able to be contacted.

To fix-

1. Ensure that the domain has been extended to include the Oracle WSM Policy Manager using the Weblogic Domain Configuration utility: C:\Oracle\Middleware\wlserver_10.3\common\bin\config.exe. If the domain has not been extended then extend the domain using the Weblogic Domain Configuration utility.

Check domain is extended for wsm-pm.

2. If #1 has been confirmed and there are still problems then ensure that the wsm-pm web application that has been used to secure the DRM web service has been started in the Weblogic Administration Console (http://server:7001/console) > Domain Structure > Deployments.

Check that wsm-pm is started.

3. Ensure that the server where the DRM web service has been deployed is a target for the wsm-pm web application (note: FoundationServices is in the screenshot below but the DRM web service may have been deployed somewhere else). To do this from the Weblogic administration console go to: Domain Structure > Deployments > wsm-pm > Targets > Current Targets.

Check that wsm-pm is correctly targeted.

4. If the location where the DRM web service has been deployed is not a target then click Lock & Edit (top left) > tick the box next to wsm-pm Enterprise Application > click Change Targets > tick the relevant location > click Yes > then Activate Changes (top right).

Thanks,
~KKT~

When Upgrading DRM Repository Error: “ORA-03114: not connected to ORACLE”


When copying the DRM repository with the repository wizard the following error is seen whilst ‘Applying updates …’ has been running for some time (i.e. not immediately):

ORA-03114: not connected to ORACLE

Reason – A network device may be dropping idle connections after a certain period of time.

In order to see if this is the issue that you are facing:

1. Note how long it takes before the ‘ORA-03114: not connected to ORACLE’ error is seen when upgrading the DRM repository.
2. Ask your DBA to locate the server side copy of sqlnet.ora and set the SQLNET.EXPIRE_TIME parameter to a value lower than the time taken for the ORA-03114 to appear.

For example:

1. If the ORA-03114 is being seen after 60 minutes and the SQLNET.EXPIRE_TIME parameter has been set to 60 minutes (SQLNET.EXPIRE_TIME = 60) or higher try a setting like this:

SQLNET.EXPIRE_TIME = 50
2. If the ORA-03114 is being seen after 60 minutes and the SQLNET.EXPIRE_TIME parameter is not present in the sqlnet.ora then this means that the default value of SQLNET.EXPIRE_TIME = 0 will be used. In this case add a row like the following to the sqlnet.ora

SQLNET.EXPIRE_TIME = 50
The main thing here is that SQLNET.EXPIRE_TIME is set to a lower value than the time taken for the ORA-03114 to be seen.

Thanks,
~KKT~

DRM External Connection Using TNS Alias Name for Oracle DataBase failover


How to setup TNS alias name with DRM to use failover with Oracle Database?

* Navigate to the Instant Client ODP.NET DB driver located in DRM app server:
E:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\server\odp\network\admin

* Create a TNSNAMES.ORA file with the TNS ALIAS information

* During the External connection creation for Application in DRM Console, Select the Database as ‘Oracle’ and in the connection string specify the value as :
” Data Source = ”

* Test and verify the DB connection.

Thanks,
~KKT~

DRM- How to Lock DRM Users Out of Applicaition for Short Periods of Time


What are the ways to lock DRM users out for short periods of time?

There is no one way to lock people out of DRM. Some workarounds would include the following depending on how DRM is configured:

1. If user are CSS ( shared service users) one could change the authentication mode of DRM to be just internal. Bounce DRM; Then use only an internal user to run the updates.

2. One could go through and change each user in DRM to Lock them out but this is very manual and if there are a lot of users , time consuming

3. If user are apart of NAG’s, then all of the roles could be revoked, then added back after the black out period is over

Thanks,

~KKT~

DRM – How to create a workflow model


The new request tab under worklist is greyed out for the user as workflow model was not created.

Scenario: Create a Workflow Model(WFM) which has two stages one is Submit and the other is Commit. This WFM is used for adding new base node.

1.Create users with the below roles:

Governance user, governance manager and workflow user

2.Create required Node Access Group(NAG).

3.Create the workflow task.

4.Create the workflow model.

–Click on Edit of Submit Stage in Action column and assign Workflow Task and Node Access Group to that Stage.

–Select the respective Workflow Task in the available list and push to selected list.

–Select the respective NAG in available list and push to selected list.

–Click on Save which is on the right-hand side

–Click on Edit of Commit Stage in Action column and assign Node Access Group to that Stage

–Select the respective NAG in Available list and push to selected list

Note: No Workflow Task will be there in Commit Stage.

–After completion of all Stages updates, Click on Save.

5.Assigning Hierarchy Node Access to NAGs
–Login to DRM.

–Select Version and open respective hierarchy.

–Go to Nodes->Assign->Node Access

–Select respective NAG group and select the appropriate access level and click on Save.

 

The new request tab in the work list will be available now.

DRM Learning – Export global nodes


Exporting global nodes is useful when you want to output a list of nodes from a version without specifying hierarchy information; for example, a master list of projects, a report of inactive customers, or a list of employees who are not assigned to a cost center.

For this type of export, configure the export wizard tabs as follows:

  • Source—Select a normal, baseline, or as-of version.
  • Style—Indicate whether to export all nodes or only limb or leaf nodes. You can include implicitly shared nodes, if necessary.
  • Filter—Define a query or validation. Only nodes that meet the query criteria or that fail the validation are exported.
  • Columns—Select properties, including version and global properties, for output columns in the export. You can include as many properties as needed. For example, you may want to include a node’s name, description, and parent node name.
  • Target—Specify whether to export results to a client file, a server file, or a database table. If you export to a database table, you must also specify the database table.

Begin by navigating to the Export task group. Use the Export task group to create and manage exports.

Screenshot for Step

Click the New Export () button.

Screenshot for Step

Use the Choose Export Type dialog box to select an export type (hierarchy, comparison, version, property, or log).

Click Version.

Screenshot for Step

Use the export wizard to define the source, style, filter, columns, and target for the export. You begin on the Source tab.

Use the Source tab to specify the version that you want to export. You can select a normal, baseline, or as-of version. In this example, you leave the [Default Current Version] – 2010 03 – Production normal version selected. Click the Style tab.

Screenshot for Step

Use the Style tab to specify the type of nodes to be included in the export and to specify whether to include implicitly shared nodes.

Perform the following actions on the Style tab:

  • Click the Leaf Nodes Only option.
  • Leave the Include Implicitly Shared Nodes option cleared. This option enables you to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are exported only if they are not filtered out by another option. If you use a query filter in the export, you must explicitly include the shared nodes.

Screenshot for Step

Click the Filter tab.

Screenshot for Step

Use the Filter tab to define filter criteria for the exported data. Only nodes that fail the validation or that meet the query criteria are included in the export results.

In the Query list, select North America Cost Centers.

Screenshot for Step

The Description field displays the query criteria.

Click the Columns tab.

Screenshot for Step

Use the Columns tab to select global properties for the export. In this example, you export Name, Description, and Region (in that order).

In the Available list, click Description.

Screenshot for Step

Click the Select () button.

Screenshot for Step

The Description property is displayed in the Selected list.

In the Available list, click Name.

Screenshot for Step

Click the Select () button.

Screenshot for Step

The Name property is displayed in the Selected list.

Click the Category drop-down list.

Screenshot for Step

In the Category drop-down list, select Location.

Screenshot for Step

In the Available list, click Region.

Screenshot for Step

Click the Select () button

Screenshot for Step

The Region property is displayed in the Selected list.

Make the Name property the first in the Selected list. Click 2 – Name.

Screenshot for Step

Click the Move Up () button.

The Name property is displayed first in the Selected list.

Click the Target tab.

Screenshot for Step

Use the Target tab to configure where the data is to be exported and the format of the exported results.

In the Device drop-down list, select Client File to export data to a client file.

Screenshot for Step

In the Field Delimiter drop-down list, select (Comma) to indicate the field delimiter character and record delimiter character. In this example, you use commas for the field delimiter.

Screenshot for Step

Click the Save As () button to save the export to the repository .

Screenshot for Step

Use the Save Export As dialog box to specify a name, a description, and an access level for your export.

In the Save Export As dialog box, perform the following actions:

  • In the Name field, enter North America Cost Centers.
  • Optional. In the Description field, enter a meaningful description of the new export. For example, enter North America Cost Centers.
  • In the Object Access Level drop-down list, select Standard. The Object Access Level field assigns one of the following access levels:
    • User—Enables only you to run and edit the blender
    • Standard—Enables all users to run the blender, but only users with the Data Manager role can edit it

Screenshot for Step

Click OK. The tab name is displayed as North America Cost Centers.

Screenshot for Step

Click the Run () button to process the export.

Screenshot for Step

The File Download dialog box is displayed. Use the File Download dialog box to open or save the export results. You can also cancel the export, if necessary.

Click Open.

Screenshot for Step

The export results are displayed in Notepad.

 

DRM- Cross Referencing Nodes in Another Hierarchy


I am getting a lot of questions now a days on DRM cross referencing nodes and how to achieve this.

let’s say we want a property to hold a comma-separated list of nodes in the Accounts hierarchy where a certain property value matches one in the current node.

For example, a list property has certain values, e.g. HR, Finance, Legal, etc. Nodes in the Services hierarchy need a list of nodes in Accounts where this value matches.

Any solution that traverses a whole hierarchy for each execution of a formula, i.e. for every node in another hierarchy, would have performance implications once the number of nodes rose above a few thousand.

Here we describe how to use a lookup table for the list. A property (e.g. ‘AccountLookup’) needs to be created with a lookup table pre-populated with the list of those nodes in the Accounts hierarchy that have each possible entry, e.g.

HR – 001,002,003,…
Finance – 004,005,006,…
Legal – 007,008,009,…

The cross reference property should be a string lookup property, with AccountLookup as the lookup property and the value the list property.

Populating the lookup table is not so straightforward. My proposal is this:

1. Create an export for each possible value of the list property (‘ListProp’). The first export, ExportHR, has the top of hierarchy Account as its top node, recurses, has a single column, NAME, and an in-line query filter: “ListProp Equal HR”. On the Target tab, export to client file with the Field Delimiter set to None and record delimiter set to comma. This produces a file with a single line. In the Header field enter HR. The result is this:
HR,001,002,003,
2. Copy this export to ExportFinance, replace the filter value with  “ListProp Equal Finance” and put Finance in the Header field
3. Repeat for Legal and all other members of the list.
4. Combine these exports into a book, exporting to client file and selecting ‘Include Combined Export Output File’ with Combined.txt as the filename. This book now produces a zip file, which if you open it in Windows Explorer can be drilled down into to find Combined.txt, which looks like this:

Finance,007,008,009,
HR,001,002,003,
Legal,004,005,006,
etc.

5. If you use the Migration Utility to export the ISSrelatedCoA property, it contains a section like this:

<drm:LookupValues>
<drm:PropLookupValue>
<drm:LookupValue>Finance</drm:LookupValue>
<drm:ResultValue>007,008,009</drm:ResultValue>
</drm:PropLookupValue>
<drm:PropLookupValue>
<drm:LookupValue>HR</drm:LookupValue>
<drm:ResultValue>001,002,003</drm:ResultValue>
</drm:PropLookupValue>
<drm:PropLookupValue>
<drm:LookupValue>Legal</drm:LookupValue>
<drm:ResultValue>004,005,006</drm:ResultValue>
</drm:PropLookupValue>
</drm:LookupValues>

It should be possible to merge Combined.txt with XML like above to create Migration Utility import. You might use a utility or XSLT for this. Note that the XML file must be complete, i.e. not only contain the above!

The lookup table must be refreshed whenever the Accounts hierarchy or its ListProp values change.

— Comments and questions welcome.

 

 

What caused the Data Relationship Management (DRM) Environment to Restart Reboot Suddenly


The IIS Application pool Recycling was not configured or is miss-configured . Without this configured IIS will continue to use memory for the web application until its allotted memory is full. It will then recycle to clear the memory. This happens all existing session are terminated. Since DRM work primarily in memory all data not saved to the database will be lost.

To configure this parameter follow these steps:

To open IIS Manager from the Start menu

Click System and Security, and then click Administrative Tools.

In the Administrative Tools window, double-click Internet Information Services (IIS) Manager.
To open IIS Manager from the Search box

Click Start.
In the Start Search box, type inetmgr and press ENTER.

In the Connections pane, expand the server node
Click Application Pools.
On the Application Pools page, select an application pool generally drm_pool,
Click Recycling in the Actions pane
Click the box next to Specific time
In the box below enter a non business time ( IE 2:30 AM)
Click next
Click Finish
Click Recycle on the right hand side ( this will activate the changes)

Close IIS Manager

Saving DRM as-of-version


As-Of versions can not saved directly because they are intended for temporary analysis.

Indirectly, however, in the DRM interface, copy the As-Of version with a new name and the newly created copy can be saved.

Via the batch client :

Use the batch client to export an as of version to file.

Please see https://docs.oracle.com/cd/E40248_01/epm.1112/drm_user_11123500/frameset.htm?ch16.html for the parameters that can be used in the Export Section of Configuration File