Escolar Documentos
Profissional Documentos
Cultura Documentos
Administrator
Manual
Chapter 1. Introduction
Chapter 2. The BOS/e Desktop toolbar
Chapter 3. Using the BOS/e Desktop
Chapter 4. Configuring the BOS/e Desktop
Chapter 1. Introduction
Chapter 2. Using the BOS/e Component Manager
Activity 1. Adding Components to Global Database
Activity 2. Modifying Component Parameters
Activity 3. Creating Companies, assigning Sub-companies, Transactions, and
adding Company Components
Activity 4. Defining Company-wide Default Desktop Tree View
Chapter 1. Introduction
Chapter 2. Adding, Deleting, and Updating Registry Information
Activity 1. Adding Registry Information
Activity 2. Editing Registry Information
Activity 3. Deleting Registry Information
Chapter 3. Updating Local Lookup Data
Chapter 1. Introduction
Chapter 2. Adding User Details
Chapter 3. Managing Accessible Tables and Field Restrictions to Global Users
Activity 1. Specifying Accessible Tables
Activity 2. Specifying Restricted Columns in a Table
Chapter 4. Creating User Roles and Assigning BOS/e Components
Activity 1. Creating a New Role
Activity 2. Adding BOS/e Components to the Role
Chapter 5. Assigning Global User/Role to Company Database Group
Activity 1. Adding Company User
Activity 2. Adding Role : Company level
Activity 3. Associating Role to Company User
Chapter 6. Adding Sub-Company Access to BOS/e User(s)
Chapter 7. Adding Restricted Records to BOS/e User(s)
Chapter 8. Adding Restricted Functions to BOS/e User(s)
Chapter 1. Introduction
Chapter 2. Adding, Deleting, and Updating Lookup Records
Activity 1. Adding Lookup Information
Activity 2. Editing Lookup Information
Activity 3. Deleting Lookup Information
Chapter 3. Updating Local Lookup Data
Chapter 1. Introduction
Chapter 2. Viewing User, BOS/e Component, and Table Activities
Activity 1. Viewing User Activities
Activity 2. Viewing BOS/e Component Activities
Activity 3. Viewing Table Activities
Chapter 3. Optimizing BOS/e Audit Trail Manager
Chapter 4. Generating BOS/e Audit Trail Manager Reports
Chapter 6. Conclusion
V. Set Up Users
Components Involved
1. BOS/e Applicant InfoManager
Create a record for the new user in Global People to assign him a Global Unique
ID (GUID)
2. BOS/e User Admin
Create a record for the new user in to assign him a Global Unique ID (GUID)
Modify user properties (password, private path, login names, restrictions, etc.)
3. BOS/e User Role Manager
Add user role, accessible tables, components
Associate roles to company users, subcompany access, restrictions (GUID,
Functions,etc)
MODULE 1:
Installing the BOS/e
PeopleWARE 2003
CONTENTS
Prerequisites
Hardware Requirements
Software Components
Installing BOS/e PeopleWARE 2003
Whats Next
Appendix A BOS/e Database Configuration Parameters
Appendix B BOS/e PeopleWARE 2003 Installation Types
Appendix C Advantages and Disadvantages of SQL Server
on a Separate Machine
BOS/e Installation CD
BOS/e Technology Overview Manual
BOS/e PeopleWARE 2003 Installation Manual (This manual)
Before you begin, make sure that all items mentioned above are present in the BOS/e
PeopleWARE 2003 CD pack.
2.0 Pre-requisites
The following minimum configuration is required for BOS/e PeopleWARE 2003 to run
smoothly:
If your hardware and software components satisfy minimum requirements, you may proceed
to Section 3.0 for actual installation.
Before proceeding with the Server Installation, ensure that the target database
server had already been installed and the following server objects had been created:
Required databases. There are four (4) required databases for initial
BOS/e Server installation: Global, Company, Subcompany, and Transaction
Databases. Ask your Database Administrator (DBA) for the names of these
databases (see also BOS/e iTechnology Overview Handbook for more
information of BOS/e Datawarehouse Components).
Database User with initial password. Make sure that the database user
has sufficient privileges to create, delete, insert, update, and drop objects
within the database.
2. If auto play is disabled, locate the setup.exe program from the CD-ROM using
Windows Explorer. Double-click the setup.exe. The setup program will now
launch, see Figure 1.
6. Click the Next > button to proceed with the Server Installation.
2. If you choose Native for the driver interface, parameters such as Driver Name,
Global Database Name, Server Name, User Name, and Password are required.
3. For ODBC driver interface type, you must first create the datasource from the
ODBC Datasources applet in the Control Panel.
4. Enter the appropriate parameters for ODBC Datasource and ODBC Driver
Name.
NOTE: For Paradox driver interface, you must supply the correct path of the
Paradox tables. Please see appendix A for explanation on configuration
parameters used in database configuration wizard.
Post-Server Installation
BOS/e iTechnology Server contains COM components that need to be manually
configured after installation. Follow the sequential steps below to configure COM.
1. Click Start > Run. Type DCOMCNFG.EXE, and then hit Enter key. Search for
the BOSeUniversalApplication object from the Applications tab.
3. From the Default Security tab, click Edit Defaultfrom the Default Access
Permission group. A screen similar to the one below will pop up.
4. Choose the user from the Name group box. Make sure to select Allow Access
from the Type of Access drop-down list box.
5. Click Add button to allow the selected user access to the application server.
BOS/e Application Server is now ready to accept client requests from any BOS/e
workstations wired within the network.
OVERVIEW
The BOS/e Datawarehouse is composed of four database levels, the Global, Company,
Sub Company and Transaction databases. Each database level contains different data
that BOS/e utilizes when it is run. In order to run BOS/e we will need: One (1) Global
Database (named preferably as GBOSE) and at least one Company (named preferably
as CBOSE), Sub Company (named preferably as SBOSE) and Transaction Databases
(named preferably as TBOSE). The number of Company databases that you need to
create depends on the number of companies licensed upon purchase of BOS/e, since
one company corresponds to one company database.
The BOS/e CD Installer contains the SQL Scripts (found in the folder SQL Scripts) and
the default values needed to run BOS/e as an administrator with access to all licensed
components (found in the folder BOSe Defaults).
NOTE: The following steps illustrate generic instructions on how to create and
populate the different databases for BOS/e. Since BOS/e is designed to run in
different Relational Database Management Systems (RDBMS), it is assumed
that the System/Database Administrator has proper knowledge on how to
manipulate the Database Management Tool(s) being used by your company.
Steps
1. Using your database management tool, create four databases, namely GBOSE,
CBOSE, SBOSE, and TBOSE.
2. Run the respective SQL Scripts for the created databases (for example: run
CBOSE.sql in the CBOSE database, TBOSE.sql in the TBOSE database, and so
on). The CD Installer contains the scripts for the RDBMS that your company has
(for example: MSSQL scripts if your company uses MSSQL).
NOTE: We now have four databases with empty tables. We cannot run BOS/e
yet because we need default values in order for BOS/e to run properly (for
example: a default user with administrator access, data for the different
components that are licensed to the company, and so on). The BOS/e CD
Installer contains the default values needed to run BOS/e. These default values
are stored in Paradox tables. In the CD Installer inside the BOSe Defaults folder
are four folders for the different database levels, namely CBOSE, GBOSE,
SBOSE, and TBOSE.
2. If auto play feature is turned off, locate the setup.exe file from the BOS/e
iTechnology Universal CD.Double-click to launch the installer.
6. Click Browse to select a different program location. Click Next > to select
Install type. Install types are fully describe in Appendix B.
7. Follow the next steps to finish the installation process. This completes the
BOS/e Installation process.
5.0 Appendices
The list shows the advantages/disadvantages of providing an individual machine for our
database server and on providing a separate volume for the MS SQL data.
1) Provide a separate machine to house the database server and its data:
* Advantages:
- Dedicated CPU processing. The MS SQL service can freely accommodate most of the
system's time splice without the need to share CPU processes with other highly consuming
applications. The MS SQL service can effectively run and cater data-oriented queries rightly
faster and better.
- Dedicated Memory usage. The MS SQL service can freely accommodate the system's
memory capacity making it more efficient in processing memory-consuming queries and
data transactions.
- Prevents multiple services failure. If the UAP machine suddenly fails or has suffered a
hardware or software malfunction, the MS SQL service cannot be affected and can still
provide the necessary needs for the iBOS/e web transactions.
- Less maintenance issues. Taking good care of systems that carry multiple services can be
very hard to maintain since a service failure can affect other running services thus resulting
in a more time-consuming troubleshooting and repair.
- A lower TCO (Total cost of ownership) plan in terms of system upgrade/update. To have the
MS SQL server separated on a single machine may provide costs benefits for future
* Disadvantage:
- There is an additional investment involved. Separating the database service and data will
require a new separate machine. (Note: The emerging trend nowadays is to further separate
database service from database files in two machines for disaster recovery purposes).
2) Provide a separate volume of hard drives to house the MS SQL service's data with UAP:
* Disadvantage:
- If the database server will not be provided with a separate machine but instead, its data will
be separated only to another hard drive volume (and will still share with the same machine of
UAP), only the 'access' to data will be freed up of space (not the MS SQL service). It will not
relieve the system of the problem of future expansion.
MODULE 2:
Managing the
BOS/e Desktop
CONTENTS
Overview
The BOS/e Desktop Login Screen
The BOS/e Desktop Toolbar
Using the BOS/e Desktop
Configuring the BOS/e Desktop
Chapter
BOS/e DESKTOP
Introduction
OVERVIEW
1
BOS/e Desktop provides BOS/e users with a standard user desktop interface for launching
BOS/e components and third-party custom components. BOS/e Desktop also manages user
configuration and desktop preferences for easy retrieval of accessible BOS/e components.
Every time a user launches BOS/e Desktop application, the login screen asks the user to
provide a valid user name and password. This user name/password combination authenticates
the user and immediately gets a Security Token1 from the BOS/e Application Server2 for
appropriate component authorization.
Once authenticated, the BOS/e Desktop loads the users preferred workspace and displays the
users accessible BOS/e components for a given accessible company (see Figure 2). Users
desktop preferences can be configured separately for each company in multi-company setup.
Chapter
BOS/e DESKTOP
The BOS/e Desktop Toolbar
Presented below are the common functions found in the standard BOS/e Desktop toolbar.
2
Table 1. BOS/e Desktop Toolbar Buttons
NOTE: Some toolbar buttons are grayed out when selecting a folder or
clicking another button from the toolbar. This prevents a user from
performing inappropriate task or function on a given folder (for example,
is grayed out to prevent the user from running any BOS/e
component when there is no component selected from the BOS/e
component tree view).
Chapter
BOS/e DESKTOP
Using the BOS/e Desktop
Steps
3
1. BOS/e is designed for multi-company setup. Different companies can have different
desktops depending on the configuration. Selecting a company from the company list
window loads the users preferred desktop configuration. Thus, BOS/e component
listings may differ from one company to another. Refer to Figure 3.
a. Right-click the selected BOS/e component, and click Run Component from the
popup menu.
b. Double-click the BOS/e component from the right pane of the BOS/e Desktop
Chapter
BOS/e DESKTOP
Configuring the BOS/e Desktop
4
Steps
1. To configure BOS/e Desktop, click the Configure Component Folders from the
BOS/e Desktop toolbar. A new window will appear showing the current desktop
configuration tree.
2. To add/modify BOS/e Desktop configuration, right-click the selected folder to see more
options. Refer to Figure 6.
Delete Removes a node, branch, or BOS/e component from the tree view.
Load Default Tree This function loads the default BOS/e Desktop tree defined from the
BOS/e Component Manager.
NOTE: You may notice that some of the components you configured in the
BOS/e Desktop are missing. This may be due to the lack of access to that
particular component or the component itself may not be properly configured.
Please refer to the BOS/e User Role Manager Administrators Manual for
discussion on assigning access rights.
1
Security Token An application object that holds BOS/e-wide security credentials or information about the current
authenticated user.
2
BOS/e Application Server A BOS/e Server component that manages all activities happening inside BOS/e. Please
refer to BOS/e Technology Overview for more detailed explanation of BOS/e Application Server.
3
BOS/e Desktop Workspace an area in the BOS/e Desktop divided into several windows (i.e. Company Listing,
Component Listing, and Component Details).
MODULE 3:
Using
BOS/e Component
Manager
CONTENTS
Overview
Running the BOS/e Component Manager
Adding Components to Global Database
Modifying Component Parameters
Registering Company Components
Creating Companies, Assigning Sub-companies, Transactions,
and Adding Company Components
Defining Company-wide Default Desktop Tree View
Chapter
BOS/e COMPONENT MANAGER
Introduction
1
OVERVIEW
BOS/e comes with pre-configured business programs known as business components. All of
these components (as well as 3rd party business components) must be registered inside the
BOS/e registry before you can use them. Component registration in BOS/e is accomplished
using the BOS/e Component Manager found in the BOS/e Business Engine group. Aside from
component registration, the BOS/e Component Manager also handles the addition of new
companies (if supported by company license for BOS/e); and the definition and assignment of
Sub-company groupings in a given company and its corresponding transaction grouping. Lastly,
the BOS/e Component Manager also handles the default desktop tree configuration for
assignment to one or more companies.
In BOS/e, data can only be used after being registered in the global database or registry. This
convention is consistent to all components in the BOS/e PeopleWARE 2003 Business Engine
component group.
This section will discuss the steps in registering components in the global database.
1. In the BOS/e Desktop (see Figure 1), click the [+] sign beside the folder of Business
Operating System for the Enterprise, click the [+] sign beside the folder of BOS/e
Business Engine, then right-click the BOS/e Component Manager. A run component
tab will appear, click the said tab. You may also opt to double-click the BOS/e
Component Manager displayed in the right frame of the screen.
2. The BOS/e Component Manager window will now appear, refer to Figure 2.
Chapter
BOS/e COMPONENT MANAGER
Using the BOS/e Component Manager
Activity
BOS/e COMPONENT MANAGER
Adding Components to Global
Database 1
In BOS/e Architecture, all data should be first registered in the Global level before it can be used
by other levels (for example: in company). When BOS/e is installed, the licensed components
by the company are already installed. This activity should be done when:
Steps
1. From the Component List panel, right-click the Global components tree. Choose Add
Component from the pop-up menu (see Figure 3).
A new data entry window, similar to Figure 4 will appear. See Table 1 for explanation on the
information given on the data entry form.
Term Definition
Unique code of the business component that you want to register.
For example: BOSEGOALMGT. If the component to be
Component Code
registered is part of the BOS/e iTechnology product, Infostructure
will provide this code, otherwise, you can assign any unique code
to the component.
Component Name Descriptive name of the business component that you want to
register.
Description Short description of the component.
Specifies the name of the executable file of the given business
Executable name component.
Class name (Optional) Used internally by BOS/e Universal Application Server.
Component grouping. This is usually required for processing and
Component group code simulating business components such as Payroll and
Timekeeping.
Information that will be loaded during component startup. These
parameters could be table filter conditions, security token,
Additional parameters component status, etc. Normally used by business component
developer for controlling component behavior.
When tagged, the business component can be launched (opened)
Multi-instance simultaneously from the BOS/e Desktop.
Specify the image or icon to represent business component. This
Icon will be the icon of the component when displayed in BOS/e
Desktop.
2. After completing the required text boxes, click to add the new component
(Figure 5).
Figure 5. Inserting BOS/e Goal & Activity Logger in the global database
The component will now be a part of the BOS/e Global component list (Figure 6).
Activity
BOS/e COMPONENT MANAGER
Modifying Component Parameters
Steps
2
IMPORTANT: Once registered, components can be modified when
necessary. Note that modifying component registry parameters is not
advisable unless, otherwise, required by the component developer.
1. From the Component List panel, right-click the Global components tree. Choose Edit from
the pop-up menu (see Figure 7). The component parameters will now be loaded on the
data entry form similar to Figure 4.
The number of companies that a user can add to their BOS/e installation depends on the
number of companies that are licensed to their company. The initial BOS/e installation should
have at least one company included.
Steps
1. Click the company icon. Right-click and select Insert from the pop-up menu (Figure 8).
2. Provide the information requested, such as Company Code, Company Name, and Data
Location Code. Note that the Data Location Code entry must be created first in the
BOS/e Registry Manager component. Refer to BOS/e Registry Manager Manual on how
to setup Data Location.
3. In addition, you can upload an image that will represent the component once displayed
on BOS/e Desktop. Click Load Icon to upload an image/logo that will represent the
given component. The dialog box shown below will then appear.
Assigning a Sub-company
Sub-company and transaction databases maintain data integrity and confidentiality in BOS/e
by providing physical separation of records across different payroll groups, compensation
class, or employee levels.
Steps
1. Click the company. Right-click and press the Add Sub-company from the pop-up menu
(Figure 11).
2. Provide the Sub-company Code, Sub-Company Name, and Data Location Code.
Again, data from Data Location Code box should come from the code defined in the
BOS/e Registry Manager component. Please refer to the BOS/e Registry Manual for
more information on setting up data location code.
3. Once you have entered the required information in Figure 12, click OK .
Assigning a Transaction
Steps
1. To set up Transaction database grouping, right-click the Subcompany created, then
select Add Transaction from the pop-up menu. A new window will emerge (Figure 13).
2. On the window that will appear, provide the Transactional Code, Description, and
Data Location Code boxes. Notice the Active DB check box. When checked, the
transactional grouping is active and can be used by BOS/e components. Please refer to
the BOS/e Registry Manual for more information on setting up data location code.
3. Click OK .
Components listed at the company level originate at the global components registry. It is
therefore necessary to register those available components at the company level.
Component registration at this level is a required task to enable the users to see the
licensed components on their BOS/e Desktop.
Steps
1. To register BOS/e components at the company level, click the Company tree, right-click
Components then select Add Component on pop-up menu. A new window will appear
(Figure 14).
2. Choose the BOS/e component licensed to your organization. To select multiple BOS/e
components, click the components that you want to add while holding down the Shift or
Ctrl key.
3. Click OK
Activity
BOS/e COMPONENT MANAGER
Defining Company-wide Default
Desktop Tree View 4
BOS/e comes with a preconfigured BOS/e Desktop Tree View. This tree view displays
BOS/e components in a hierarchical view, hence, the reason why it is called Desktop Tree
view. BOS/e administrators can modify this tree view to suit the organizations standardized
component groupings.
Steps
1. From the toolbar menu, click Configure Desktop Tree to activate the Default
Desktop Tree configurator screen (Figure 15). Note: Right-click to display options.
the same folder level while a branch is a child of the node. Refer to table 2 for
explanations on the sub-menu items in each menu.
Delete Removes a node, branch, or BOS/e component from the tree view.
MODULE 4:
Using BOS/e Registry
Manager
CONTENTS
Overview
Running the BOS/e Registry Manager
Adding, Deleting, and Updating Registry Information
Updating Local Lookup Data
Chapter
BOS/e REGISTRY MANAGER
Introduction
OVERVIEW
1
BOS/e is designed to be user-friendly, highly configurable, and customizable software that
supports any relational database server. These features are accomplished in BOS/e through
the use of registries. Registries include system registry, and system lookup tables that contain
information about database location and connection parameters, table repository, file
references, BOS/e components, licensing information, among others. Only tables defined as
Global or System Tables in the BOS/e Data Architect component and tables that are registered
in the BOS/e InfoManager Customizer component are displayed here.
2. The BOS/e Registry Manager window will now appear, refer to Figure 2.
Chapter
BOS/e REGISTRY MANAGER
Adding, Deleting, and Updating
Registry Information 2
OVERVIEW
In BOS/e Registry Manager, registries can either be global in scope or specifically used at the
company level.
Activity
BOS/e REGISTRY MANAGER
Adding Registry Information
Steps
1
The steps outlined below are the same for all registry tables in the BOS/e Registry Manager.
Also, steps in adding records at the global and company level are the same.
1. Click Global under the Entities list then select a registry or table. Click Edit to set
the form in edit mode. You are only allowed to add registry information while the table is
in edit mode.
2. Click Add to insert new registry record. A data entry form will then appear (see
figure 3). Input the required information on the text boxes.
See Table 2 for more information on the toolbar icons used in BOS/e Registry Manager.
Edit Set the data entry form to edit mode. You are only allowed to modify
records once the form is in edit mode.
Cancels all changes made to the registry table. Note that you can
Cancel only cancel changes if changes had not yet been saved using the
save button.
Infocards Displays Infocard for the given registry table. This only applies to
registry tables configured to have detail files in the BOS/e Data
Architect.
Find Next Find next occurrence of registry record specified from the initial global
find dialog box.
Activity
BOS/e REGISTRY MANAGER
Editing Registry Information
Steps
2
Registry entries can be edited directly from the grid or from the edit form. The following steps
describe editing registry records on any registry table in the BOS/e Registry Manager
component.
1. Click Edit to set the grid in edit mode. Alternately, you may double-click the grid to
display the edit form screen shown in Figure 3.
2. Enter the appropriate changes and click Edit once again to end editing.
3. Click Save .
Activity
BOS/e REGISTRY MANAGER
Deleting Registry Information
Steps
3
Deleting registry entries is not recommended in BOS/e Registry Manager Component.
Removing records accidentally might render the entire BOS/e system unusable. Unused
registry entries can be deleted though to free up some server space occupied by the
unnecessary records.
1. Click Edit to set the grid in edit mode. You can only delete records once edit mode is
in effect. Alternately, you may also delete registry records if you are in the edit form
screen shown in Figure 3.
3. Click Save .
Chapter
BOS/e REGISTRY MANAGER
Updating Local Lookup Data
OVERVIEW
3
In BOS/e, some of the registries and lookup tables are cached locally to enable the components
to quickly access references without connecting to the database server. This method
dramatically improves BOS/e application performance especially during heavy, simultaneous
usage.
BOS/e updates this local cache during sign on. But users can override this behavior and can
download lookup data immediately; ensuring only current data are stored in its cache.
Steps
1. From the Tools menu, click Refresh Lookup. Alternately, you can click Refresh
Lookup from the toolbar to immediately update local lookup data (See Figure 4).
MODULE 5:
Using BOS/e User
Admin and User
Role Manager
CONTENTS
Overview
Running the BOS/e User Admin and User Role
Manager
Adding User Details
Managing Accessible Tables and Field Restrictions to
Global Users
Defining Roles in the Global Database Group
Assigning Global User/Role to Company Database
Group
Adding Sub-Company Access to BOS/e User
Adding Restricted Records to BOS/e User
Adding Restricted Functions to BOS/e User
Chapter
BOS/e USER ADMIN AND USER ROLE MANAGER
Introduction
OVERVIEW
1
BOS/e PeopleWARE 2003 is a secure, robust, and an industrial-class product. Security and
confidentiality of data is at the forefront of every BOS/e PeopleWARE 2003 component.
Componentization shields the user from the complexity of the entire system, thus providing
them with only the components they directly need to accomplish a particular task or fulfill a
specific role within the organization. This user-role design philosophy paved the way for
BOS/e PeopleWARE 2003s adaptation of the same design methodology in creating BOS/e
User Role Manager Component.
BOS/e User Role Manager handles the creation of Roles that can be assigned to a certain
BOS/e user in an enterprise. It also manages the security context in the form of accessible
tables and columns, user desktop and password management, subcompany rights
management, and component security context such as accessible users and functions.
BOS/e User Admin and User Role Manager handles the following security contexts:
Steps
1. In the BOS/e Desktop (see Figure 1), click the [+] sign beside the folder of Business
Operating System for the Enterprise, click the [+] sign beside the folder of BOS/e
Business Engine Components then right-click the BOS/e User Role Manager/ BOS/e
User Admin. A run component tab will appear, click the said tab. You may also opt to
double-click the BOS/e User Role Manager/ BOS/e User Admin displayed in the right
frame of the screen.
2. The BOS/e User Role Manager/BOS/e User Admin window will appear, refer to Figure 2.
Chapter
BOS/e USER ADMIN
Adding User Details
1
In the BOS/e Desktop, open BOS/e User Admin Manager and do the following:
Setup BOS/e Users Login Restrictions like Account Disable, Grace Login Limit, Number
of Grace Login Allowed, Grace Login Left Display, Lock for Intruder User, User Private
Path, and User Default Components Tree.
Private Path is the folder where all temporary files and some payroll reports are saved while
using BOS/e. Before assigning a Private Path, make sure that folder exists in your computer.
The Default path is C:\BOSe\Priv
For the Load User DefaultTree, always use the file DESKTOP.TRE, located in the BIN BOS/e.
Note: You can assign specific hour/s or day/s that a BOS/e user is allowed to login to BOS/e.
This can be done by checking the exact hours inside a day. Uncheck all hours inside a day to
prohibit the user from logging in the entire day.
Assigned username for the newly added user. Note that the default login
Login name name is the users first name. If it is already being used by another user, the
users GUID will be considered as default. You may, however, modify this
text. Login names for BOS/e should always be unique.
Private path Specify local temporary path. The Private Path is mainly used by the BOS/e
Executive Query component.
User Password Password used to log in to BOS/e. The default password when a User is
created is the users first name.
Password To ensure password security, this option requires the user to change
expires on password on a specified date.
Remind me # BOS/e will remind the user to change his password when password
days before expiration nears the specified expiration date.
expiration
Locked out BOS/e Universal Application Server automatically locks the users account
when three (3) failed login attempts have been detected.
Must change If tagged, BOS/e will prompt the user to change his password on his next
password on login.
next login
Chapter
BOS/e USER ROLE MANAGER
Managing Accessible Tables and
Field Restrictions to Global Users 3
OVERVIEW
Security in BOS/e is carried out at the lowest level of the database object, that is, table and
columns. This feature protects confidential data from modification by unauthorized users.
Furthermore, security can also be observed at the column level, wherein users are (not) allowed
to modify or view the content of a confidential column in a table (for example: salary column,
benefits, and the like in Salary and Salary history tables).
Activity
BOS/e USER ROLE MANAGER
Specifying Accessible Tables
Steps
1
1. Expand the Global Tree by clicking the plus [+] sign beside Global. Expand the Global
Users Tree by clicking the plus sign beside Users. Right-click the user that you want to
edit and select Add Accessible Tables. Refer to Figure 9.
2. From the Add Accessible Tables window, select the tables that the user will have
access to. Press Ctrl or Shift key to select multiple tables then press Include. You may
choose to include all the tables by clicking Include All. Please refer to Figure 10.
3. Click OK to add accessible tables to the user. The newly added accessible tables will be
reflected on the GRGUSERTABLE table.
Add Users Accessible Tables window will appear, refer to Figure 10.
NOTE: Only tables registered in BOS/e Data Architect can be added as accessible
tables. Refer to the BOS/e Data Architect manual for the discussion on how to
register tables in BOS/e.
Activity
BOS/e USER ROLE MANAGER
Specifying Restricted Columns
In a Table 2
Steps
1. Expand the Global Tree by clicking the plus [+] sign beside Global. Expand the Global
Users Tree by clicking the plus [+] sign beside Users. Click the plus [+] sign of the user
whom you want to add the restricted fields with, right-click and select Load Accessible
Tables.
2. Expand the Accessible Tables tree and select a table. Expand the table and right-click
on Restricted Fields, select Add Restricted Fields on Table.
3. From the Global Field Selector, check/uncheck the column you want to restrict/unrestrict
for a given user by ticking the box (es) that corresponds to the field description that you
need. See Figure 12.
Chapter
BOS/e USER ROLE MANAGER
Creating User Roles and Assigning
BOS/e Components 4
OVERVIEW
Traditionally, software security was designed in a group-wise environment, that is, users were
given specific access rights based on the security credentials given to a specific group. The
ubiquity of software packages used at the enterprise level prompted users to assume cross-
functional tasks but performing the same role as other software users in the enterprise. Role-
based design simplifies system administration by providing common security properties for a
given role or job function. Users at the Data Entry Group, which basically perform data updates,
merge with other users who represent several departments. By creating Role for the Data Entry
Group, they can only use BOS/e components that perform data entry tasks. Similarly, only
reports customized for this group will be displayed on their BOS/e Desktop.
Activity
BOS/e USER ROLE MANAGER
Creating a New Role
Steps
1
1. Expand the Global Role tree. Right-click the Role tree then select Insert from the popup
menu.
2. From the Role Global Info pop up window, enter the Role code and its corresponding
description in the Description text box. See Figure 13.
3. Click OK to register this role to the Role tree. Otherwise, choose Cancel.
Activity
BOS/e USER ROLE MANAGER
Adding BOS/e Components to the Role
Steps
2
1. Right-click the newly created Role, choose Add Component from the popup menu. See
Figure 14.
2. From the Global Component Selector form select the BOS/e components that you want
to be included to the selected Role. See Figure 15.
3. Click Include, to include the selected BOS/e component(s) to the Role. Alternately, you
may use Include All to immediately include all components. Exclude/Exclude All does
the opposite of Include/Include All. Note that the OK button will only be activated if a
selection had already been added to the Target Data list box.
Chapter
BOS/e USER ROLE MANAGER
Assigning Global User/Role to
Company Database Group
OVERVIEW
5
User at the Global level is useless if no accessible companies are defined. To complete the
user management task, users must be registered at the company where that user is defined.
Note that the BOS/e User Role Manager only gives access to the user for a particular company
or companies, but the said user does not have to be an employee of the companies that s/he
has access to.
Activity
BOS/e USER ROLE MANAGER
Adding Company User
Steps
1. Navigate through the Company entity tree until you find the Users tree item.
1
2. Right-click the Users tree item and choose Insert from the popup menu. Figure 16 will
be displayed.
3. Define your filter conditions to be able to select target personnel (See Chapter 3 for more
information on setting up Filter conditions). See Figure 17.
4. Extract the personnel that you need to have access on the selected company and press
OK. Note that only users listed in the Global Users are accessible through this form.
Activity
BOS/e USER ROLE MANAGER
Adding Role At The Company Level
Steps
2
1. Navigate through the Company entity tree until you find the Roles tree item.
2. Right-click the Roles tree item and choose Insert from the popup menu. Figure 18 will
be displayed.
3. Select role(s) from the Company Role Selection form. Note that only Global Roles are
accessible through this form. See Figure 19.
4. Click OK.
Activity
BOS/e USER ROLE MANAGER
Associating Role to Company User
Steps 3
1. Navigate through the Company entity tree until you find the Users tree item.
2. Right-click the selected user and choose Add User Role from the popup menu. See
Figure 20.
3. Select role(s) from the Company Role Selection form. Click OK to accept the selected
roles. See Figure 21.
Chapter
BOS/e USER ROLE MANAGER
Adding Sub-Company Access to
BOS/e User(s) 6
OVERVIEW
Steps
1. Navigate through the Company entity tree until you find the Users tree item.
2. Right-click the selected user then choose Add Sub-Company Access from the
popup menu. See Figure 22.
3. Select subcompany(s) from the Sub-Company Selection box by ticking the box
that corresponds to the Sub-Company name that you need. See Figure 23.
4. Click OK.
Chapter
BOS/e USER ROLE MANAGER
Adding Restricted Records to
BOS/e User(s) 7
OVERVIEW
Deep into the BOS/e security model is the capability to restrict records to certain BOS/e user.
Users are only allowed to view, modify, or delete records assigned by the BOS/e Administrator.
Steps
1. Navigate through the Company entity tree until you find the Users tree item. Select the
Restricted GUID(s) tree item under the Users entity.
2. Right-click and choose Add Restricted GUID from the popup menu. See Figure 24.
3. Define filter conditions to select personnel (See Chapter 3 for more info on setting up
Filter conditions). See Figure 25.
4. Click OK. This indicates that the selected user has no access to view, modify, or delete
the selected personnel.
Chapter
BOS/e USER ROLE MANAGER
Adding Restricted Functions to
BOS/e User(s)
8
OVERVIEW
Restricted functions are actions embedded in all BOS/e business components. These actions
are functions grouped together to perform a task. Actions can also represent controls
specifically designed for a given BOS/e component. By attaching actions to these elements and
tasks, BOS/e can control what actions can only be performed at the component level (for
example: visible tabs or pages in a form, allowable views, menus, and so on and so forth).
Steps
1. Navigate through the Company entity tree until you find the Users tree item. Select the
Restricted Functions(s) tree item under the Users entity tree.
2. Right-click and choose Add Restricted Function(s) from the popup menu. See Figure
26.
3. From the form, click beside the Component Code text box. See Figure 27.
4. Based on the selected component in step 3, the actions associated with this
component will be displayed on the Action Codes text box.
5. Check Visible if you want this action to be visible in the BOS/e component
specified in Component Code text box.
6. Click OK.
7. Press on main window after using the BOS/e User Role Manager.
MODULE 6:
Using
BOS/e Lookup
Manager
CONTENTS
Overview
Running the BOS/e Lookup Manager
Adding, Deleting, and Updating Lookup Records
Updating Local Lookup Data
Chapter
BOS/e LOOKUP MANAGER
Introduction
OVERVIEW
1
The BOS/e Lookup Manager maintains the references and lookup data used in BOS/e. Only
tables defined as Lookup Cards in the BOS/e Data Architect component and tables registered in
the BOS/e InfoManager Customizer are displayed in this component. Reference data are
crucial during data entry. This shields the user from entering erroneous data as a result of
incomplete references. In addition, there are required reference tables that must be populated
before a certain BOS/e component could function well. Lookup tables such as SSS,
Withholding Tax, and other payroll-related references are just some of the required reference
tables that must be maintained and populated first.
2. The BOS/e Lookup Manager window will now appear, refer to Figure 2.
Chapter
BOS/e LOOKUP MANAGER
Adding, Deleting, and Updating
Lookup Records 2
OVERVIEW
In BOS/e Lookup Manager, reference tables can either be global in scope or specifically used at
the company level. Lookup data are either referenced during processing, simulation, or data
entry.
Tax Tables A series of tables that maintain tax rates for weekly, semi-
monthly, and annual withholding tax computations
Activity
BOS/e LOOKUP MANAGER
Adding Lookup Information
1
The steps outlined below are the same for all lookup tables in the BOS/e Lookup Manager. The
steps in adding records at the global and company level are the same.
Steps
1. Click Edit to set the form in edit mode. You are only allowed to add lookup
information while the table is in edit mode.
2. Click Add to insert new lookup record. A data entry form will then appear (see
Figure 3). Input the required information on the text boxes.
Refer to Table 2 for more information on the toolbar icons used in BOS/e Lookup Manager.
Edit Set the data entry form to edit mode. You are only allowed to
modify records once the form is in edit mode.
Cancels all changes made to the lookup table. Note that you can
Cancel only cancel changes if changes have not been saved using the
save icon.
Find Next Find next occurrence of lookup record specified from the initial
global find dialog box.
Activity
BOS/e LOOKUP MANAGER
Editing Lookup Information
2
Lookup records can be edited directly from the grid or from the edit form. The following steps
describe editing lookup records on any lookup table in the BOS/e Lookup Manager component.
Steps
1. Click Edit to set the grid in edit mode. Alternately, you may double-click the grid to
display the edit form screen shown in Figure 3.
2. Enter the appropriate changes then click Edit once again to end editing.
Activity
BOS/e LOOKUP MANAGER
Deleting Lookup Information
3
Deleting lookup records is not recommended in BOS/e Lookup Manager Component.
Accidentally removing records might produce unpredictable results to components that use the
lookup data.
Steps
1. Click Edit to set the grid in edit mode. You can only delete records once edit mode is
in effect. Alternately, you may also delete lookup records if you are in the edit form
screen shown in Figure 3.
Chapter
BOS/e LOOKUP MANAGER
Updating Local Lookup Data
OVERVIEW
3
In BOS/e, some of the registries and lookup tables are cached locally to enable the components
to quickly access references without connecting to the database server. This method
dramatically improves BOS/e application performance especially during heavy, simultaneous
usage.
BOS/e updates this local cache during login. But users can override this behavior and can
download lookup data immediately; ensuring only current data are stored in its cache.
Steps
1. From the Tools menu, choose Refresh Lookup menu item. Alternately, you can click
Refresh Lookup from the toolbar to immediately update local lookup data (See
Figure 4).
3. Press on the main window after using the BOS/e Lookup Manager.
MODULE 7:
Using BOS/e Audit
Trail Manager
CONTENTS
Overview
Running the BOS/e Audit Trail Manager
Viewing User Activities
Viewing BOS/e Component Activities
Viewing Table Activities
Optimizing BOS/e Audit Trail Manager
Generating BOS/e Audit Trail Manager Reports
Conclusion
Chapter
BOS/e AUDIT TRAIL MANAGER
Introduction
OVERVIEW
1
Monitoring changes made to every record in BOS/e is a very daunting task for a BOS/e
Administrator. Tracking every inserts, updates, and deletion is not possible without the aid the
BOS/e Audit Trail Manager component. This BOS/e component tracks changes made to tables,
by the BOS/e users on different BOS/e components.
BOS/e Audit Trail Manager gives the BOS/e Administrator total control of audit trail object
parameters.
2. The BOS/e Audit Trail Manager window will now appear, refer to Figure 2.
Figure 2. BOS/e Audit Trail Manager window: Initially displays the list of BOS/e Users
Chapter
BOS/e AUDIT TRAIL MANAGER
Viewing User, BOS/e Component,
and Table Activities 2
This chapter talks about three (3) audit trail activities:
Activity
BOS/e AUDIT TRAIL MANAGER
Viewing User Activities
1
User activities can be traced in the User List page. Audit logs will then be organized per
component, and per database level: Global, Company, Sub-Company, and Transaction. Note
that the component listing for each user is limited to the BOS/e components that s/he has
access to.
Steps
1. From the User List, expand the BOS/e Users tree. Click the user whose activities on
the BOS/e will be audited.
2. Choose the BOS/e component that you want to audit.
3. Select the appropriate database level. A screen similar to Figure 3 should appear.
NOTE: From the Sub-Company and Transaction database level, you can
further view audit logs for the selected component provided this component
supports Sub-Company and Transaction database level tasks. Transaction
logs (refer to the figure shown below) are transactions/changes that a
particular user has made under a particular component. It contains the
Transaction ID, Audit Date, Audit Time, and the Component Code. The details
part on the other hand, gives you an idea of the update type that the user has
made, its corresponding table name, the column name, its new value, and the
old value.
Transaction Logs
Activity
BOS/e AUDIT TRAIL MANAGER
Viewing BOS/e Component Activities
2
View the BOS/e component activities option if you want to track changes made on a selected
BOS/e component. Audit logs will then be presented per user, per database level.
NOTE: Upon installation, all BOS/e tables registered in BOS/e Data Architect have
complete Audit Options checked. System Administrators adding new tables should
activate relevant Audit Options based on the companys requirement, they are also
responsible for limiting the audit levels for the available tables.
Steps
1. Click the Components tab; expand the selected BOS/e component tree. Click the user
whose activities on the BOS/e will be audited.
2. Select the appropriate database level, for example: Global, Company, Sub-company, or
Transaction. A screen similar to Figure 4 will appear.
Activity
BOS/e AUDIT TRAIL MANAGER
Viewing Table Activities
3
Registered tables in BOS/e Data Architect component are automatically included in this page.
Audit logs per table in each database level (Global, Company, Sub-Company, Transaction) can
be seen in this view option.
Steps
1. Select the Table Listing tab. Expand the selected database level.
2. Click the desired table that where you want the activities done to be traced. A screen
similar to Figure 5 should appear.
NOTE: Audit logs made by all components on the given table will also be
displayed in this view. The preview was specifically designed on a per
component audit log.
Chapter
BOS/e AUDIT TRAIL MANAGER
Optimizing BOS/e Audit Trail Manager
3
Auditing, if not planned carefully, will contribute to the performance degradation of the entire
BOS/e PeopleWARE 2003 software. Each registered BOS/e table can be configured to limit the
auditing actions. The three audit actions edit, insert, delete can be selectively turned on/off to
reduce server read/write overhead cost. As BOS/e Administrator, you have the option between
heavy auditing and selective auditing. Heavy auditing will enable you to gather more information
(not necessarily important data), this produces a more secure and more efficient work results
but it slows down system performance. Selective auditing on the other hand will enable you to
gather less information (however, if audit options are selected properly it will only produce
relevant data), but faster system performance. Also note that the Audit Options are sometimes
dictated by the management depending on their preferences.
Steps
1. From the main menu, select the Options menu item. Click Audit Options to activate the
audit trail options configuration screen (refer to Figure 6).
2. From the BOS/e Table List, expand the database level, and select the table you want to
optimize.
3. From the Audit Actions group, check the appropriate action you want to turn on/off.
Audit Insert tracks the addition of new data that are made by BOS/e
users for a particular table.
Audit Delete tracks the removal of data that are made by BOS/e users
for a BOS/e registered table.
4. Click OK to apply the audit options. The audit options will immediately take place on
BOS/e components affected by the changes.
Chapter
BOS/e AUDIT TRAIL MANAGER
Generating BOS/e Audit Trail
Manager Reports 4
BOS/e Audit Trail Manager provides comprehensive reports for reporting audit activities in
BOS/e PeopleWARE 2003. These reports help BOS/e Administrators evaluate audit trail
performance and can be used as an input for coming up with a better audit trail strategy and
user management.
Steps
1. From the main menu, choose Report menu item. Click Audit Trail Reports to activate
the report options dialog box. See Figure 7.
2. Choose the appropriate Report Type: Audit Trail Summary or Audit Trail Detail. For
Audit Trail Summary, report is presented per component. All tables used by the given
component will be presented with summary of inserts, deletes, and updates. For Audit
Trail Detail, all changes on each component are presented: new value, old value.
3. Choose the appropriate database level where you want to report be generated. For
subcompany and transaction levels, you will be prompted to choose the appropriate
subcompany and transaction codes.
4. Choose a Subcompany code by clicking the pick list button that corresponds to
subcompany. A lookup window will appear, refer to Figure 8.
5. Place the arrow key on the Subcompany Code that you will use. Click Select.
NOTE: Choose the pick list button that corresponds to the transaction.
9. Press on main window after using the BOS/e Audit Trail Manager.
Chapter
BOS/e AUDIT TRAIL MANAGER
Conclusion
5
After reading through this manual, users are expected to be able to
perform the following:
Audit user activities
Audit BOS/e component activities
Audit Table activities
Generate BOS/e Audit Trail Manager Reports