Banner 7 FAQs.doc

Banner 7.0 FAQ

(Updated May 26, 2006)

NOTE: Enriching SunGard Higher Education functionality and/or updating technology may affect your current Oracle license. This has been communicated several times via release information, FAQs, and listserve postings. If your institution elects to apply one of our latest technologies, such as Workflow or self-service products, and you are presently under Oracle's concurrent user metric, there may be an impact on your current user limitations that requires you to migrate your Oracle programs. Please note that Oracle supports deployment of Forms 9i/Forms 10g only on the web. As a result, Banner 7.0 forms can only be deployed on the web. Client/server deployment is not supported.

What is the financial impact of an Oracle migration on your institution? Based on Oracle's current policy, you are eligible to receive credits to apply to the current processor-based metric. This may result in a migration that has zero cost, nominal cost, or quite frankly, a significant cost depending on your site's licensed concurrent user count and current hardware configuration.

There are tremendous benefits to migrating your Oracle license to the current processor-based metric. Obvious reasons are eliminating the need to monitor users and adding functionality, features, and/or products. Please contact your Account Manager to assess your license and the potential cost of your migration.

What is the expected release date for Banner 7.0?What is the minimum database requirement for Banner 7.2?What is the minimum database requirement for Banner 7.3?What are the technical requirements for Banner 7.0?When will the Oracle 10g database be supported for Banner 7.x?Is the client/server mode of deployment supported with Banner 7.0?What are the overall hardware and software requirements for Banner 7.0?What browsers does SunGard Higher Education recommend for Banner 7.0?We use Macs in my organization. What must I do to use Banner 7.0?Do I need to upgrade from 5.x to 6.0 and then to 7.0? Or can I go from 5.x directly to 7.0?Do I need to do anything to my Banner 6.x data to prepare for the migration to 7.0?Can I mix products from the Banner 6.x release with products from the Banner 7.0 release?Which operating systems are supported as a web forms server to deploy Internet-native Banner 7.0?Is there a new user interface with Banner 7.0? What does it involve?What enhancements besides the new user interface are included in Banner 7.0?What documentation is available for Banner 7.0?I am a current user of Banner Financial Aid. If I upgrade to Banner Financial Aid 7.0, will I remain up-to-date

with the most current regulatory requirements?When will Banner 5.x be desupported?Is a Banner 7.0 upgrade CD available to clients?Where can I get more information?Will Banner 7.0 have Dynamic Help?Is Banner 7.0 compatible with line extension products?Are there any known issues for Banner 7.0?

Banner 7.0 FAQ Page 1

1. What is the expected release date for Banner 7.0?

The U.S. version of Banner 7.0 was delivered on January 18, 2005. Non-U.S. versions were released three to six months after the U.S. version.

2. What is the minimum database requirement for Banner 7.2?

Banner General 7.2 requires a minimum of Oracle 9i, Release 2 database with JVM (Version 9.2.0.5, Enterprise Edition). Banner General 7.2 also supports the Oracle 10g database.

The Banner General 7.1.1 release, which was rolled into Banner General 7.2, enables the web service based integration to Campus Card and Housing. For the installation script that registers the XML schemas to run successfully, Banner General 7.1.1 requires Oracle 9i, Version 9.2.0.5.

3. What is the minimum database requirement for Banner 7.3?

Banner General 7.3 requires a minimum of Oracle 9i, Release 2 database with JVM (Version 9.2.0.6, Enterprise Edition). Banner General 7.3 also supports the Oracle 10g database. Version 9.2.0.6 is not available for Open VMS. For Open VMS clients who are using the Campus Card and/or Housing Integration APIs, Oracle Version 9.2.0.7 is required. If those APIs are not being used, then Version 9.2.0.5 is recommended.

SunGard Higher Education will support RAC with the May release. For additional information, refer to FAQ CMS-11533 (Banner Support on RAC) on the Customer Support Center.

4. What are the technical requirements for Banner 7.0?

Database

Banner 7.0 requires a minimum of Oracle 9i, Release 2 database with JVM (Version 9.2.0.4, Enterprise Edition). However, if you meet any of the following criteria, you must be at a minimum of 9.2.0.5.

