Contact us for more information

Request a QuoteEnterprise BatchLoader


Use Cases
ERP integrations: JD Edwards and PeopleSoft
  • Sales report distribution
  • Profit/loss statements
CAD integrations
  • Drawings to PDF
Large volume content migrations
  • File share to WebCenter
  • Third-party ECM to WebCenter
Document imaging
  • Hard copy conversion (TIFF to PDF) for documents requiring wet signatures

Configuration Steps

1. Install onto Oracle Content Server (content repository for Oracle WebCenter Content)
2. Configure the watch directory, where business applications output text or XML files and Word or PDF documents, for example
3. Start Enterprise BatchLoader as a service or by using the start-up script

Additional Resources

Contact Us to Learn More
Contact us to learn more, schedule a demo, or request a quote.

Enterprise Batchloader Product Box

As organizations strive to more effectively manage their enterprise content, they are turning to Oracle WebCenter Content systems and creating enterprise information repositories. However, the persisting problem facing organizations is how to quickly and efficiently load content into the system and provide a single repository for searching, accessing, editing, and sharing enterprise content. Organizations can solve the problem with Fishbowl Solutions' Enterprise BatchLoader product.

Enterprise BatchLoader is a robust software application that integrates enterprise business systems with Oracle WebCenter Content by consolidating the content that exists within those systems. It ensures content generated by ERP, CRM, CAD and 3rd-party file shares gets checked in to Oracle WebCenter, providing a single access point to high-value information. Enterprise BatchLoader is a standalone application requiring minimal configuration steps.

Comparative Analysis


Oracle Batch Loader

Web-based Batch Loader

Enterprise BatchLoader

Easily load thousands of documents




Batch-loaded files enter workflow



Can run on an external server




Watches a folder for items to check in



User interface to specify metadata


















Enterprise BatchLoader's pre-processor component can be further configured for direct integrations with such systems as Oracle's JD Edwards and PeopleSoft applications. With these direct integrations, Enterprise BatchLoader not only monitors the directories for data output by these systems, but it also maps the data to fields existing in Oracle WebCenter Content.



Frequently Asked Questions

Is Enterprise BatchLoader an Oracle WebCenter Content component, or is it something that sits outside Oracle WebCenter Content, but connects to it?
Enterprise BatchLoader is both. It has an Oracle WebCenter Content component that enables some of its functionality, but it's an external application that can run either on the Content Server machine or a completely separate machine. Enterprise BatchLoader will connect to the Content Server to check in, update, or delete content.

Does Enterprise BatchLoader have a user interface?
Enterprise BatchLoader does not have a user interface because it is typically used when integrating two systems and runs in the background. It can watch a network folder and automatically check in content that appears in that folder.

Does Enterprise BatchLoader use a script like the Oracle WebCenter batch loader, or does it have its own format?
Enterprise BatchLoader is very flexible with the types of input it can handle because you can customize the pre-processor yourself. For example, we have created pre-processors that get their data from a database, XML file, text file, folder structure, etc. The default input format for metadata is a text file that is very similar to the Oracle WebCenter Content batch loader format.

Enterprise Batchloader Architecture graphic

A third party system will output a .xml, .txt, and .bif file and put these files in a directory on the server that is watched by the pre-processor. The pre-processor is customizable for each customer and typically reads the contents of the file found in the watch directory. It will then parse that file to create a .bif file containing the information that Oracle needs to perform the check in, update, delete, etc. The Enterprise Batch Loader is then invoked to read the .bif file and take the appropriate action specified by the pre-processor. Typically this means it will take the metadata specified in the .bif file and check the native file designated into Oracle.

4500 Park Glen Road Suite 200, Minneapolis, MN 55416 | (952) 465-3400 © 2015 Fishbowl Solutions. All rights Reserved.