Skip Headers
Oracle® Outside In XML Export Developer's Guide
Release 8.3.7

Part Number E12888-02
Go to Documentation Home
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

2 Windows Implementation Details

The Windows implementation of this software is delivered as a set of DLLs. For a list of the currently supported platforms, see:

Click on Outside In Technology, then click the Certification Information PDF.

The 64-bit version of sccvw.dll will not load on an AMD-64 system without Visual C++ runtime version 8 installed. This happens because the system is missing the msvcr80.dll library, which is required. Users can download the required library from the following location:

2.1 Installation

To install the demo version of the SDK, copy the contents of the ZIP archive (available on the Web site) to a local directory of your choice.

This product requires the Visual C++ libraries included in the Visual C++ Redistributable Package available from Microsoft. There are versions of this package for the x86 and x64 versions of Windows. This can be downloaded from, by searching on the site for the following packages:

The required download version is the "2005 SP1 Redistributable Package."

Outside In requires the msvcr80.dll redistributable module.

The installation directory should contain the following directory structure:

Directory Description
\docs Includes HTML and PDF versions of the manual you are reading right now. Release notes contain more up-to-the-minute information on product changes which occurred after documentation production.
\redist Contains a working copy of the Windows version of the technology.
\sdk\common Contains the C include files needed to build or rebuild the technology.
\sdk\demo Contains the compiled executables of the sample applications.
\sdk\lib Contains the library (.lib) files needed for the products.
\sdk\resource Contains localization resource files.
\sdk\samplecode Contains a subdirectory holding the source code for a sample application.
\sdk\samplefiles Contains sample input files authored in a variety of popular graphics, word processor, compression, spreadsheet and presentation applications, designed to exercise XML Export.
\sdk\XXSchemaDocs Contains a Flexiondoc manual, version 5.4

2.1.1 NSF Support

Notes Storage Format (NSF) files are produced by the Lotus Notes Client or the Lotus Domino server. The NSF filter is the only Outside In filter that requires the native application to be present to filter the input documents. Due to integration with an outside application, NSF support will not work with redirected I/O, when an NSF file is embedded in another file, or with IOTYPE_UNICODEPATH. Either Lotus Notes version 8 or Lotus Domino version 8 must be installed on the same machine as OIT. SCCOPT_LOTUSNOTESDIRECTORY should be set to the directory containing the nnotes.dll. NSF support is only available on the Win32, Linux x86-32, and Solaris Sparc 32 platforms.

2.2 Libraries and Structure

The following is an overview of the files in the main installation directory for all five Outside In export products.

2.2.1 API DLLs

These libraries implement the API. They should be linked with the developer's application. Files with a .lib extension are included in the SDK.

Library Description HTMLExport ImageExport PDF Export Search Export XML Export
sccda.dll Data Access module X X X X X
sccex.dll Export module X X X X X
sccfi.dll File Identification module (identifies files based on their contents). X X X X X

The File ID Specification may not be used directly by any application or workflow without it being separately licensed expressly for that purpose.

2.2.2 Support DLLs

The following libraries are used for support.

Library Description HTML Export ImageExport PDF Export Search Export XML Export
ccflex.dll A data model adapter that converts from stream model utilized by Outside In filters to the FlexionDoc Tree model used as a basis by XML Export.         X
exhtml.dll HTML Export module X        
exxml.dll XML Export module         X
libexpatw.dll A third-part XML parser         X
ocemul.dll Output component emulation module X X X X X
ospdf.dll PDF generation module     X    
oswin*.dll Interface to the native GDI implementation

oswin32.dll is the 32-bit version, oswin64.dll is the 64-bit version

X X   X X
sccanno.dll The annotation module X X X    
sccca.dll Content Access module (provides organized chunker data for the developer) X X X    
sccch.dll Chunker (provides caching of and access to filter data for the export engines) X X X X X
sccdu.dll Display Utilities module (includes text formatting) X X X X X
sccexind.dll The core engine for all Search Export formats: SearchText, SearchHTML, SearchML and PageML       X  
sccfmt.dll Formatting module (resolves numbers to formatted strings) X X X X X
sccfut.dll Filter utility module X X X X X
sccind.dll Indexing engine. In Search Export, it handles common functionality. X X X X  
scclo.dll Localization library (all strings, menus, dialogs and dialog procedures reside here) X X X X X
sccole2.dll OLE rendering module X X X X X
sccsd.dll Schema Definition Module Manager (brokers multiple Schema Definition Modules)         X
sccut.dll Utility functions, including IO subsystem X X X X X
sccxt.dll XTree module         X
sdflex.dll Schema Definition module (handles conversion of XML string names and attribute values to compact binary representations and vice versa)         X
wvcore.dll The GDI Abstraction layer X X X X X

2.2.3 Engine Libraries

The following libraries are used for display purposes.

Library Description HTML Export Image Export PDF Export Search Export XML Export
debmp.dll Raster rendering engine (TIFF, GIF, BMP, PNG, PCX…)     X   X
dess.dll Spreadsheet/Database (Excel, Calc, Lotus 123…)   X X   X
detree.dll Archive (ZIP, GZIP, TAR…)   X X    
devect.dll Vector/Presentation rendering engine (vector drawings, presentations, and charts) X X X   X
dewp.dll Document (Word, Writer, WordPerfect…)   X X X X

2.2.4 Filter and Export Filter Libraries

The following libraries are used for filtering.

Library Description HTML Export Image Export PDF Export Search Export XML Export
vs*.dll Filters for specific file types (there are more than 150 of these filters, covering more than 500 file formats) X X X X X