You are running VMS. Your database was built using the Oracle 9.2.0.4 toolset. You are fully implementing the Banner events for integration with LDI

for e-Procurement version 1.1 or future integrations. You are upgrading to Banner General 7.1.1 or Banner General 7.2.

For additional information, refer to FAQ CMS-2554 (Oracle RDBMS Versions) on the Customer Support Center.


Forms

Banner 7.0 requires Oracle Forms and Reports 10g and must be deployed using the Oracle Application Server 10g as well.

Application Server

Both Internet-native Banner (INB) and Self-Service Banner require Oracle 10g. The minimum version is 9.0.4.1 for both Banner and Workflow. For INB, you need to be at a minimum of Oracle JInitiator 1.3.1.18.

For additional information, refer to FAQ CMS-2228 (Oracle Web Application Server Versions) on the Customer Support Center.

Note: We discovered screen-painting issues (overlapping fields) with the earlier version of JInitiator. The problem is fixed by using the Oracle JInitiator version 1.3.1.18, which is certified only with the Oracle Application Server version 9.0.4.1.

5. When will the Oracle 10g database be supported for Banner 7.x?

The Oracle 10g database is supported with the Banner General 7.2 release, delivered in October 2005 for Unix and Windows operating systems.

We want to thank the beta clients (New Mexico Highlands University, Villanova University, University of Illinois, and University of Richmond) for partnering with us in the beta test.

UDC (Unified Digital Campus) Support for Oracle 10g

The following releases of SunGard Higher Education UDC products support the Oracle 10g database:

Luminis Channels for Banner 7.1 Luminis Platform III.2 and III.3.1 Workflow 4.1 e~Print Reports 2.1-1 Banner XtenderSolutions 7.0 LDI for e-Procurement 1.1+ LDI for e-Learning 3.0 and Banner Intcomp 7.0 Operational Data Store 2.2 Enterprise Data Warehouse 1.2


A separate FAQ includes details about the configuration and code changes that support the Oracle 10g database.

Known Issues

Terminated Session When Using the Common Matching APIThe Common Matching API may cause a user’s session to terminate with a core dump. This behavior is due to an internal Oracle error and only occurs in certain data configurations when SQL tracing is turned on for the session. This problem is related to Oracle bug 4157342 (QUERY WITH MULTIPLE UNPREPARED NESTED CURSORS CORRUPTS EXECUTION HEAP) and is present in all versions of Oracle 10g Release 1 (10.1.0.x). If the problem occurs, the preferred workaround is turning off SQL tracing.

Oracle announced that the bug is fixed in the upcoming Oracle 10g Release 2 (10.2.0.0). SunGard Higher Education requested and received a back port of the bug fix to 10.1.0.4 for Solaris and verified that the problem is resolved. As clients start migrating to Oracle 10g with the Banner 7.2 release, SunGard Higher Education will evaluate the need to request back ports for other platforms.

Invalid Dictionary ObjectsIn Oracle 10g, Version 10.1.0.4 and earlier, certain dictionary objects may randomly become invalid. This does not normally cause any problem and can be ignored because the objects will be revalidated on access. In some circumstances (for example, when using the OEM Storage Manager), these invalid objects may cause a loss of functionality. An Oracle patch in Storage Manager 10.1.0.4 (Patch 3377171), with a back port available to 10.1.0.3, addresses this issue. The following objects are affected:

DBA_HIST_FILESTATXS,DBA_HIST_LATCH DBA_HIST_LATCH_MISSES_SUMMARY DBA_HIST_DB_CACHE_ADVICE DBA_HIST_ROWCACHE_SUMMARY DBA_HIST_SGASTAT DBA_HIST_SYSSTAT DBA_HIST_SQLSTAT DBA_HIST_SQLBIND DBA_HIST_SYSTEM_EVENT DBA_HIST_WAITSTAT DBA_HIST_SYS_TIME_MODEL DBA_HIST_OSSTAT DBA_HIST_PARAMETER DBA_HIST_SEG_STAT


