Home > Articles > Programming > Windows Programming

Like this article? We recommend

DDS System Processes

Because the best way to ensure the viability and stability of the production system is to ensure that no one has the right to disrupt it, most organizations don't want to give installation rights to local developers. For this reason, the core components of the production system should include distributed application support. Each corporate-wide development tool should include a runtime version. This means that all of the program components required to execute a program written by the development tool can be separated from the program and installed independently. These are the components that require installation rights on a Windows 2000/XP system because they must be integrated and registered in the system. These components can be included into the basic system, thus eliminating the need for decentralized installation. Files created for application enhancement can be copied to the system instead of installed on the system. And since all users have file copy rights to specific folders, decentralized applications can easily be installed without actually giving installation rights to developers.

For example, Microsoft Access and Microsoft Visual Basic for Applications both include runtime editions. These runtime versions must be included into the corporate system (see Figure 1). Like all other system components, they must be managed and updated as required. When developers create applications, they must ensure that the applications are designed to run with runtime components, instead of requiring the actual application to run. Thus when developers must "install" an application, all they need to do is copy the files to appropriate locations on the PC, since the runtime is already included into the system. They don't need to have elevated rights to do this.

Figure 1Figure 1 A corporate production system should be designed to include the installation of corporate runtimes.

Thus, the production system must make allowances for these types of applications. By including the runtimes into the system, the issue of installation is resolved. This must be complemented with special DDS folders within the system. These folders give copy and edit rights to both users and local developers.

In addition, local developers must be able to deploy their applications. Since they don't have access to traditional deployment tools and since they don't want to go from desk to desk to manually install their tools, they must use other means—means that fit within corporate standards.

Most organizations don't have complete inventories of their decentralized applications. Local developers often justify this by saying that their department is special and has needs that are not required by others. Developers prefer their own approaches. For this reason, many organizations have four or five timesheets, four or five corporate letter templates, and four or five expense sheets. This occurs because the corporation overlooks two processes: inventory and communication. If there is no inventory, it's difficult for the corporation to identify and manage its assets. It's also difficult for the corporation to communicate to decentralized developers all of the products that it owns.

Decentralized developers are a part of every network. They should be organized as a team that provides the same type of function at local levels. This team should be structured through standards and processes, just like every other part of the corporate network. These processes should include centralized systems for decentralized development support.

The centralized system should consist of an application depot that includes all of the elements required to make the application work properly. This should include a master directory for the application. This master directory is named after the application's asset number (four digits is usually sufficient). Subfolders should include the following (see Figure 2):

  • Clients. All client components that must be copied to a PC.

  • Documents. All product documentation or links to user documentation on the intranet.

  • Icons. The application's icon on the desktop.

  • Shortcut. The program's shortcut.

  • Source Data. If the application requires shared data, it should be located here.

  • UserGroups. This folder contains the list of authorized users.

Figure 2Figure 2 DDS depot structure.

Each application folder always contains the same subfolders. Shared databases are stored centrally. Updates are applied centrally and downloaded to desktops automatically by the shortcut.

Users should be allowed read and execute rights on this deposit. Developers should be allowed read, write, and execute rights to their own particular application directories. New application directories should be created centrally through the inventory and asset management process. This process should automatically publish information on the application to the central intranet application inventory page. (Developers can also use this page to search for existing applications.)

An additional tool—a code-signed VBScript (VBS) that replaces the normal application shortcut on the desktop—supplements the central application deposit. This script performs the following steps:

  1. Shortcut launch. Instead of launching the application, the VBS shortcut begins the authorization and update/installation process.

  2. Authorize users. Is the user authorized?

    1. The VBS shortcut reads the file GROUPS.TXT within the UserGroups subfolder to determine whether the user is authorized. If yes, it moves to the next step.

    2. If no, it stops operation and displays an "unauthorized user" message.

  3. Install/update verification. Is the application on the user's PC?

    1. If yes, is there a new version of the application? If no, behave as a normal shortcut and launch the application.

    2. If no, the shortcut copies itself to the PC and then proceeds with the next step.

  4. Install/update/launch. Does the application include local or updated local components?

    1. If yes, copy the contents of the Clients subfolder to the local PC, and then launch the application.

    2. If no, launch the remote application.

Since core DDS components are already in the system, the DDS installation process is a simple file copy. This process is illustrated in Figure 3.

Figure 3Figure 3 A DDS application "installation" process.

This simple program serves several purposes:

  • It validates user authorizations.

  • It automatically installs or updates local components (if local components are required).

  • It automatically performs an application validity check at startup.

Decentralized developers can use the VBS shortcut to manage all of their updates and installations. By properly placing all of their applications within the structure of the DDS depot, they can facilitate their application management process. They can use the VBS shortcut to automatically install applications on user systems. This can be done through a simple email message to the user. Before doing so, the developer must ensure that the user's name is included in the GROUPS.TXT file on the server. When users receive the email message, all they have to do is launch the shortcut and the VBS program will automatically install, and then manage the application through its lifecycle.

One single VBS shortcut program can manage all of the decentralized applications within a corporate network. The only object that developers need to modify is the VBS shortcut itself, through its properties. This must be done to ensure that it points to the appropriate application directory on the server. Figure 4 illustrates this modification.

Figure 4Figure 4 Modifying the VBS shortcut properties.

Several other technologies can be integrated to this process as technology changes within the network. For example, the VBS shortcut could verify actual user groups within the security database (such as Active Directory) instead of user lists in text files. But this change would require central administrators to give DDS developers rights to manage their own distribution groups within the security database. This is not a very likely scenario today, because delegated management of distribution groups is a new concept brought about by directory-enabled networks (DEN) such as Windows 2000.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020