------------------------------------------------------------------------------- IntraBuilder Prebuilt Business Solutions Version 1.01 README2.TXT Updated 8:00 PM 12/18/96 This file is a continuation of README.TXT. For general information and setup instructions, refer to README.TXT. This file describes the following prebuilt business solution applications: - Security Administrator - Contact Manager - Phone Book ------------------------------------------------------------------------------- USING THE SECURITY ADMINISTRATION BUSINESS SOLUTION ------------------------------------------------------------------------------- The Security Administration prebuilt business solution is used to manage the various aspects of an application security system. You can define users, groups, resources and policies. The security system is used by each of the other solution applications. You will find a link to the Security Administration solution on the INDEX.HTM page. The Security Administration page is password protected. Only members of the Administrators group can access this page. For demonstration purposes you can use the user name "SYSDBA" and the password "masterkey" to access the form. Before deploying your own system with security, be sure to create a new user in the Administrators group and then delete the SYSDBA user (or at least change the password). The security system main page allows you to view a list of users, groups, resources or policies. You can add new items, add a copy of an existing item, update an existing item or delete an existing item. The Policy Administration form lets you update system policies as well as create your own policies. A policy is configuration information that is used throughout the security system, and is not specific to any one user. The system policies have to do with passwords and lock outs. The password policies are called CASE, MINPASS and MAXPASS. The CASE policy determines whether the security system treats passwords as case sensitive or not. Names are never case sensitive. By default the passwords are not case sensitive either. MINPASS and MAXPASS define the minimum and maximum length of a password. This is enforced when creating a new user or when users change their password. The lock out policies are AUTORESET, LOCOUNT and LOMINUTES. A lock out occurs after several failed login attempts in a certain amount of time. This security feature is designed to deter attempts to break into a secure system. The LOCOUNT policy determines the number failed logins that will trigger a lock out. This is set to zero by default, disabling lock out security. The LOMINUTES policy determines the amount of time that must pass before the lock out count for this user is reset. The AUTORESET policy affects what happens after a lock out has occurred. If this is set on, then the locked out account will be cleared after the LOMINUTES period has passed. If this is set off, then only the system administrator can clear the account (this is done using the User Administration form described below). Note that policies may either be set to a boolean value or a numeric value. (System policy types can not be changed.) Because of this there are two places to set the value. Use only the On/Yes/True checkbox when setting boolean policies, and the Numeric Value text control when setting numeric policies. The User Administration form lets you create a new user or update an existing user. You can enter basic information such as name and description. In addition you can make group and resource assignments. You can temporarily disable a user account by checking the Account Disabled option. If a user has been locked out, you can clear the account by unchecking the Account Locked Out option. The Group Administration form lets you create a new group or update an existing group. You can enter the description of a group. In addition, you can designate group members and designate the resources that this group has access to. The Resource Administration form lets you create a new resource or update an existing resource. You can enter the description of a resource as well as designate which groups and users can access this resource. The information defined in the Security Administration pages can be accessed by your own applications through the Security Manager API. This API is defined in the SECURITY.JS file in the Apps\Shared directory. Take a look at this file for more information about using the API. Take a look at the other prebuilt business solutions to see examples of using the API to provide security. ------------------------------------------------------------------------------- USING THE CONTACT MANAGER BUSINESS SOLUTION ------------------------------------------------------------------------------- The Contact Manager prebuilt business solution allows you to keep track of the people you interact with. You can keep personal information for each contact person. In addition you can track specific types of contacts, called events, for each person. The Contact Manager solution uses Access tables. To run this solution, you will need an ODBC Access driver. Once you have installed the ODBC Access driver, create an ODBC data source for the Contact Manager database. 1. Run the 32Bit ODBC Administrator. 2. Select the Add button in the Data Source dialog. 3. Select the Access Driver in the Add Data Source dialog. 4. Enter any Data Source Name, such as ODBC_Contacts. 5. Enter a description, if you wish. 6. Press the Select... button. 7. Use the Select Database dialog to select the Contacts.mdb file in the c:\Program Files\Borland\IntraBuilder\Apps\Contacts directory. 8. Press OK in the Select Database dialog. 9. Press Close in the Data Sources dialog. After creating the ODBC data source, you can create the necessary BDE alias. 1. Run the BDE Configuration program in the IntraBuilder program group. 2. Press the New ODBC Driver button. 3. Give the driver a name, such as ODBC_Contacts. 4. The Default ODBC Driver should be Microsoft Access Driver. 5. Select the Default Data Source Name that you created in step 4 of the ODBC setup above. 6. Press OK. 7. Select the Aliases tab and press the New Alias button. 8. Enter CONTACTS as the alias name. This name is required. 9. The Alias Type should be the ODBC Driver that you created in steps 2 through 6. 10. Press OK. 11. Select Exit from the File menu to close BDE Configuration. Once you have configured the ODBC data source and the BDE alias, you can run the Contact Manager prebuilt business solution. To run the application, select the Contact Manager link in the INDEX.HTM page. This first page allows you to manage events or contacts. The Events page allows you to view and update information about each contact event. An event can be any type of interaction between you and the people that you contact. Each event contains the name of the person making the contact, the person contacted, the start and end time of the event, the type of event and comments about the event. Using the tool bar at the bottom, you can navigate, add or delete records. There are also buttons at the bottom to generate reports based on the type of contact and the person making the contact. There is also a search button at the button of the page. The People page allows you to view and update the name, address, and phone number of each person that you contact. The toolbar at the bottom of the page allows you to navigate, add or delete records. The type of events displayed in the Events page are contained in a table named Types. To update this list, you can run the IntraBuilder Designer. Then select the Tables tab in the IntraBuilder Explorer. Then select the Contacts database from the Look In combobox. This will display the tables in the Contacts database. Double clicking the Types table will open it for editing. While editing you can use the Table menu to add or delete rows or to search for a particular record. ------------------------------------------------------------------------------- USING THE PHONE BOOK BUSINESS SOLUTION ------------------------------------------------------------------------------- The Phone Book application can be used within a company or department to quickly retrieve information about coworkers, such as their phone number or location. You begin the phone book application by viewing one of the two phone book lists. The phone book can be viewed alphabetically or by department. The alphabetical list is PHONEEMP.JRP and the department list is PHONEDEP.JRP. These lists may contain all the data that you need. But to get more information and a picture of any employee, simply click on the employee's name. The name acts as a link to a document specific to that employee that includes a picture as well as their department and position. In addition to the list and detail views, there is also a Phone Book Administration page for updating the employee data. If you are viewing the detail page for an employee you can use the update link to update that employee. When viewing the reports, the update link takes you to the first employee (by default). The administration form allows you to update employee records as well as do searches, additions and deletions. The administration form is password protected so that only managers may update employee records. Each employee may also update their own record. If an employee (not a manager) loads the administration page, they will only see their own record (even if they tried to update a different employee's record). For demonstration purposes, you may use the first name of any employee shown in the phone list as a user name. The passwords match the user name. When viewing the department list, titles are shown. Use this information to find the user name of any manager. Whenever a user is viewing their own employee record, there is an additional button to update the security profile. This updates information in the security system, not the phone book. Users can use this to update their description or password. When you are logged into the administration form as a manager, you also have the ability to update the department lookup table. The department update form displays a list of departments. You can add or delete department names from the list. See the Security Administration prebuilt business solution for more information about setting up this type of security. ------------------------------------------------------------------------------- Copyright (c) 1996 Borland International, Inc. All rights reserved.