DBA_HIST_ACTIVE_SESS_HISTORY DBA_HIST_TABLESPACE_STAT DBA_HIST_SERVICE_STAT DBA_HIST_SERVICE_WAIT_CLASS DBMS_SWRF_REPORT_INTERNAL DBMS_SQLTUNE

The following MetaLink references are available:

Note:312076.1 - Invalid Objects Surface in Random Note:314461.1 - After 10.1.0.4 Grid Control Patchset Applied, no

Longer Displays Invalid Objects For Sys

6. Is the client/server mode of deployment supported with Banner 7.0?

No. Banner 7.0 uses Oracle Forms 10g, and that version does not support client/server. Banner 7.0 must be deployed only on the web in Internet-native mode.

7. What are the overall hardware and software requirements for Banner 7.0?

Because Banner 7.0 uses Oracle Forms 10g and that version does not support client/server (only Internet-native), Banner requires the web browsers that Oracle supports for Forms 10g deployment.

The following are the requirements for installing Oracle Developer Suite 10g and running Banner 7.0 INB.

Hardware Requirements

Hardware Item RequirementsCPU A Pentium or compatible processor (500

MHz recommended)Disk space Complete: 943 MBVideo Can display a minimum of 256 colors

Memory Requirements for Oracle Developer Suite Components

Component MemoryOracle Reports Developer Minimum 128 MB

Recommended 256 MBOracle Forms Developer Minimum 128 MB

Recommended 256 MB


Operating Environment Software Requirements

Software Item RequirementWindows Operating Environment

Microsoft Windows NT 4.0 Service Pack 6a

Microsoft Windows 2000 Service Pack 3 or greater

Microsoft Windows XP Professional Edition Service Pack 1 or greater

Online Documentation Requirements

Item RequirementsOnline HTML reader Netscape Navigator 4.7 or higher

Microsoft Internet Explorer 5.0 or higherOnline PDF reader Acrobat Reader 3.0 or higher

Acrobat Reader+Search 3.0 or higher Acrobat Exchange 3.0 or higher PDFViewer web browser plug-in 1.0 or

higherDisk space 130 MB

Oracle Home Considerations

Your Oracle home is the top-level directory in which you install Oracle software.

Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with its previous versions (Oracle9iDS Release 2 (9.0.2) or Oracle Internet Developer Suite Release 1.0.2.x).

Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with any Oracle databases, including Oracle9i Database Release 2.

Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with an Oracle Application Server Forms and Reports Services 10g standalone server instance.

Oracle Developer Suite 10g (9.0.4) can coexist in the same Oracle home with any installation of Oracle Application Server 10g (9.0.4), with the exception of Oracle Application Server Infrastructure.

8. What browsers does SunGard Higher Education recommend for Banner 7.0?

SunGard Higher Education completed testing with the following browsers:


Internet-native Banner 7.0

In this area, SunGard Higher Education looks to Oracle's client platform support certification matrix at http://www.oracle.com/technology/products/forms/htdocs/10g/clientsod_forms10g.html

Microsoft Internet Explorer 6.0 (with Oracle JInitiator 1.3.1.18) Netscape 7.0x (with Oracle JInitiator 1.3.1.18) Macintosh client - Safari 1.2 (Sun plug-in 1.4.2) for Mac OS X (1.4

JDK); must use Forms patch set patch2 (9.0.4.2)

Internet-native Banner via the Luminis Portal

Microsoft Internet Explorer 6.0 Macintosh client - Safari 1.2 (Sun plug-in 1.4.2) for Mac OS X (1.4

JDK); must use Forms patch set patch2 (9.0.4.2)

Self-Service Banner 7.0

Microsoft Internet Explorer 6.0 Netscape 7.01 Netscape 7.2 Mozilla 1.7 Microsoft Internet Explorer 5.2 for Macintosh OS X Macintosh client - Safari 1.2 for Mac OS X

Self-Service Banner via the Luminis Portal

Microsoft Internet Explorer 6.0 Netscape 7.2 Macintosh client - Safari 1.2 for Mac OS X

At this time we do not support the following browsers:

Browser Java for INB SUN Java Plugin/WebStart for INB AOL's repackaged browser LINUX desktop browsers Other non-Windows browsers

Customer Support Center FAQ CMS-13329 has information on how to get Firefox/Mozilla to work with Oracle JInitiator and Banner INB.

