ILINX Export Demo
0 likes329 views
ILINX Export is a tool that enables extracting data and documents from enterprise content management (ECM) repositories through both a user interface and application programming interface. It allows exporting content in different formats to various locations based on search parameters for purposes such as public disclosure, controlled access, and compliance. Key benefits include flexible search options, integration with line of business applications and Oracle, and the ability to export images and files programmatically or via a simple user interface.
ILINX Export Demo
- 1. ExportExtract, convert and migrate data and documents from your ECM system.
- 2. Introducing ILINX ExportExtract data & documents from ECM repositoriesUI and APIILINX Export enables:DisclosurePublic accessControlled accessComplianceCompiling of select information
- 3. BenefitsWide variety of search parametersAllows calls from line-of-business apps.Works seamlessly with OracleEnables posting of info for public consumption and/or credentialed usersPull images from the system with a few clicksor programmaticallyUser-friendly
- 4. FeaturesExports to two different file formatsConfigure index settings to output to different locationsExported files can be transferredVariety of folder output structuresFlexible file naming conventionsConfigurable option to crawl & exportSimple install wizard
- 6. ILINX Export Job TypesEnterprise Server Export(Sequential or Portal) Export from a point in the past to presentWorkstationExport (Varied or Prompted) Utilize Predefined Saved Searches to perform one-time searches based on certain parametersEnterprise Server Web Service (Programmatically or API or SDK Mode)Gives users exposed code to customize the application
- 7. Jobs ScreenView job statuses, last date the job was run and the type of job it is
- 8. Job Information ScreenUser determines whether to run the job in Sequential or Varied mode
- 9. Oracle IPM InformationThe user must login with their User Name and PasswordA drop-down list of Saved Searches is displayed
- 10. Index SettingsChoose to save the document data to a MS SQL Server Table, a CSV file or choose not to save data at all
- 11. Database Field MappingMap the Oracle IPM Index Fields to the available fields in the MS SQL Server table
- 12. Comma Separated File FieldsCreate a list of Oracle IPM fields in the specific order you want them to be exported to the CSV file
- 13. File Output SettingsSpecify the Temporary Working Folder, the file format you want documents exported in, whether or not to include annotations and the Output Folder Structure
- 14. File Transfer SettingsSelect whether to use a Network Path or an FTP location to transfer exported files
- 15. Scheduling Jobs to RunSelect the day(s) of the week and time the search will query the database
- 16. Predefined Saved SearchesUsers can input values based on the predefined Saved Search they have selectedResults then appear in the Oracle IPM Search Results view window
- 17. Export SettingsThe Export Settings screen gives a summary of settings that the user has defined
- 18. API LevelUsers can customize the application at the API level by configuring the exposed code
- 19. ConclusionEnables data and documents to be extracted from ECM repositoriesFor managed exports at both the UI & API levelsILINX Export enables:DisclosurePublic accessControlled accessComplianceCompiling of select information for streamlining business processes
Editor's Notes
- #3: Multiple, programmable interfaces, from GUIs to portals, can be used to intuitively export in a variety configurations and formats.Enterprise Server (API) ILINX Export Enterprise Server provides an easy and consistent interface for the retrieval and display of images/documents from Oracle ECM repositories through standard Web service applications. To economically service a large number of external users, connection pooling can be utilized to reduce user access loads.Workstation (UI)Installed on end-user desktops, Workstation—or stand-alone mode—of ILINX Export allows individuals to access groups of documents from Oracle ECM software, then output the documents to a desired location, using meaningful file names. Using the querying power of Oracle, this flexible product extracts lists of documents, which can then be filtered manually.
- #4: Allows searches using a wide variety of search parametersIndex valuesMetadataFile namesAllows calls from line-of-business apps.Web portalsOracleSAPIBMWorks seamlessly with OracleQuery Oracle, massage the result set & output documents to a (separate) consumption server where they can be consumed by internal employees or external customers with a few mouse clicksStreamlines export of documents from Oracle systems, without added modificationsLeverages Oracle Saved Search settingsEnables posting of information for public consumption and/or credentialed usersImages can be pulled from the system with a few simple mouse clicks or programmatically from any web compliant web service – calls from API, such as:JAVA.NETColdFusionUser-friendly applicationEasy to masterIntuitiveDesigned for general usersIn Enterprise Server mode, can pool a configurable amount of user licenses for export purposes, economically allowing Internet community access to image files, while reducing user access loadsPromotes compliance by allowing flexible search and simple access to information
- #5: Exports to two different file formatsPDFTIFFIndex settings can be configured to output to different locationsCSVDatabaseExported files can be transferred to the following paths:NetworkFTPAllows a variety of folder output structuresOutput to a single folderUse indexes to generate a pathFlexible file naming conventionsConfigurable option to crawl and export documents from any point in the past at specific intervalsUser login, license pooling, communication, export & file creation – auto-enabledSupports Oracle-named queries and the creation of ad hoc queries to create lists of files for outputCan select specific documents to export from result set of queriesExported images and files are initially named based on index values—using a simple interface, the user determines names that are readable and meaningful to the individual or organization Export takes place with a simple clickSelect destination directory and annotation optionsSimple Install WizardOptimized for multi-user client server environmentLicenses utilized only during query or download, then released to service another user (Enterprise Server mode) Comprehensive logging of exports & queries run and documented functions performed by usersCan be used in public disclosure/auditing mode.Using the tool to produce a CD with images and index data can be used for disclosure or auditing
- #7: Enterprise Server (Sequential or Portal) Export Allows users to export documents from a point in the past based on the desired RecID, to the presentWorkstation (Varied or Prompted) Export Allows users to utilize Predefined Saved Searches to perform one-time searches based on parameters they setEnterprise Server (Programmatically or API or SDK Mode) Web Service Gives users the exposed code (foundation) or SDK to configure the application in a way that is custom for them The trigger is another program, not the user
- #8: From the ILINX Export Jobs screen, you can see what jobs you have and what mode they are in.You can view their statuses, the last date the job was run and the type of job it is (Sequential or Varied)From this screen you can select one of the buttons to Create a New Job, Edit a Job, Copy a Job, Delete a Job, View a Job, Run a Job, or Stop a Job.
- #9: When you Create a New Job or Edit an Existing Job, you must give the job a name. You must also determine if you want the job to run in Sequential or Varied Mode.Sequential mode allows users to choose a specific point in the past (represented by the RecID) and export all the documents from that point to the present.Varied mode allows users to export documents based on search fields and parameters set up in the Saved Searches. This is a one-time search.A Web Service Activation ID is generated for the job.
- #10: Users are then required to login to ILINX Export using their Oracle IPM User Name and Password.They also have access to their Saved Searches.
- #11: The Index Settings screen allows the user to determine where to save the document index metadata.Users can save this data to a Microsoft SQL Server Table, a CSV file, or they can choose not to save any document index data.
- #12: This screen allows users to map fields from Oracle IPM
- #13: Users will need to move indexes over from the Available Oracle IPM Index Fields, into the Oracle IPM Index Fields to Output. These fields will appear in the CSV file, and the user will need to determine the order within the Output table in which they want the indexes to appear in the CSV file.
- #14: You will need to determine the following things: The location of the Temporary Working Folder The format you want the files exported in (PDF or TIF) Whether or not to include annotations when the documents are exported The Output Folder Structure
- #15: Users will need to choose whether to use a Network Path or an FTP location to transfer exported files
- #16: If Sequential mode is selected, you will need to determine how often and at what time the query will run.
- #17: If Varied Mode is selected, users will then have to give values that ILINX Export will search on, based on the Predefined Saved Search the user selects.The results of the search will appear in the Oracle IPM Search Results window.
- #18: The Export Settings screen summarizes all the settings the users has determined
- #19: For those users who want to configure the application, they can use the exposed code or SDK at the API level.This trigger is another program