Home > Community > Blogs > PCB Design > what s good about adw s server metrics check out the 16 5 release and see
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the PCB Design blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

What's Good About ADW’s Server Metrics? Check out the 16.5 Release and See!

Comments(2)Filed under: PCB design, SPB, metrics, Allegro Design Workbench, PCB, Library flow, ADW, Library, design, data management, LRM, Library Revision Manager, design data management, SPB16.5, Allegro 16.5, Team design, configuration manager, server metrics, usage metrics

The Allegro Design Workbench (ADW) 16.5 has the capability of providing usage metrics.

By enabling analysis of the software environment, this enhances software serviceability and reduces IT costs. The ADW Server metrics are based on the ADW Server technology and enables metrics data to be collected from all sites and all clients.

Read on for more details …


As this is a new ADW capability offered in the 16.5 release, there are a limited number of initial metrics collected, namely version numbers of ADW and SPB tools and environment information. There are plans to extend metrics capability to design and process metrics.

How it works


The designer launches the ADW Flow Manager
The Flow Manager connects to the ADW metrics server
The Flow Manager sends data to server:

  •   User name
  •   OS info – architecture, version, etc
  •   Software version of ADW,  SPB, java, Tcl
  •   Environment variables

The ADW metric server displays some of these metrics. There is no need to have a metrics server for each replicated server.

The ADW Configuration Manager dashboard displays the collected metrics:




Detailed information for a single client:




The extended information is controlled by the $ADW_CONF_ROOT\adw_dashboard.ini file. This controls what command is executed:

  • On opening a project
  • Can be different for a different operating systems
  • Should be executable from the ADW Prompt
    • Put in $CDS_SITE/cdssetup/pcbdw/bin (inside $ADW_CONF_ROOT) that is in client PATH
  • Output of command is stored as “extended information”
  • Currently just text and basic HTML

Please share how you're using this new capability.

Jerry "GenPart" Grzenia

Comments(2)

By Soundman99 on February 27, 2014
This is great, but what I really would want to see is how long a user has each tool open, so that you can see license usage.  ADW already has checks for at least ADW version, and won't let you open if the client version doesn't match the server.  I have to monitor the FlexLM server to see how many licenses of each product we have checked out at a time, it would be nice to see this in the ADW server metrics.

By Jerry GenPart on February 27, 2014
Thanks Soundman99 for your suggestion. I will open a new Case and forward your enhancement request to our R&D team.
Jerry G.

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.