9. We use Macs in my organization. What must I do to use Banner 7.0?

Banner 7.0 must be implemented in an Internet-native mode. Therefore, you must run Banner 7.0 with an Oracle-supported Internet browser for


http://www.oracle.com/technology/products/forms/htdocs/10g/clientsod_forms10g.html

the Mac. This configuration requires Safari 1.2 browser (with Sun plug-in 1.4.2) on Mac OS X. You must use Forms patch set patch2 (9.0.4.2). This can be a runtime usage of the patch2 (iAS10g 9.0.4.2).

10. Do I need to upgrade from 5.x to 6.0 and then to 7.0? Or can I go from 5.x directly to 7.0?

As is the case with any major Banner upgrade, you must upgrade to the next major release (Banner 6.0) first. You can then upgrade directly to the next major release (Banner 7.0). It is not necessary to install all interim 6.x releases before migrating to release 7.0. Specifically, the following migration path is required for your licensed products:

1. Upgrade all Banner baseline products to 6.0.2. Upgrade all Banner baseline products to 7.0 (all interim 6.x releases

are included in 7.0).3. Upgrade all Banner self-service products to 6.0.4. Upgrade all Banner self-service products to 7.0.

11. Do I need to do anything to my Banner 6.x data to prepare for the migration to 7.0?

Yes. A primary key was added to the GOREMAL table to prohibit duplicates. The primary key consists of the PIDM, e-mail type, and e-mail address. This change enables Banner and external systems to uniquely identify rows in the table and is necessary for the e-mail API to function correctly. Any duplicate records currently in the e-mail table will not be allowed once the primary key is placed on the table. Therefore, duplicates must be removed before the General 7.0 upgrade begins.

To help you prepare for this, a script is available to identify the existing duplicate records that need to be removed before applying the primary key to the GOREMAL table. The new primary key will be applied during the upgrade to 7.0, but you can analyze and cleanse your data now. You should re-run the script before applying 7.0 to determine if any new records also need to be removed/consolidated. The script can be run against a Banner 5.x or 6.x database. The script will identify duplicates in GOREMAL and will not delete any GOREMAL records.

The script to identify the duplicates is in the Review Documentation section of the Customer Support Center. The file is named goremaldup


12. Can I mix products from the Banner 6.x release with products from the Banner 7.0 release?

No. To use the functionality in Banner 7.0, you must upgrade all products at the same time.

13. Which operating systems are supported as a web forms server to deploy Internet-native Banner 7.0?

INB can be deployed on web servers running Windows, Solaris (SPARC), AIX, HP-UX, HP Tru64 UNIX, and Linux (Intel). Please see FAQ CMS-3603 (Oracle Forms Versions) for details on exact versions.

14. Is there a new user interface with Banner 7.0? What does it involve?

Most definitely yes! Banner 7.0 includes the following enhancements:

Internet-native Banner (INB)

All FormsMigrating to Oracle Forms 10gEnlarging window to 1024 x 768Adding "separator bar" (where appropriate)Changing font to Verdana Adding prompts to establish relationship between labels and fieldsMaking disabled text easier to readAdding pop-up options list with right mouse clickAdding smart toolbar that does not re-draw each time a form is openedEnabling user-defined window colorAdding option to highlight required fieldsReplacing blue labels with iconAdding F5 (Find) for direct access to forms, menus, reports, QuickFlows

Validation FormsAdding more rows to the bottom of pages

Selected FormsAdding tabs for improved internal window navigation

Self-service and Channels

New Cascading Style Sheet that includes:Tabs for easier navigationRepositioned fields for better usabilityNew Verdana fontSeparator bar


15. What enhancements besides the new user interface are included in Banner 7.0?

Application Programming Interface (API) Development

We are transforming Banner into an open API (Application Programming Interface), message-aware architecture. This requires us to migrate Banner business logic from Banner forms, web pages, and processes into common procedures stored in the database. This enables any Banner object to call the same routine to perform a business function. Making these stored procedures message-aware allows non-Banner modules to invoke these same business functions, enabling integration across the Unified Digital Campus.

