Track every DLL, OCX and SCR file use
Eliminate the risks of license non-compliance for your entire system
Save on software costs
Keep your network safe from the use of potentially unsafe screen savers (.SCR files)
|
|
Corporate Network Managers now have a simple, effective means of tracking and enforcing compliance - and staying legal - with all software license agreements including COM / ActiveX component use. Component License Broker™ is state-of-the-art in Software Asset Management tool that actively monitors and reports DLL / OCX file usage in real-time, ensuring your organization both complies with component vendor license agreements (thereby avoiding litigation) and is not paying for unused, often expensive licenses. Component License Broker™ when used in conjunction with License Broker™ ensures organizations have complete control over all software assets without the added technical complications, administrative overhead or financial burden. If you are merely interested in a static, on-demand IT audit tool and are not interested in on-going real-time compliance with software vendor license agreements, check out System Integrators' Integrated Auditor™ (What is license metering?). |
How does it work? |
Most all Windows applications rely on one or more reusable component in the form of COM / ActiveX DLL and OCX files. By tracking every DLL, OCX, SCR use in real-time, Component License Broker™ is able to both actively enforce license policies and passively detect the use of unlicensed or pirated software, whilst reporting usage statistics for software cost control. Organizations use Component License Broker™ to enforce license compliance on a varierty of applications and COM extensions including SAIC GeoRover® extensions such as DDT, LocusTrack, ZoomTools on ESRI® ArcMap™ application. Inbuilt reports show who is using what, when, to help you get the most from your software dollars by redistributing unused licenses and purchasing upgrades for only the software you actually use. You can also use Component License Broker™ to restrict access to potentially unsafe screen savers (.SCR files). Component License Broker™ is proactive and can alert you to major events via email such as low licenses and violated access attempts. End-users' day remains interruption-free as Component License Broker™ runs transparently in the background. |
|
|
|
Track every DLL, OCX and SCR file use |
|
|
Eliminate the risks of license non-compliance for your entire system |
|
|
Save on software costs |
|
|
Keep your network safe from the use of potentially unsafe screen savers (.SCR files) |
|
> Gain quick, easy access to real-time, system-wide software usage information |
||
> Have the ability to make upgrade decisions based on actual software usage needs |
Component License Broker™ is Client-Server technology that uses Web (TCP/IP) protocols to instantaneously transmit secure, small bytes of license usage information across your intranet. The simple, smart event-driven design uses minimal network bandwidth and system resources to deliver a stable, uninterrupted detection service. |
| ü | Scalable to grow with your environment. No new hardware usually required |
|
| ü | Monitor the use of every component (COM, ActiveX) in the system, including offline metering of laptops, for system-wide detection |
|
| ü | Efficient processing of data ensures optimized, real-time license distribution and enforcement (cached data from offline laptops and network downtime are transmitted upon server reconnection) |
|
| ü | Comprehensive licensing information is provided at point-of-need, helping you make more informed decisions about your licensing policies |
|
| ü | Report drill-downs provide for intuitive investigation paths and the painless data entry of new license policies (licensing details automatically load) |
|
| ü | Ability to easily define license policies for multiple versions of a DLL, OCX, SCR |
|
| ü | Administration is web-based, secure, easy-to-use and accessible from anywhere |
|
| ü | Easy to configure and distribute (via SMS, NT Server or Netware® login scripts). Unlike other tools, License Broker™ does not use wrapper technology (which adds another step to the distribution process and can cause conflicts with virus software) |
|
| ü | Ability to share real-time usage data with third-party XML enabled tools, such as Microsoft SQL Server 2000 |
|
| ü | Support for a host of licensing models, including: |
|
| ü | Ability to release and re-use seat licenses from retired PCs |
|
| ü | Ability to detect PCs where Component License Broker™ Client software is disabled or uninstalled to ensure tamper-proof monitoring |
|
| ü | Ability to customize engaging messages to end users related to component use |
|
| ü | Native support for Windows 2003 Server IIS 6.0 Worker Process Isolation mode |
| ü | Supports Windows NT, 2000, XP, 2003. Also supports Citrix® MetaFrame™ |
| ü | Network operating system independent - runs on Microsoft Windows NT Domain / 2000 Active Directory based networks as well as Novell® Netware® networks |
| ü | The License Server uses your corporate intranet server for secure administration (Internet Information Server 4.0/5.0/6.0) |
| ü | No dependence on external databases. Alternatively, interface Component License Broker™ with any DBMS from vendors such as Microsoft, Oracle® and MySQL |
|
Any Windows Platform |
Windows NT Server 4.0 or Windows 2000 Server or Windows 2003 Server or Small Business Server |
||||||
Running |
Internet Information Server 4.0/5.0/6.0 |
||||||
Optional - Mail Service |
Microsoft Exchange Server 5.5 or any other
Internet Mail Service |
||||||
Optional - ODBC Database |
Any DBMS via ODBC (tested with Microsoft SQL Server 6.5,
7.0, 2000; Oracle 7.2, 8i; Microsoft Access 97, 2000; MySQL 4.1) |
||||||
Hard disk space- Fixed |
15 MB |
||||||
Hard disk space- Variable |
The 'Stat' database table maintains a running statistics of all component activity by applications and drives the bulk of the variable disk space requirements. Each record in Stat table is 20 bytes long (refer 'Quick Start and Setup Guide' for table definitions). For a large site with 5000 users and each user running 50 applications a day with at least one component each, the disk space requirement per day will be 4.8 MB. |
||||||
Memory- Fixed |
503 KB |
||||||
Memory- Variable |
For each licensed component 518 bytes
Note: 'Licensed components' or 'app's' above refers to those components or applications on which license policy is being enforced. A typical site would enforce licensing on some 50 applications. The scenarios assume that all clients are running at least one of the licensed component or application and all components or applications are in use at any given time. Further the scenario assumes floating/concurrent license policy. For seat/user/group policies, add 196 bytes for each authorized/unauthorized seat/user/group policy definition for each licensed component or application. Unlicensed components and applications i.e. those for which a license policy is not defined, do not contribute to memory requirements - they simply contribute to hard disk space requirements in Stat table referenced above. The above memory requirements represent those of License Server only and are over and above IIS memory requirements. For example when a client runs an application or component, IIS must receive the license request and may allocate additional memory of 1 KB for each request, thus if 5000 users run applications or components simultaneously, IIS would allocate an additional 5 MB variable memory to process these requests! Administrator access is required for the system on which License Server is installed. Access to a web browser is required for License Server administration (either Microsoft Internet Explorer or Netscape Navigator). |
|
Windows Operating System |
- Windows 2000 Professional/Windows NT® Workstation 4.0 (x86) Service Pack 6, or |
Hard disk space |
- Windows NT/2000 = 2 MB |
Memory |
- Windows NT/2000 = 196 KB |
|
Each component or application launched by end users results in a HTTP license request frame approximately 64-96 bytes long from License Client to License Server and a HTTP response frame 1 byte long from License Server to License Client. The information transmitted comprises of the application information including its version, bitness and vendor information as well as login userid and machine name of client. Assuming a worst case scenario of a corporation with 5000 users and 50 application launches each day by every user, this results in a network bandwidth of 25 MB each day. |
|
|
> Component License Broker is Client-Server technology that uses Web (TCP/IP) protocols to instantaneously transmit secure, small bytes of license usage information across your intranet. We have a License Client for each flavor of Windows. |
Contact us to discuss your compliance requirements or simply to get pricing details. We price based on the number of PCs (in case of Terminal Server / Citrix MetaFrame, based on number of users). We offer a worldwide Education discount of 15%. |
|
|||
|
|
|
|
|
|
||
|
|
|
|
|
|