Support files for the vslwp filter. X X X X X Support file for the vsnsf filter. X X X X X
exgdsf.dll Export filter for GIF, JPEG, and PNG graphics files. X       X
eximg.dll Extended image conversion module   X      
expagelayout.dll Page layout module     X    
sccimg.dll Image conversion module X X     X

2.2.5 Premier Graphics Filters

The following are graphics filters.

Library Description HTML Export ImageExport PDF Export Search Export XML Export
i*2.flt 30 .flt files (import filters for premier graphics formats) X X X X X
isgdi32.dll Interface to premier graphics filters X X X X X

2.2.6 Additional Files

The following files are also used.

Library Description HTML Export ImageExport PDF Export Search Export XML Export
adinit.dat Support file for the vsacd2 filter X X X X X
cmmap000.bin Tables for character mapping (all character sets) X X X X X
cmmap000.sbc Tables for character mapping (single-byte character sets). This file is located in the /common directory. X X X X X
cmmap000.dbc Identical to cmmap000.bin, but renamed for clarity (.dbc = double-byte character). This file is located in the common directory. X X X X X
flexiondoc.dtd The DTD version of the Flexiondoc schema         X
flexiondoc.xsd The schema version of the Flexiondoc schema         X

2.3 The Basics

The following is a discussion of some basic usage and installation features.

All the steps outlined in this section are used in the sample applications provided with the SDK. Looking at the code for the exsimple sample application is recommended for those wishing to see a real-world example of this process.

2.3.1 What You Need in Your Source Code

Any source code that uses this product should #include the file sccex.h and #define WINDOWS and WIN32 or WIN64. For example, a Windows application might have a source file with the following lines:

#define WINDOWS         /* Will be automatically defined if your
                           compiler defines _WINDOWS */
#define WIN32
#include <sccex.h>

The developer's application should be linked to the product DLLs through the provided libraries.

2.3.2 Options and Information Storage

This software is based on the Outside In Viewer Technology (or simply "Viewer Technology"). When using the Export products, a list of available filters and a list of available display engines are built by the technology, usually the first time the product runs. You do not need to ship these lists with your application. The lists are automatically recreated if corrupted or deleted.

The files used to store this information are stored in an .oit subdirectory in \Documents and Settings\user name\Application Data.

If an .oit directory does not exist in the user's directory, the directory is created automatically. The files are automatically regenerated if corrupted or deleted.

The files are:

  • *.f = Filter lists

  • *.d = Display Engine lists

  • *.opt = Persistent options

Some applications and services may run under a local system account for which there is no users "application data" folder. The technology first does a check for an environment variable called OIT_DATA_PATH. Then it checks for APPDATA, and then LOCALAPPDATA. If none of those exist, the options files are put into the executable path of the UT module.

These file names are intended to be unique enough to avoid conflict for any combination of machine name and install directory. This allows the user to run products in separate directories without having to reload the files above. The file names are built from an 11-character string derived from the directory the Outside In technology resides in and the name of the machine it is being run on. The string is generated by code derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm.

The software still functions if these lists cannot be created for some reason. In that situation, however, significant performance degradation should be expected.

2.3.3 Structure Alignment

Outside In is built with 8-byte structure alignment. This is the default setting for most Windows compilers. This and other compiler options that should be used are demonstrated in the files provided with the sample applications in samples\win.

2.3.4 Character Sets

The strings passed in the Windows API are ANSI1252 by default.

To optimize performance on systems that do not require DBCS support, a second character mapping bin file, that does not contain any of the DBCS pages, is now included. The second bin file gives additional performance benefits for English documents, but cannot handle DBCS documents. To use the new bin file, replace the cmmap000.bin with the new bin file, cmmap000.sbc. For clarity, a copy of the cmmap000.bin file (cmmap000.dbc) is also included. Both cmmap000.sbc and cmmap000.dbc are located in the \common directory of the technology.

2.3.5 Runtime Considerations

The files used by the product must be in the same directory as the developer's executable.

2.4 Changing Resources

Outside In XML Export ships with the necessary files for OEMs to change any of the strings in the technology as they see fit.

Strings are stored in the lodlgstr.h file found in the resource directory. The file can be edited using any text editor.


Do not directly edit the scclo.rc file. Strings are saved with their identifiers in lodlgstr.h. If a new scclo.rc file is saved, it will contain numeric identifiers for strings, instead of their #define'd names.

Once the changes have been made, the updated scclo.dll file can be rebuilt using the following steps:

  1. Compile the .res file:

    rc /fo ".\scclo.res" /i "<path to header (.h) files folder>" /d "NDEBUG" scclo.rc
  2. Link the scclo.res file you've created with the scclo.obj file found in the resource directory to create a new scclo.dll:

    link /DLL /OUT:scclo.dll scclo.obj scclo.res


    Developers should make sure they have set up their environment variables to build the library for their specific architecture. For Windows x86_32, when compiling with VS 2005, the solution is to run vsvars32.bat (in a standard VS 2005 installation, this is found in C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\). If this works correctly, you will see the statement, "Setting environment for using Microsoft Visual Studio 2005 x86 tools." If you do not complete this step, you may have conflicts that lead to unresolved symbols due to conflicts with the Microsoft CRT.
  3. Embed the manifest (which is created in the \resource directory during step 2) into the new DLL:

    mt -manifest scclo.dll.manifest -outputresource:scclo.dll;2

If you are not using Microsoft Visual Studio, substitute the appropriate development tools from your enviroment.


In previous versions of Outside In, it was possible to directly edit the SCCLO.DLL using Microsoft Visual Studio. Outside In DLLs are now digitally signed. Editing the signed DLL is not advisable.