Banner 7.0 targets API development for business entities that enable integration with those systems ranked highest by the Banner Advisory Board and the Pillar Institutions, namely:

Learning management systems Housing systems One-card systems Library systems Bookstore systems e-Procurement systems

Multiple PIDM Prevention

The Multiple PIDM Prevention enhancement creates a single rule-driven process that can help institutions determine whether an entity (person or non-person) is truly new to the system before it is added to the database. This process, called Common Matching, can be called from online forms, C programs, and external interfaces. Anything that can insert a new SPRIDEN record first calls this common matching process to check for an existing record. This includes the basic person forms and data loads (recruiting search files, test score files, financial aid application files, etc.).

Restricted Access to Personally Identifiable Information (PII)

Banner 7.0 addresses two important issues surrounding the protection of private information:

Ability to restrict an Banner user's access from information about a person for whom he/she does not have a legitimate business need

Ability to mask sensitive information while displaying other mission critical data for a person


The solution is to add a Fine-Grained Access Control (FGAC) policy function to the SPRIDEN table. This function determines whether the user should have access to a given PIDM. To control the display or masking of sensitive information, new forms and tables define the fields and types of masking that should be applied to personal data.

New Value-Based Security Using Fine-Grained Access Control

The old Banner Value-Based Security (VBS) was replaced with a new rules process that implements Oracle Fine-Grained Access Control (FGAC). VBS restricts a user’s access, either in an insert, update, delete, or select activity, to rows of a database table based on a column value. An example is allowing user ID SMITH to see all Admissions records but insert, update, and delete only those records with college code ‘AS’. Oracle’s Fine-Grained Access dynamically appends the restrictive ‘where’ clause to SQL statements during execution.

16. What documentation is available for Banner 7.0?

Release guides, upgrade guides, object lists, database comparison reports, entity relationship diagrams, user guides, handbooks, technical reference manuals, online help, and Banner Bookshelf can be downloaded from the Customer Support Center.

17. I am a current user of Banner Financial Aid. If I upgrade to Banner Financial Aid 7.0, will I remain up-to-date with the most current regulatory requirements?

Banner Financial Aid 7.1 provides up-to-date regulatory support. This release was delivered in January 2005.

18. When will Banner 5.x be desupported?

There are no additional upgrades to the 5.x Banner product after December 31, 2004 with the following product-specific notes:

Banner Financial Aid 5.x provides support through the Summer Regs 2004-2005 (August 2004). Fall Regs/Early Decision 2005-2006 is an optional release and is supported in Banner Financial Aid 6.x only. Any institution planning to use Fall Regs/Early Decision 2005-2006 functionality must be on Banner 6.x for new year processing of Early Decision aid in Financial Aid.

Banner HR 5.x US, Canada, and Puerto Rico Year End Regulatories were supported through the reporting cycle for tax year 2004 (into the early part of 2005).


TRA 1098T processing in 5.x was supported through the reporting cycle for tax year 2004 (into the early part of 2005).

1099 Misc processing in 5.x was supported through the reporting cycle for tax year 2004 (into the early part of 2005).

19. Is a Banner 7.0 upgrade CD available to clients?

Yes. A CD was sent to all clients. You can also download the release from the Customer Support Center.

20. Where can I get more information?

The following documents are available on the Customer Support Center:

Banner 7 Frequently Asked Questions (this document) Banner 7 Documentation Deliverables Banner 7 Overview Sheet Banner 7.0 Glossary of Terms Banner 7 Oracle Sequencing for IDs and PIDMs FAQ Banner 7 Common Matching FAQ New Value-Based Security FAQ New Banner Online Help Overview Protection of Personally Identifiable Info - information sheet New Value-Based Security (VBS) Overview White Paper on APIs and Messages Banner Entity APIs by Product Banner Entity APIs by Program Banner 7 API Overview Luminis Channels for Banner Descriptions Luminis Channels for Banner FAQ Concurrent Curricula: Methods for Selecting and Maintaining CC Banner 7.0 Concurrent Curricula Foundation Oracle Forms 9i Conversion Known Issues Banner 7 Description of Tabbed Forms

21. Will Banner 7.0 have Dynamic Help?

