Technical info and insight on using Oracle Documaker for customer communication and document automation

  • ODEE
    June 12, 2014

ODEE Green Field (Windows) Part 5 - Deployment and Validation

Andy Little
Technical Director

And here we are, almost finished with our installation of Oracle Documaker Enterprise Edition ("ODEE") in a Windows green field environment. Let's recap what we've done so far:

  1. In part 1, I went over the basic process that I intended to show with installing an ODEE on a green field server. I walked you through the basic installation of Oracle 11g database
  2. In part 2, I covered the installation of WebLogic application server.
  3. In part 3, I showed you how to install SOA Suite for WebLogic.
  4. In part 4, we did the first part of the installation of ODEE itself.
What remains after all of that, is the deployment of the ODEE components onto the database and application server - so let's get to it!


First, we'll deploy the schemas to the database. The schemas are created during the ODEE installation according to the responses provided during the install process. To deploy the schemas, you'll need to login to the database server in your green field environment.

Open a command line and CD into ODEE_HOME\documaker\database\oracle11g.
Run SQLPLUS as SYSDBA and execute dmkr_admin.sql: 
 sqlplus / as sysdba @dmkr_admin.sql

Execute dmkr_asline.sql, dmkr_admin_correspondence_example.sql

If you require additional languages, run the appropriate SQL scripts (e.g. dmkr_asline_es.sql for Spanish).


Next, we'll deploy the WebLogic domain and it's components - Documaker web services, Documaker Interactive, Documaker dashboard, and more. To deploy the components, you'll need to login to the application server in your green field environment.

1. Open Windows Explorer and navigate to ODEE_HOME\documaker\j2ee\weblogic\oracle11g\scripts.
2. Using a text editor such as Notepad++, modify weblogic_installation_properties and set location of MIDDLEWARE_HOME and ODEE HOME. If you have used the defaults you’ll probably need to change the E: to C: and that’s it. Save the changes.
3. Continuing in the same directory, use your text editor to modify set_middleware_env.cmd and set the drive and path to MIDDLEWARE_HOME. If you have used the defaults you’ll probably need to just change E: to C: and that’s it. Save the changes.
4. In the same directory, execute wls_create_domain.cmd by double-clicking it. This should run to completion. If it does not, review any errors and correct them, and rerun the script.
5. In the same directory, execute wls_add_correspondence.cmd by double-clicking it - again this should run to completion. 
6. Next, we'll start the AdminServer - this is the main WebLogic domain server. To start it, use Windows Explorer and navigate to MIDDLEWARE_HOME\user_projects\domains\idocumaker_domain. Double-click startWebLogic.cmd and the server startup will begin. Once you see output that indicates that the server status changed to RUNNING you may proceed. 
a. Note: if you saw database connection errors, you probably didn’t make sure your database name and connection type match. You can change this manually in the WebLogic Console. Open a browser and navigate to http://localhost:7001/console (replace localhost with the name of your application server host if you aren't opening the browser on the server), and login with the the weblogic credential you provided in the ODEE installation process.
b. Once you're logged in, open Services→Data Sources. Select dmkr_admin and click Connection Pool. 
c. The end of the URL should match the connection type you chose. If you chose ServiceName, the URL should be:
jdbc:oracle:thin:@//<hostname>:1521/<serviceName> and if you chose SID, the URL should be:
d. An example serviceName is a fully qualified DNS-style name, e.g. "idmaker.us.oracle.com". (It does not need to actually resolve in DNS). An example SID is just a name, e.g. IDMAKER.
e. Save the change and repeat for the data source dmkr_asline. 
f. You will also need to make the same changes in the ODEE_HOME/documaker/docfactory/config/context/.bindings file - open the file in a text editor, locate the URL lines and make the appropriate change, then save the file. 
7. Back in the ODEE_HOME\documaker\j2ee\weblogic\oracle11g\scripts directory, execute create_users_groups.cmd
8. In the same directory, execute create_users_groups_correspondence_example.cmd
9. Open a browser and navigate to http://localhost:7001/jpsquery. Replace localhost with the name of your application server host if you aren't running the browser on the application server. If you changed the default port for the AdminServer from 7001, use the port you changed it to. You should see output like this:

10. Start the WebLogic managed servers by opening a command prompt and navigating to MIDDLEWARE_HOME/user_projects/domains/idocumaker_domain/bin/. When you start the servers listed below, you will be prompted to enter the WebLogic credentials to start the server. You can prevent this by providing the credential in the startManagedwebLogic.cmd file for the WLS_USER and WLS_PASS values. Note that the credential will be stored in cleartext. To start the server, type in the command shown.
a. Start the JMS Server: ./startManagedWebLogic.cmd jms_server
b. Start Dashboard/Documaker Administrator: ./startManagedWebLogic.cmd dmkr_server
c. Start Documaker Interactive for Correspondence: ./startManagedWebLogic.cmd idm_server

