Preface

This guide describes how to enable interoperability between the Microsoft Office suite of products and the Oracle Application Server set of components. This includes a description of the Microsoft Office-centric architecture, the Microsoft Office Extensibility technologies, the Oracle Application Server components that can interoperate, and many step-by-step procedures that describe how to build Microsoft Office interoperability solutions.

Note: For the portable document format (PDF) version of this guide, when a URL breaks onto two lines, the full URL data is not sent to the browser when you click it. To get to the correct target of any URL included in the PDF, copy and paste the URL into your browser's address field. In the HTML version of this guide, you can click a link to directly display its target in your browser.

Audience

This guide is intended for Oracle Application Server developers and administrators who want to configure Oracle Application Server components to interoperate with Microsoft Office, and are familiar with Microsoft Office applications and Microsoft programming languages.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Related Documents

You can find all documentation related to Oracle Application Server, including the release notes, on the Oracle Application Server documentation page of the Oracle Technology Network (OTN): http://www.oracle.com/technology/documentation/appserver.html

For additional information and to post queries about Oracle Application Server and Microsoft Office interoperability, access the Microsoft Office Interoperability discussion forum on OTN:

http://forums.oracle.com/forums/forum.jspa?forumID=266

Conventions

The following text conventions are used in this document:

Convention	Meaning
boldface	Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic	Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace	Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
CAPITALIZED	Capitalized text indicates procedure names.
< >	Angle brackets enclose user-supplied information.
[ ]	Brackets enclose optional clauses from which you can choose one or none.
. . .	Vertical ellipsis points in an example mean that information not directly related to the example has been omitted.

Accessing the Demonstration Support Files

The demonstration support files that are described in various chapters of this guide are available on the ORACLE FUSION MIDDLEWARE and Microsoft Interoperability page on Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/middleware/fusion-middleware-microsoft-interoperability.html. The ZIP file microsoft-interoperability-guide-demo-support.zip (found in the Developer's Guide section) contains folders with support files for specific chapters in this guide. These support files are necessary to run the example procedures. The individual chapters' prerequisites sections will have additional details about what must be done with the support files. The following table maps example folders to the chapters in which they are used.

Folder Name	Chapter Title
selfservice	Chapter 4, "Creating Smart Documents That Interact with Self-Service Business Processes"
fillingforms	Chapter 5, "Completing Forms and Entering Data Using Microsoft Office"
securingsmartdocs	Chapter 6, "Securing Smart Documents and Web Services"
identitymanagement	Chapter 10, "Provisioning User Identity Information and Alerting Microsoft Outlook Contacts"
smarttags	Chapter 11, "Accessing in-Context Web Information and Invoking an Enterprise Portal"
reports	Chapter 13, "Delivering Enterprise Reports to Microsoft Office with Oracle Reports"

See Also: Appendix A, "Code Examples" for details about code samples and template content that you may need to use in the sample demonstrations that are described in various chapters of this guide.