DevPartner

Forum Post: RE: DevPartner Finalizes DPS 11.1 Whats New

PDL — Mon, 13 May 2013 17:24:00 GMT

Sample code for the above posted IKnownFolder mismatch (Windows 7)...

WCHAR szBuffer[MAX_PATH]; IKnownFolderManager *pKnownFolderManager = NULL; HRESULT hr = CoCreateInstance(CLSID_KnownFolderManager,          NULL,           CLSCTX_INPROC_SERVER,          IID_IKnownFolderManager,          (void**)( &(pKnownFolderManager) )); if (SUCCEEDED(hr)) {  IKnownFolder* pKnownFolder = NULL;  HRESULT hr = pKnownFolderManager->GetFolder( FOLDERID_PicturesLibrary, &pKnownFolder);  if ( SUCCEEDED(hr) && pKnownFolder)  {   //extract path   LPWSTR pszPath(NULL);   hr = pKnownFolder->GetPath( 0, &pszPath);   if ( SUCCEEDED(hr) && pszPath)   {    wcscpy( szBuffer, pszPath );    CoTaskMemFree( (LPVOID) pszPath );   }   pKnownFolder->Release();  }  pKnownFolderManager->Release(); }

Forum Post: RE: DevPartner Studio 11.1 - MicroFocus License Management System

PDL — Wed, 01 May 2013 20:58:00 GMT

Found the Sentinel tools to show the usage - wlmAdmin.exe for Win32 UI, and lsmon.exe for Win32 command line, however, I am now looking for the method to force a remote user's license to be cleared in the case of a service problem (the user is not using any tool, yet the license is still being shown as used)...

Wiki: DevPartner Knowledge Base

Anonymous — Wed, 01 May 2013 03:10:00 GMT

Wiki: DevPartner - Code Analysis - Wiki

Anonymous — Wed, 01 May 2013 03:09:00 GMT

Wiki Page: Demystifying The Performance Analysis Session File

Anthony Hollis — Tue, 30 Apr 2013 22:10:00 GMT

Introduction

You have just installed DevPartner Studio, instrumented your application, and launched Performance Analysis. You are fired up and ready to go. Then it hits you, you have no idea what you are looking at, or any idea what this stuff means.

What are all of these numbers and columns?
How am I supposed to interpret this data?
How in the heck is any of this information useful to me?

Trust me, I've been there too!

At first glance, the Performance Analysis session file can appear a little daunting, however, the presentation of information makes more sense then you may realize.

What is Performance Analysis?

Let’s quickly cover what the component does. In a nutshell, Performance Analysis profiles distributed, and component-based applications. It collects performance data, COM method calls, etc, of which the server data is transmitted back to the client and automatically correlated into a single session file.

Moreover, the Performance Analyzer is used to collect the performance metrics of DLLs, source code files, assemblies, methods, functions, and line-level code. The session data made available to you, assists in highlighting performance issues, anywhere in your code, from third-party APIs, and or the operating system.

Session File Breakdown

The completion of a successful performance profiling session results in a session file with the extension of *.*.dpprf. By default, the session file has the naming convention of the profiled executable's name, appended with a numerical representation of subsequent runs.

When first displayed, the session file will be presented as a two-paned window. A tree list will display filtered data and the tabulated pane will display session data. (See Fig. 1)

Fig. 1

Filtered Pane

The tree list to the left is the filtered pane, listing the performance data from your profiled application (.exe, dll, .ocx, managed-assemblies, etc). Expanding the view of these components will display the timing metrics for each source file (.cpp, .vb, .cs, etc). *Note: The percentage in parentheses represents the total execution time. (See Fig. 2)

(Fig. 2)

Fig. 2 shows us that animationinstance.cpp, spent 0.3% of the session time in that section of the code. Whereas, dxut.cpp spent on 0.2%.

*Note: During the execution of MutliAnimation.exe, used for this demonstration, only certain parts of the application was executed, therefore, 0.0% metrics in certain areas.

If you look further down the tree in Fig. 2, you will notice that there is a high percentage listed for System. Usually, you will find that System produces the highest percentage of time.

By expanding the System node, you can research how your application uses system resources. However, keep in mind that it is your source code that controls the system, and it is up to you to determine where the actual performance losses may be coming from.

Data Pane

Next to the tree list is the data pane. The session data pane provides method level metrics. You have a total of three tabs available to you across the top: Method List, Source, and Session Summary. (See Fig. 3)

(Fig.3)

Information overload?

Not really. So what is the information actually telling us?

Let’s take a look at the method DXUTRender3DEnviornment(void). (See Fig. 3)

We can see that the time spent in the method is 0.0%, in actuality this is probably closer to 0.1%. But lets take a look at the time spent “with Children” which is 9.4%, and how many times our method was called - 2,984 times. This could be a possible candidate for further investigation.

First let’s discuss what some of these columns mean.

% in Method - indicates how much time was spent during the session percentage wise.
% with Children - indicates how much time was spent in the method, and any child methods.
Called - represents the number of times a particular method was called.
Average - the average execution time of the method.
Real - the average execution time of the method, and its child methods, including the time spent in threads of other processes. *Note: Real is the value also known as wall-clock-time.

Viewing the Source Code

The first item in this section that you may want to investigate are the lines with the highest amount of time associated with them. These lines of code represent the slowest executed lines.

Here is a quick rundown of the columns:

Count - indicates the number of times that a particular line of code was executed.
% of Method - indicates how much time was spent on a particular line of code, and the methods it calls as a percentage of the time spent in the entire method.
% with Children - indicates how much time is spent on a particular line of code, and the methods it calls as a percentage of the time spent during the session.
Time - the total time spent executing a particular line of code and the methods it calls during the session. (See Fig. 7)

(Fig. 7)

Conclusion

Well there you have it, a 50,000ft view of the Performance Analysis session file. Although we only touched on the high level details. You should now have a better understanding of Performance analysis, how to use it, and how to interpret the data.

For a more in-depth look at Performance Analysis, its available features, options, and configurations - please consult the DevPartner User Guide (Micro Focus, 2013, p. 207).

References

Micro Focus (2013). Understanding DevPartner -Chapter 7 “In-Depth Performance Analysis”(207).

Wiki Page: How To Profile A Native DLL Called From A C# Application

Anthony Hollis — Tue, 30 Apr 2013 22:09:00 GMT

Introduction

Profiling a DLL called from a .NET application is fairly straightforward. In this example, I will demonstrate how to profile a DLL called from a simple C# winform.

Steps

Instrument your native code with Error Detection
**If you would like to know how to build and instrument from the command line, view the knowledgebase article located here: http://community.microfocus.com/borland/develop/devpartner_-_code_analysis/w/knowledge_base/21152.msbuild-vs-nmvcbuild.aspx
From the menu of Visual Studio, select "Devpartner>C++ Instrumentation Manager".
Proceed to build your DLL project in Visual Studio.
Navigate to the standalone version of Error Detection: Start>Programs>Micro Focus> DevPartner>Error Detection.
Click File>Open and navigate to the executable that will invoke your DLL.
Click on Program and then Settings.
Navigate to Modules and Files.
From the Modules and Files Property Page, click Add Module and select the DLL you want to profile.
Click Ok.
To start, click on the Play button or navigate to Program>StartProgram>Start.

At this point, if you have instrumented your native code, Error Detection will begin the process of profiling your application for errors, memory leaks, etc.

For example, the application that I created is nothing more than a simple C++ DLL of which a memory leak, and a buffer overrun was added.

During the execution of my simple example, Error Detection reported the following:

Memory Leak Generated in DLL Code

Write Over Run Generated from DLL Code

*Note: If you are not seeing any profiled data. Locate your native DLL in the "Modules Tab" of the session file to verify instrumentation.

Wiki Page: How To Profile A Multiple Process Executable

Anthony Hollis — Tue, 30 Apr 2013 22:03:00 GMT

Introduction

This example will show you how simple it is to profile an application that spawns multiple executable's. These steps are also applicable for use with both “Coverage” and “Performance” Analysis. It is also important to mention that the duration of the session is directly related to the duration of the parent process. Meaning, during the profiling session, a separate performance or coverage file will be generated for each targeted child process. However, the session file for the parent process will get generated upon the termination of its process.

The overall architecture of the application used for this demonstration is fairly simple and straightforward, developed only to demonstrate the mechanics of the process. The parent process was written in C# and the child processes, a total of three, were written in Native C++.

Steps

1. Customize your .xml configuration file (samples of configuration files can be found @ C:\Program Files (x86)\Micro Focus\DevPartner Studio\Analysis\SampleConfigs)

XML Attributes of note:

SESSION_DIR- Specifies the folder that your generated session file will be saved into. If this attribute is not set, the session file generation will default to “My Documents”

SESSION_FILENAME – Specifies the customized name of the session file generated. By default, the executable name followed by a number will be appended to the session file, e.g., myApplication1.dpcov.

NM_METHOD_GRANULARITY – This is an optional attribute used to set data collection to method-level, line-level is used by default.

EXCLUDE_SYSTEM_DLLS – This is an optional attribute used to exclude system images.

FORCE_PROFILING – This is an optional attribute used to force the profiling of a executable written with C/C++ instrumentation or managed code.

This is only but a small sample of the attributes available to you for customizing your configuration file based on your needs. In addition to the xml attribute data, there are a number of switches that allow you to change the analysis type, how data is collected, and addressing session specific needs. For a more in-depth overview consult the DevPartner Studio Users Guide (Micro Focus, 2013, p. 109)

Here is a sample of the xml file used for this example. A number of the available attributes were omitted for sake of simplicity. There are numerous xml attributes available for custom configurations.

XML Configuration Example

<?xml version="1.0" ?>

<ProductConfiguration xmlns="http://www.microfocus.com/products">
<RuntimeAnalysis Type="Coverage" />

<Targets>

<!- Parent Process ->

<Process CollectData="true" Spawn="true" Primary="true" NoWaitForCompletion="false" NewConsole="false">                         <AnalysisOptions NM_METHOD_GRANULARITY="0" NM_ALLOW_INLINING="1" SESSION_FILENAME=""    SESSION_DIR="C:\_source\projects\vs2010\CommunityArticle3\profileData"/>    <Path>C:\_source\projects\vs2010\CommunityArticle3\CommunityArticle3.exe</Path>
     <WorkingDirectory>C:\_source\projects\vs2010\CommunityArticle3\</WorkingDirectory>
  </Process>

<!- Child Process ->

<Process CollectData="true" Spawn="true" NoWaitForCompletion="false" NewConsole="false"> <AnalysisOptions NM_METHOD_GRANULARITY="0" NM_ALLOW_INLINING="1" SESSION_FILENAME="" SESSION_DIR="C:\_source\projects\vs2010\CommunityArticle3\profileData"/> <Path>C:\_source\projects\vs2010\CommunityArticle3\sampleAppThree.exe</Path> <WorkingDirectory>C:\_source\projects\vs2010\CommunityArticle3\</WorkingDirectory>
</Process>

</Targets>
</ProductConfiguration>

2. Calling your configuration file from the Command Line

*For convenience and ease of use, placing the DPAnalysis.exe executable in the system “path” is desirable.

From the command line, invoke DPAnalysis: C:\ [ Application Process Directory ] \ dpanalysis /config NameOfYourConfigFile.xml

Once executed, a session dialog box will appear allowing you to control the session, e.g., pausing, taking additional snapshots, and or terminating the session.

For this example, the parent process is named “CommunityArticle3”. The parent process will spawn three additional processes, "sampleAppOne", "sampleAppTwo", and "sampleAppThree".

Upon the completion of each child process a session file is generated.

(SampleAppOne.exe – Session File)

(SampleAppTwo.exe – Session File)

(SampleAppThree.exe – Session File)

A session file is generated for the parent process after termination.

(CommunityArticle3.exe – Session File)

The session file data for each profiled process will remain open. Allowing you the option to print the coverage data, view the profiled source code, and or export to ether XML or CSV formats.

Here is an example of the coverage data for one of the processes profiled in this example.

To learn more about profiling for Coverage or Performance Analysis, consult the DevPartner Studio User Guide (Micro Focus, 2013, p. 109),

References

Micro Focus (2013). Understanding DevPartner -Chapter 4 “Automatic Code Coverage”(109).

Wiki Page: Missing VCBuild For VS2003

Anthony Hollis — Tue, 30 Apr 2013 21:19:00 GMT

Problem:

If you attempt to build an application with instrumentation for Dev Partner Studio from the command line, the documentation advises you to use nmvcbuild.exe for Visual Studio 2003 for DPS 8.2.4 and earlier. However, nmvcbuild.exe attempts to invoke vcbuild.exe which was not shipped with VS 2003. The documentation also advises that you can download vcbuild.exe for VS 2003 directly from Microsoft.

Resolution:

You can try downloading vcbuild.exe for VS 2003 from the following link:
http://web.archive.org/web/20051103044322/http://www.gotdotnet.com/team/cplusplus/samples/vcbuild.zip

Additional Information with further alternatives:

http://community.microfocus.com/borland/develop/devpartner_-_code_analysis/w/knowledge_base/21213.com-interface-tracking.aspx

Wiki Page: Problems with Terminating DPS When Running As Limited User on Windows XP

Angela — Wed, 03 Apr 2013 12:44:00 GMT

Created On: June 7, 2010

Problem:

On Windows XP it is possible to run DevPartner Studio from a limited account. However if you run Error Detection on an application, you will run into a problem when you attempt to close the “DevPartner Error Detection – Active Session” tab. When you attempt to close the tab, the message “You cannot close this window while debugging.” will be displayed.

Resolution:

Modify the local security policy of the XP machine in question to give the limited account the “Debug programs” permission.

2455625

Old KB# 31155

Wiki Page: Installation repair on DevPartner 10.5 causes Error Detection to crash

Angela — Wed, 03 Apr 2013 12:43:00 GMT

Created On: 11/7/2011

Problem:

If a customer performs a repair on the product, the registry value for “Coredir” is appeneded with \x64\ which will cause BoundsChecker to crash.

Resolution:

Fix: Delete \x64\ in the registry at the end of the string value.

Known issue.

Old KB# 35181

Wiki Page: DP Analysis Remote Profiling procedure on VISTA OS or later

Angela — Wed, 03 Apr 2013 12:42:00 GMT

Created On: 11/7/2011

Problem:

Updated procedure for DP Analysis Remote Profiling on VISTA OS or later (Win 7, Win 2008, etc.).

Resolution:

FIREWALL CONFIGURATION
• Local and Remote Machine (Windows Firewall)
- Add an inbound/outbound rule for NCS.EXE process with all ports enabled.
- Add a connection security rule for the IP address of the other endpoint machine to allow connection (e.g. the rule in the Local machine specifies the IP of the Remote machine to be exempted from authentication requirements and vice versa)

• Remote Machine (Windows Firewall)
- Add an inbound/outbound rule for TCP port 37493.

COMPONENT SERVICES
• Local and Remote Machine
1. From the Start menu, type DCOMCNFG.EXE at the Search box.
2. Execute the DCOMCNFG.EXE from the search result. This opens the Component Services application.
3. On the tree view at the left side of the GUI, navigate to Console Root  Component Services  Computers  My Computer. Right-click on My Computer and select Properties from the context menu.
4. On My Computer Properties dialog, select the COM Security tab.
5. Under Access Permissions, select Edit Limits… button and make these changes:
a. Click Add… and enter Authenticated Users
b. Provide Local and Remote access by enabling the corresponding check box.
c. Click OK button to apply changes
6. For Win2008/2008R2 only:
a. Add the Distributed COM Users group having Local and Remote access by following step 5.
b. Under Launch and Activation Permissions section, select Edit Limits… button and make sure that the Distributed COM Users have permissions for Local Launch, Remote Launch, Local Activation and Remote Activation. If the said user group is missing, then add it and apply the corresponding permissions.
7. Click OK to apply changes and to close the My Computer Properties dialog.

MACHINE LOCAL SECURITY POLICY
• Local and Remote Machine
1. In the Control Panel, open Administrative Tools  Local Security Policy  Local Policies  Security Options.
2. Open the properties for Network Access: Let Everyone permissions apply to anonymous users.
3. Select the Enabled radio button and click OK to apply changes.

RECOMMENDATIONS
Starting from Vista OS, the following items also need to be considered in order for the Remote Profiling feature to work properly.
• A user with administrative privilege is necessary for configuring DP Remote Profiling because user elevation as Administrator is needed when setting up the security requirements in the Local and Remote machine.
• Win 7 OS, Win2008/2008R2: The changes made to both Component Services and Machine Local Security Policy will require a machine reboot to fully take effect.
• If a 3rd party anti-virus program is managing the windows firewall (e.g. Symantec Endpoint Protection), define the firewall rules (program, port, IP) in the managing application rather than in the Windows Firewall console. The reason for this is that the rules in the managing application takes precedence over the Windows firewall rules.
• Make sure the firewall rules necessary for Remote Profiling (program, port and IP) takes priority over the existing firewall rules esp. if the firewall has the means to prioritize rules (topmost rule in the list is the highest).
• If ever the Local and Remote machines are running in a virtual environment (e.g. VMWare Workstation), make sure that the security application (e.g. Symantec Endpoint Protection) of the Host machine allows communication on the IPs used by both Local, Remote machine and the virtual network.
• Any name and MAC address conflicts on the network esp. when using cloned virtual machines affects Remote Profiling functionality.
• Never use the Force Profiling switch /f for DPAnalysis when remote profiling an application with a .NET module loaded (aka mix-mode) or a pure .NET application because it leads to initialization issues especially if it is a 64-bit process.

------------------------------

The existing procedure we have for Remote Profiling found in our product doc “Understanding DevPartner Studio” still holds true for WinXP or older OS. Thus the procedure described above is intended as an additional information when configure machines having VISTA or later OS (Win7, Win2008/2008R2).

none

Old KB# 35182

Wiki Page: Executables and or Modules outside of current project scope are included during profiling

Angela — Wed, 03 Apr 2013 12:42:00 GMT

Problem:

Session file data has information that is not relevant to the current project/solution. Or, under "Modules & Files", the list indicates executables and modules that are being profiled during the session but may not be relevant or desired by the user.

Resolution:

During the first run with Error Detection, "Modules & Files" which is located in the DevPartner options will list all of the modules and executables that were loaded with the application's process space. After reviewing your session file, if you notice extra information that is not a part of your application, or additional "noise", you can exclude that information by deselecting any modules or files from within the list.

1. Go to "DevPartner>Options>Error Detection>Modules and Files"
2. Uncheck modules as necessary

*Note: After the exclusion of any extra modules, there may be noticeable gain in performance.

Wiki Page: DevPartner 10.0 - Pressing the instrumentation button in Visual Studio causes a 3-4 minute delay

Angela — Wed, 03 Apr 2013 12:41:00 GMT

Created On: 11/7/2011

Problem:

For DevPartner version 10.0, the issue is that under Visual Studio 2010 when selecting the instrument icon for Error Detection Instrumentation, Visual Studio goes into a NOT RESPONDING state and stays that way for between 3 and 4 minutes. Error Detection does appear to work after the 3 - 4 minutes, but whether enabling or disabling the C/C++ instrumentation prior to building, it is the long delay that is not satisfactory. This is not perceived in Visual Studio 2008.

Resolution:

The reason this behavior is not noticed in VS2008 is because Microsoft had made changes in VS2010, namely changing the build platform to MSBUILD. Based on how MSBUILD works and how we need to cycle through every user file for each project to modify the instrumentation state; the larger the project number, the longer it will take for us to turn on instrumentation. Unfortunately, this is working as designed and the only option is to request an Enhancement Change from Microsoft to change the build sequence. So long as you leave instrumentation on, you will only see this delay hit once until you turn it off again.

NOTE: Changes to the code logic in 10.5 have sped up up the turning on/off of Instrumentation

2463773

Old KB# 35183

Wiki Page: DevPartner installation hangs at "Create New Rules" step

Angela — Wed, 03 Apr 2013 12:41:00 GMT

Created On: 11/7/2011

Problem:

When trying to install DevPartner on Windows 7 machine, the installation is hanging at the "create new rules" step. Nothing works any further. (Windows 7 / 64bit).

Resolution:

The step that the install is failing at is indicative of the system's inability to read the VBscript. It could be that the VBscript engine is disabled, but either way, please run this Microsoft fix:

http://go.microsoft.com/?linkid=9648765

2488732

Old KB# 35179

Wiki Page: 'WatchListErrorCode=ErrorAlreadyExists

Angela — Wed, 03 Apr 2013 12:40:00 GMT

Created On:

Problem:

After installing DevPartner 10.5.2 and running Error Detection, we get "Error: There was an error injecting the process. The error returned was: 'WatchListErrorCode=ErrorAlreadyExists'. Please contact support for help."

Followed by:
[CRunManager::InjectNow() - BCAX::StartRecording() FAILED: hr=0x80004005]

Resolution:

Check the Project Properties. Once you have the Property Pages up, go to Configuration Properties > General and check that the Output and Intermediate Directories do not have a ".\” anywhere in the path(s). If it is present, then please delete the ".\".

Next Check Configuration Properties > Debugging and ensure that the Command value does not have a ".\" value as well. You can check this by selecting the Text Box for the value and choosing "Edit" from the Dropdown menu. This will bring up the whole string, but more often than not what is there by default is usually just the $(TargetPath) macro.

Save the settings and restart Visual Studio.

2537404

Old KB# 35178

Wiki Page: MSBuild vs NMVCBuild

Anthony Hollis — Tue, 02 Apr 2013 16:34:00 GMT

Problem:

When building with instrumentation from the command line, and depending on your version of Visual Studio, you will either have to invoke MSBuild or NMVCBuild. Without understanding the differences in setup for either build utility, chances are, attempting to successfully build your solution may prove difficult.

Resolution:

*For Visual Studio Versions 2008 and prior

1. Ensure that NMVCBUILD is in the "path" (Enviornment Settings)

2. Ensure that VCBuild is in the "path" (Environment Settings)

3. When opening a command prompt, navigate to the vcvars32.bat from the version of Visual Studio that your project was created from, and execute from that directory.

4. To execute the build from the command line, navigate to your project and run the following: “nmvcbuild/nmbcon projectName.proj"

*For Visual Studio Version 2010 and onward

**NMVCBuild and VCbuilld are now irrelevant

1. Open a command window, navigate to vcvars32.bat from the version of Visual studio used for your project

2. From the command line, navigate to the folder that has the "sln" file and excute the following: "msbuild projectName.sln"

*Note: MSBuild is ran against the solution file, whereas NMVCBbuild in VS2008 and prior is ran against the project file.

Wiki Page: Knowledge Base

Jon Bourne — Mon, 18 Feb 2013 13:14:00 GMT

Welcome to the DevPartner Knowledge Base. The Knowledge Base contains a large amount of information that may answer any technical questions you have. To take full advantage of the Knowledge Bases across the Community please use the site search found in the top right hand corner of your Internet page. This search offers a wide range of customisation to narrow down your search to find your article. If you fail to find a solution here SupportLine will be able to assist you further.

Wiki Page: DevPartnerJava compatibility with IE 9

admin — Sat, 16 Feb 2013 03:39:00 GMT

Created On: 20 July 2012

Problem:

Windows users will be upgrading to Internet Explorer 9 as part of Windows Updates, but still need to use the browser to display the DevPartner for Java Graphical User Interface.

Resolution:

No formal testing has been compatible with Internet Explorer 9. But cursory testing indicates that as long as the Java plugin is from a Oracle Java JRE 1.6 version 24 or later, Internet Explorer seems to be compatible with DevPartner for Java 4.5.

Incident #2583930

Old KB# 36131

Wiki Page: Install CES licenses in DevPartner 10.6

admin — Sat, 16 Feb 2013 03:39:00 GMT

Created On: 23 July 2012

Problem:

With the migration of DevPartner from DLM to CES Safenet Sentinal licensing systems the method of installing licenses will change from file based authorization to authorization based licensing.

Resolution:

1. Open up the Micro Focus Licensing System Administration Tool "C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WINNT\CesAdminTool.exe" or use the GUI. Continue with Step 2 if the license will be installed on this machine. If the license has already been installed on a central license server, skip to Step 5.

2. Click on the Authorize tab. In the "Enter authorization code:" dialog box, clear the "Input your authorization code" string and enter the 16 digit hexadecimal authorization code you received via email.

3. Note if the DevPartner product you purchased is displayed under the Licenses tab.

4. Net stop and restart mfcesd or reboot. Under Windows Services it will be noted as "Micro Focus CES daemon". Use steps 5 and 6 below only if the license resides on a remote server.

5. After launching the License Management System tool as in step 1. Open Options/ Advanced Configuration to display the Advanced Configuration dialog box.

6. Change the value of "License Server" from 127.0.0.1 to the address of your license server. You may try the short name, but if that does not work, try the v4 IP address of that server.

Ensure that port 5093 is opened to permit the license client to communicate with the server.

Old KB# 36136

Wiki Page: Support for borrowing licenses with DevPartner 10.6

admin — Sat, 16 Feb 2013 03:39:00 GMT

Created On: 23 July 2012

Problem:

Support for borrowing licenses is available upon request for DevPartner 10.5 and earlier version concurrent licenses. With the migration of the licensing system used by DevPartner from DLM to CES Safenet Sentinel there will still be a need for borrowing licensese for users without network access to the CES Safenet Sentinel License Server.

Resolution:

The standard DevPartner 10.6 concurrent license key has support for Commuting, which has the same functionality as Borrowing under DLM in prior versions of DevPartner. To commute a license to the client PC, open up the Micro Focus License Administration Utility and navigate to the Commuter Tab. Select on the Product to be Commuted, for example DPS Professional 10.6 and click on the "Commute" button. The license will not be available for any other user or machine until the license is returned. To return the license, open up the Micro Focus License Administration Utility and navigate to the Commuter Tab. Select on the Product to be Commuted, for example DPS Professional 10.6 and click on the "Return License" button.

Old KB# 36137