SOA Composites

 If you're planning on testing out the approval process components of BPEL that can be used with Documaker Interactive, then use the following steps to deploy the SOA composites. If you're not going to use BPEL, you can skip to the next section.

1. Stop the servers listed in the previous section (Step 10) in the reverse order that they were started.
2. Run the Domain configuration command: navigate to and execute MIDDLEWARE_HOME/wlserver_10.3/common/bin/config.cmd.
3. Select Extend and click next.

4. Select the iDocumaker Domain and click Next.

5. Select the Oracle SOA Suite – (this may automatically select other components which is OK). Click Next.

6. View the Configure JDBC resources screen. You should not make any changes. Click Next.

7. Check both connections and click Test Connections. After successful test, click Next. If the tests fail, something is broken. Go back to configure JDBC resources and check your service name/SID.

8. Check all schemas. Set a password (will be the same for all schemas). Enter the database information (service name, host name, port). Click Next.

9. Connections should test successfully. If not, go back and fix any errors. Click Next.

10. Click Next to pass through Optional Configuration.

11. Click Extend.

12. Click Done.

13. Open a terminal window and navigate to/execute: ODEE_HOME/documaker/j2ee/weblogic/oracle11g/bpel/antbuild.cmd
14. Start the WebLogic Servers – AdminServer, jms_server, dmkr_server, idm_server. If you forgot how to do this, see the previous section Step 10.

Note: if you previously changed the startManagedWebLogic.cmd script for WLS_USER and WLS_PASS you will need to make those changes again.

15. Start the WebLogic server soa_server1: MIDDLEWARE_HOME/user_projects/domains/idocumaker_domain/bin/startManagedWebLogic.cmd soa_server1
16. Open a browser to http://localhost:7001/console and login. 
17. Navigate to Services→Data Sources and select DMKR_ASLINE. 
18. Click the Targets tab. Check soa_server1, then click Save. Repeat for the DMKR_ADMIN data source.

19. Open a command prompt and navigate to ODEE_HOME/j2ee/weblogic/oracle11g/scripts, then execute deploy_soa.cmd. That's it! (As if that wasn't enough?)


  1. Deploy the sample MRL resources by navigating to/executing ODEE_HOME/documaker/mstrres/dmres/deploysamplemrl.bat. You should see approximately 500 resources deployed into the database.
  2. Start the Factory Services. Start→Run→services.msc. Locate the service named "ODDF xxxx" and right-click, select Start. Note that each Assembly Line has a separate Factory setup, including its own Factory service and Docupresentment service. The services are named for the assembly line and the machine on which they are installed (because you could have multiple machines servicing a single assembly line, so this allows for easy scripting to control all the services if you choose to do so.

  3. Repeat for the Docupresentment service. Note that each Assembly Line has a separate Docupresentment.
  4. Using Windows Explorer, navigate to ODEE_HOME/documaker/mstrres/dmres/input and select one of the XML files, and copy it into ODEE_HOME/documaker/hotdirectory. Note: if you chose a different hot directory during installation, copy the file there instead. Momentarily you should see the XML file disappear!
  5. Open browser and navigate to http://localhost:10001/DocumakerDashboard (previous versions 12.0-12.2 use http://localhost:10001/dashboard) and verify that job processed successfully. Note that some transactions may fail if you do not have a properly configured email server, and this is ok. You can set up a simple SMTP server (just search the internet for "SMTP developer" and you'll get several to choose from.

 So... that's it? Where are we at this point? You now have a completely functional ODEE installation, from soup to nuts as they say. You can further expand your installation by doing some of the following activities:

  • clustering WebLogic services
  • configuring WebLogic for redundancy
  • configuring Oracle 11g for RAC
  • adding additional Factory servers for redundancy/processing capacity
  • setting up a real MRL (instead of the sample resources)
  • testing Documaker Web Services for job submission
  • and more! 

I certainly hope you've enjoyed this and find it useful. If you find yourself running into trouble, visit the Oracle Community for Documaker - there is plenty of activity there and you can ask questions. For more concentrated assistance, you can engage an Oracle consultant who is a subject matter expert to assist you. Feel free to email me [andy (dot) little (at) oracle (dot) com] and I can connect you with the appropriate resource to get started. Best of luck!


Join the discussion

Comments ( 2 )
  • Kevin Landin Monday, June 20, 2016


    There is a difference between the following steps and the Installation Guide:

    17. Navigate to Services→Data Sources and select DMKR_ASLINE.

    18. Click the Targets tab. Check soa_server1, then click Save. Repeat for the DMKR_ADMIN data source.

    The Installation Guide only mentions setting soa_server1 as a Target for DMKR_ADMIN. It does not mention setting it for DMKR_ASLINE.

    Thank you!

  • Andy Tuesday, June 21, 2016

    You're right! I'm not sure why I did that... anyway, it won't hurt anything to include both as targets; it will just make that data source available to that functions in the SOA Suite. The main thing is the ensure you at least target DMKR_ADMIN for soa_Server1.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.