Yes. Banner 7.0 supports both Local Dynamic Help and Banner Dynamic Help:

Banner will provide the infrastructure for Local Dynamic Help indefinitely. This is where we recommend clients put their customized information.

SunGard Higher Education delivered Banner Dynamic Help with the 7.0 Release. However, we are gradually moving content from Dynamic Help into our new online help. As a result, the 7.0 Dynamic


Help may not be up-to-date. We encourage clients to use the new online help rather than the Banner Dynamic Help for the most current 7.0 information.

Once all the content is moved to the new online help (in a future release), we will stop delivering Banner Dynamic Help. Column information will continue to be available in both Local Dynamic Help and Banner Dynamic Help.

22. Is Banner 7.0 compatible with line extension products?

Workflow

Workflow 4.1 supports Banner 7.0. This support release allows clients to upgrade from Banner 6.x to 7.0. Workflow 4.1 was released in January 2005.

Banner XtenderSolutions (BXS)

Banner XtenderSolutions (BXS) version 7.0 was released with all other Banner 7.0 modules in January 2005. This release continues and expands the baseline integration and minimizes any maintenance issues for SunGard Higher Education clients who use the Banner suite, including our imaging solutions.

Operational Data Store (ODS)

Operational Data Store 2.1 was released so clients moving to Banner 7.0 can remain compliant. This release will also work with Banner 6.x.

HigherMarkets for Banner (LDI for e-Procurement)

LDI for e-Procurement 1.1 was released in March 2005 and is supported in Banner 6.x and 7.1. The primary focus of the 1.1 release is to simplify the deployment and maintenance of the LDI solution by using a single J2EE web container to house all of the messaging components. For Banner 6.x, the e-procurement solution requires Banner General 6.2.2 (released in March 2005), Banner Finance 6.2, and SciQuest HigherMarkets 4.2. For Banner 7.1, the e-procurement solution requires Banner General 7.1, Banner Finance 7.1, and SciQuest HigherMarkets 4.2. Banner General 7.1 and Banner Finance 7.1 were releasesd in May 2005.


e-Learning Solution (LDI for e-Learning)

Banner Intcomp 7.0 was released in January 2005 so clients moving to Banner 7.0 can remain compliant. This release also provides compatibility between Banner 7.0 and Luminis III.2.

e~Print

Both e~Print 2.0 and 2.1 (released in December 2004) are compatible with Banner 7.0.

23. Are there any known issues for Banner 7.0?

Yes, the following issues exist for Banner 7.0. We are working to correct these issues and will deliver solutions as soon as they are developed and thoroughly tested.

Oracle Reports

The infrastructure of Oracle Reports changed significantly between Reports 6i and Reports 10g. An Oracle Reports security infrastructure layer was added and delivered in the Banner General 7.1 release. You must upgrade to Banner 7.1 to get the benefits of the security layer modifications.

If you are running Banner 7.0 (and have not upgraded to Banner 7.1) and are running Oracle Reports, we recommend the following:

Do not make any .rep files that produce output containing sensitive data available to the REPORTS_PATH variable on any shared reports server.

Avoid specifying parameter form = YES when running reports on any shared reports server.

As an interim workaround, configure and run Oracle Reports for Banner 7.0 using the OC4J component (locally) on a secured workstation.

Performance

In response to feedback from client beta testing, we are working on performance improvements for the Address Review and Verification Form (GOAADDR) and the Population Selection Definition Rules/Population Selection Inquiry Forms (GLRSLCT/GLISLCT).


Confidential Business Information

------------------------------------------------------------------------------------------------------------------------------------------------------------------This documentation is proprietary information of SunGard Higher Education and is not to be copied, reproduced, lent or disposed of, nor used for any purpose other than that for which it is specifically provided without the written permission of SunGard Higher Education.

Prepared By: SunGard Higher Education4 Country View RoadMalvern, Pennsylvania 19355United States of America

©2006 SunGard. All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or the information contained herein is prohibited.

In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization’s own choosing.

Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.



Date post:	03-Nov-2014
Category:	Documents
Upload:	sammy17
View:	10 times
Download:	7 times

Banner 7 FAQs.doc

Documents