4mb limit on DRM local client uploads

4mb limit on DRM local client uploads

DRM puts a 4mb limit restriction on loading a file from local system. It expects users to load larger files from the server. however it may not always be possible for us to get access to server. Here is a small tip to fix it.

1. create a shared folder on your local pc.

2. grant read/write access to the folder.

3. create an external connection in drm and point it to this folder, using the local pc IP address or the computer name.

e.g.

\192.168.1.100\sharedfolder

\mypcname\sharedfolder

Hierarchy and Node URL in DRM 11.1.2.2

Hierarchy and Node URL in DRM 11.1.2.2

This can be achieved by configuring the Web Farm on the configuration console. this is what you have to do.

1. Start Configuration Console and click on Host Machines Tab -> UI Web Servers -> Web Farm
2. Enter the following
   1. Host Name: localhost (or name of the server where DRM is installed).
   2. Port: 80 (Default)
   3. Path:/drm-web-client (default)
3. Click on the Test Url to make sure its working.
4. Click on Save Configuration. (You may have to restart the application if it doesnt work the first time).
5. Open your version->hierarchy. You should now see the Hierarchy Url property value populated.
6. You should also be able to get the url for any node within the hierarchy.

Hope it helps

Configuration Console Error

This error generally means two different users are trying to open the configuration console.

Fix: make sure one user exits from the console before others can open.

Check DRM Application Status

 

Here is a small vbscript that can be used to check if DRM Application is up and running, this will come handy if for any reason you want to check if application is up and may be kick off exports form batch utility. Or may be use this to notify support team whenever the application is down.

1. Create a text file with extension vbs. e.g. Check_Application_Status.vbs
Note: In the example i'm only checking for Engines,Services, Process Manager and netjnibridge. If you want you can include DRM-api-Adapter and event-host.

--- Here is the vbscript code ---
set service = GetObject("winmgmts:")
i=1
cnt=0
for each Process in Service.InstancesOf("Win32_Process")
If Process.Name="drm-engine.exe" Then
   i=i+1
   if i=2 then
      cnt=cnt+1
   end if
ElseIf Process.Name="drm-process-manager.exe" Then
   cnt=cnt+1
ElseIf Process.Name="drm-service.exe" Then
   cnt=cnt+1
ElseIf Process.Name="drm-netjnibridge-host.exe" Then
   cnt=cnt+1
End If
Next
If cnt >=4 Then
   Wscript.Quit(0)
Else
   Wscript.Quit(1)
End If
--- end of the vbscript code --- --- Batch File to call the vbscript ---
cscript Check_Application_Status.vbs
GoTo %ERRORLEVEL%

:0
echo Drm Services are up and running.
goto End

:1
echo DRM services are down. Please Restart.
goto End

:End

--- End of Batch File ---


hope it helps.

What's New in Version 11.1.2.1

Oracle Hyperion Data Relationship Management, Fusion Edition V.11.1.2.1 Release Highlights

Web 2.0 Interface: A new Web client provides access to the complete feature set of a Data Relationship Management application through a Web browser. It combines the functionality previously available in the desktop client and the Web Publishing casual user client into a Web 2.0 rich Internet applications experience. Presentation of data and access to features has been enriched to improve ease of use without compromising the power user experience of a desktop client.
Unicode Support: Unicode support allows the use of multi-byte character sets (MBCS) to handle multiple languages at the same time. Unicode support is available for user-defined metadata and data. Internationalization of date and float data types based on a user's locale is also included.
Role-based Security: Role-based security controls access to data and Data Relationship Management features. Multiple roles can be assigned to a user, allowing them to perform certain higher-level functions without giving them complete higher-level access. Security administration is now segregated from metadata administration to align with corporate policies that require this level of separation of duties. A new anonymous user role has been added to create tailored "read-only" views for different segments of casual business user audiences.
Multiple Applications, Single Server: Separate Data Relationship Management applications can operate on the same server to enable customers to physically segregate and independently manage different instances without requiring additional hardware or virtualization software. Different business groups are able to administer the metadata and data within their own applications without any impact to any other application.
External Connections: Administrators can set up common connections to external network resources that can be shared by all users. Imports and exports can directly access external connections instead of requiring a manual upload/download by a user. Centralized management of connections helps minimize maintenance of connectivity to network resources, particularly for migration scenarios across environments.
Coarse-grain Services: A new Java web service API provides improved interoperability with other Oracle Middleware and third-party Service-Oriented Architecture (SOA) applications. Policy management and message protection are now available using Oracle Web Services Manager.
Single Sign On: Data Relationship Management supports single sign-on using Oracle Access Manager. Single sign-on is available through the Data Relationship Management web user interface and web service API.
64-bit Support: 64-bit support is available for the web and application servers for Data Relationship Management. This includes certification for 64-bit Windows operating systems as well as increased memory addressability on the application server.
Workflow Development Kit: The Workflow Development Kit (WDK) enables the extended business user community to participate in master data governance processes via human workflows that allow them to create, modify, and approve changes prior to being applied to production data. The WDK provides a flexible, standards-based foundation to assist with the creation and deployment of a workflow-oriented solution built on Oracle Fusion Middleware 11g. The 11.1.2 release offers improved reusability and easy customization of components to meet customer-specific requirements.

This information has been copied from Oracle Website. All credit goes to Oracle.

Using Node Access Group with Primary and Alternative Hierarchies.

Requirement: Allow user to add/modify nodes only in alternative hierarchy. User should not be allowed to make changes to data from Primary Hierarchy directly/indirectly.

Solution:
1. Create a Node Access Group -> PrimaryRead.
2. Assign this NAG (Node Access Group) to the User.
3. Assign the same NAG to Primary Hierarchy with 'Read'.
4. Create another Node Access Group -> AlternativeWrite
5.Assign the NAG to user. 
6.Assign the NAG to Alternative Hierarchy with 'Add'.

Performance Tip

Performance Tip: Do not overload the application engines. If they get overloaded the entire application can stop. You'll have to restart the application.
This can happen even if your server's CPU and RAM is extreamly under used. The issue is more on DRM side.

Here are some reasons that will overload your application.

1. Running Large Action Scripts/Creating As of Versions/Saving a large version, Blending, Importing. In fact any large Write operations will put more load as there is only one write engine.
in such cases try to perform only one of these tasks at a time.

2. Running many exports at the same time. This may fail the exports with error like 'Unable to find Job # xxx'. Try to limit the number of exports you run simultaneously

Roles and Responsibilities

The below link tries to help you understand the roles and responsibilites in DRM.

Roles and Responsibilities

Derived Property Tip

Tip: A Derived Property that references to a local property value should always be created as a Global Derived Property. e.g. Top_Node_Level deriving PropValue(Core.Level) , then Top_Node_Level should be Derived Local.

New Feature Terms

Action Script Example

This document describes how to use action script.

Assumptions:

Version Name: Zions_09_2013

Hierarchy Name: Accounts

1. Open your browser and visit DRM web client url. e.g. http://localhost/drm-web-client OR http://servername/drm-web-client

2. Click Script link
3. 

4. Click on Browse button and select the action script file.
1. Make sure the delimiter used in the file matches the delimiter in the action script screen.
2. Click Load button to load the action script file.
3. You should now see the file contents at the bottom section.
4. Click on the green triangle button to run the script.
5. You should see the results of execution at the bottom. Any errors will be displayed.
    
5.