Oracle® Business Intelligence Discoverer EUL Command Line For Java

Oracle Business Intelligence Discoverer EUL Command Line for Java
Users Guide 10g Release 2 (10.1.2.0.0)

Part No. B13919-02
November 2004
Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide, 10g Release 2 (10.1.2.0.0) Part No. B13919-02 Copyright 2004 Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065 The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Perspective for Java licensed from Three D Graphics, Inc. Copyright 1997, 2002, Three D Graphics, Inc.
Contents
Send Us Your Comments ....................................................................................................................... vii Preface ................................................................................................................................................................. ix
Documentation Accessibility ..................................................................................................................... Intended Audience...................................................................................................................................... Conventions ................................................................................................................................................. Related Documents ..................................................................................................................................... JGoodies License Agreement..................................................................................................................... ix ix x x x
1 Introducing the Oracle Business Intelligence Discoverer EUL Command Line for Java
What is the OracleBI Discoverer EUL Command Line for Java? .................................................... What are the differences between the OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Command Line for Java? ........................................................... What is a Discoverer EUL Command Line for Java command? ...................................................... What is a Discoverer EUL Command Line for Java command modifier? ..................................... What privileges do you require to use the Discoverer EUL Command Line for Java? .............. About running the Discoverer EUL Command Line for Java (Linux, Solaris and HP-UX only) .............................................................................................................................................. How to run a Discoverer EUL Command Line for Java command ................................................. How to type commands directly at a command prompt ............................................................. How to run commands stored in a command file......................................................................... About troubleshooting the Discoverer EUL Command Line for Java ........................................... About using wildcards to identify EUL objects ................................................................................. Examples of commands ........................................................................................................................... What is a command file? ......................................................................................................................... Examples of command files.................................................................................................................... List of Discoverer EUL Command Line for Java commands ........................................................... 1-1 1-2 1-3 1-3 1-3 1-4 1-4 1-5 1-5 1-5 1-6 1-7 1-7 1-8 1-8
Discoverer EUL Command Line for Java Reference

What command syntax conventions does this guide use? ............................................................... What is the syntax for commands?........................................................................................................ Rules for using the Discoverer EUL Command Line for Java ......................................................... Setting OracleBI Discoverer Registry Variables for Use by OracleBI Discoverer EUL Command Line for Java Commands..................................................................................................... 2-1 2-2 2-3 2-3
iii
Discoverer EUL Command Line for Java command reference ........................................................ 2-4 -asm ...................................................................................................................................................... 2-4 -cmdfile ............................................................................................................................................... 2-5 -connect ............................................................................................................................................... 2-5 -create_eul .......................................................................................................................................... 2-6 -delete .................................................................................................................................................. 2-7 -delete_eul ........................................................................................................................................... 2-8 -export.................................................................................................................................................. 2-9 -grant_privilege ............................................................................................................................... 2-10 -help .................................................................................................................................................. 2-11 -import .............................................................................................................................................. 2-12 -load................................................................................................................................................... 2-13 -refresh_business_area .................................................................................................................. 2-14 -refresh_folder ................................................................................................................................ 2-15 -refresh_summary ........................................................................................................................... 2-15 -revoke_privilege ............................................................................................................................ 2-16 Discoverer EUL Command Line for Java command modifier reference .................................... 2-16 -aggregate ......................................................................................................................................... 2-16 -all ...................................................................................................................................................... 2-17 -apps_fndnam ................................................................................................................................. 2-17 -apps_fndnam_password .............................................................................................................. 2-17 -apps_gwyuid ................................................................................................................................. 2-17 -apps_grant_details......................................................................................................................... 2-18 -apps_mode...................................................................................................................................... 2-18 -apps_responsibility........................................................................................................................ 2-18 -apps_security_group ..................................................................................................................... 2-18 -apps_user ....................................................................................................................................... 2-19 -asm_policy ...................................................................................................................................... 2-19 -asm_space, -asm_tablespace ........................................................................................................ 2-19 -audit_info ........................................................................................................................................ 2-19 -auto_gen_name .............................................................................................................................. 2-20 -auto_refresh .................................................................................................................................... 2-20 -auto_summaries ............................................................................................................................. 2-20 -auto_upgrade ................................................................................................................................. 2-21 -ba_link ............................................................................................................................................. 2-21 -business_area.................................................................................................................................. 2-21 -business_area_access..................................................................................................................... 2-21 -business_area_admin_access ....................................................................................................... 2-22 -business_area_and_contents ........................................................................................................ 2-22 -capitalize ......................................................................................................................................... 2-22 -character_set_encoding................................................................................................................. 2-22 -condition ......................................................................................................................................... 2-23 -date_hierarchy................................................................................................................................ 2-23 -db_link............................................................................................................................................. 2-23 -default_tablespace ......................................................................................................................... 2-23 -description ...................................................................................................................................... 2-23 -eul..................................................................................................................................................... 2-24
iv
-eul_language................................................................................................................................... -external_element ............................................................................................................................ -folder................................................................................................................................................ -function............................................................................................................................................ -hier_node ........................................................................................................................................ -hierarchy ......................................................................................................................................... -identifier .......................................................................................................................................... -import_rename_mode................................................................................................................... -item .................................................................................................................................................. -item_class ........................................................................................................................................ -join.................................................................................................................................................... -keep_format_properties................................................................................................................ -log..................................................................................................................................................... -log_only........................................................................................................................................... -lov..................................................................................................................................................... -overwrite ......................................................................................................................................... -password ......................................................................................................................................... -preserve_workbook_owner.......................................................................................................... -private.............................................................................................................................................. -privilege........................................................................................................................................... -remove_prefix ................................................................................................................................ -replace_blanks ................................................................................................................................ -role ................................................................................................................................................... -schema ............................................................................................................................................. -set_created_by ................................................................................................................................ -set_created_date............................................................................................................................. -set_updated_by .............................................................................................................................. -set_updated_date........................................................................................................................... -sort_folders ..................................................................................................................................... -sort_items ........................................................................................................................................ -source............................................................................................................................................... -summary ......................................................................................................................................... -temporary_tablespace ................................................................................................................... -user................................................................................................................................................... -wildcard .......................................................................................................................................... -workbook ........................................................................................................................................ -workbook_access ........................................................................................................................... -xml_workbooks..............................................................................................................................
2-24 2-24 2-25 2-25 2-25 2-25 2-26 2-26 2-26 2-27 2-27 2-27 2-27 2-28 2-28 2-28 2-28 2-29 2-29 2-29 2-31 2-31 2-32 2-32 2-32 2-32 2-33 2-33 2-33 2-33 2-33 2-34 2-34 2-34 2-35 2-35 2-35 2-35
Discoverer EUL Command Line for Java error messages

Discoverer EUL Command Line for Java error messages ................................................................ A-1
Differences in syntax between Discoverer command line interfaces

Differences in syntax between Discoverer command line interfaces ........................................... B-1
Index
vi
Send Us Your Comments

Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide, 10g Release 2 (10.1.2.0.0)
Part No. B13919-02
Oracle welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.

Did you find any errors? Is the information clearly presented? Do you need more information? If so, where? Are the examples correct? Do you need more examples? What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the title and part number of the documentation and the chapter, section, and page number (if available). You can send comments to us in the following ways:

Electronic mail: [email protected] FAX: 650 506 7421 Attn: OracleBI Discoverer Postal service: Oracle Corporation OracleBI Discoverer Documentation 200 Oracle Parkway, 2OP9 Redwood Shores, CA 94065 USA
If you would like a reply, please give your name, address, telephone number, and electronic mail address (optional). If you have problems with the software, please contact your local Oracle Support Services.
vii
viii
Preface
Welcome to the Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide!. This users guide also provides a reference for the Discoverer EUL Command Line for Java. To use this guide effectively, we recommend that you are already familiar with Discoverer EULs. For the latest information, please read the Discoverer Release Notes in conjunction with this guide.
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. 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 additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, 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, JAWS 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.
Intended Audience
This guide is intended for Discoverer administrators, Oracle Applications administrators, and anyone who needs to manage Discoverer EULs. Readers are assumed to have a working knowledge of Discoverer End User Layers (EULs).
ix
Conventions
In this manual:
EUL, the End User Layer, refers to the metadata layer between the database and Discoverer.
For more information about command conventions, see "What command syntax conventions does this guide use?".
Related Documents
For more information, see the following manuals:

Oracle Business Intelligence Discoverer Administration Guide You can access the above documents and other information about Discoverer (e.g. whitepapers, best practices, tutorials) on the Oracle Technology Network at www.oracle.com/technology.
JGoodies License Agreement

Oracle Business Intelligence includes the JGoodies software, whose License Agreement follows: Copyright 2003 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of JGoodies nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1
Introducing the Oracle Business Intelligence Discoverer EUL Command Line for Java
This chapter introduces the OracleBI Discoverer EUL Command Line for Java, and contains the following topics:

"What is the OracleBI Discoverer EUL Command Line for Java?" "What are the differences between the OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Command Line for Java?" "What is a Discoverer EUL Command Line for Java command?" "What is a Discoverer EUL Command Line for Java command modifier?" "What privileges do you require to use the Discoverer EUL Command Line for Java?" "About running the Discoverer EUL Command Line for Java (Linux, Solaris and HP-UX only)" "How to run a Discoverer EUL Command Line for Java command" "About troubleshooting the Discoverer EUL Command Line for Java" "About using wildcards to identify EUL objects" "Examples of commands" "What is a command file?" "Examples of command files" "List of Discoverer EUL Command Line for Java commands"
What is the OracleBI Discoverer EUL Command Line for Java?

The OracleBI Discoverer EUL Command Line for Java is a set of text based commands that enable you to create and manipulate Discoverer EULs. Note: You use Heterogeneous Services to connect to non-Oracle databases, although the EUL is stored in the Oracle database. For more information about using non-Oracle databases, see Oracle Heterogeneous Connectivity Administrator's Guide. The Discoverer EUL Command Line for Java runs in a Java environment, which means that you can run it from any Java-compatible platform (e.g. Windows, UNIX, Linux). For example, you might want to refresh (or patch) an EUL from a UNIX machine. The figure below shows three different ways in which you can manipulate Discoverer EULs:
Introducing the Oracle Business Intelligence Discoverer EUL Command Line for Java 1-1
What are the differences between the OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Com-
using the Discoverer EUL Command Line for Java on either a Windows, UNIX, or Linux machine, as described in this guide using OracleBI Discoverer Administrator on a Windows machine using the OracleBI Discoverer Administrator Command Line Interface on a Windows machine Note: To run the OracleBI Discoverer Administrator Command Line Interface, you must have OracleBI Discoverer Administrator installed on your machine.
Figure 11 Discoverer interfaces to the Discoverer EUL
Notes:

Discoverer EUL files have an EEX extension (e.g. Sales_eul.eex) For a list of Discoverer EUL Command Line for Java commands, see "List of Discoverer EUL Command Line for Java commands".
What are the differences between the OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Command Line for Java?
Much of the Discoverer EUL Command Line for Java is compatible with the OracleBI Administrator Command Line Interface. If you have commands and scripts written for the OracleBI Discoverer Administrator Command Line Interface, you can easily convert them to run on the Discoverer EUL Command Line for Java. The OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Command Line for Java differ as follows:
The Discoverer EUL Command Line for Java runs on multiple platforms. The OracleBI Discoverer Administrator Command Line Interface runs only on Windows. Note: You do not need to have OracleBI Discoverer Administrator installed to run the Discoverer EUL Command Line for Java.
Discoverer EUL Command Line for Java commands are prefixed with java -jar eulbuilder.jar. The Discoverer EUL Command Line for Java contains extra commands (e.g. to grant and revoke database privileges, you can use the commands -grant_privilege and -revoke_privilege commands). Some commands have minor differences in syntax (for more information, see "Differences in syntax between Discoverer command line interfaces").
1-2
Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide
What privileges do you require to use the Discoverer EUL Command Line for Java?
What is a Discoverer EUL Command Line for Java command?

A Discoverer EUL Command Line for Java command is an instruction that manipulates a Discoverer EUL in some way. For example:
the -connect command connects to a database using the username, password, and database specified. For example, to connect to database my_database as user jchan:
java -jar eulbuilder.jar -connect jchan/12345@my_database
The -import command imports EUL objects into the current EUL from a specified Discoverer EUL export file (i.e. a file with an EEX extension). For example, to import EUL objects from the file c:\data\sales.eex:
java -jar eulbuilder.jar -connect jchan/12345@my_database -import c:\data\sales.eex
What is a Discoverer EUL Command Line for Java command modifier?

A Discoverer EUL Command Line for Java command modifier is an instruction that qualifies or refines a command. For example:
The -log command modifier creates a log file to store processing information during the execution of a command. For example, to import EUL objects from the file c:\data\sales.eex and store log data in sales_import_logfile.txt:
java -jar eulbuilder.jar -connect jchan/12345@my_database -import c:\data\sales.eex -log sales_import_logfile.txt
The -item command modifier used in conjunction with the -delete command specifies which EUL item to remove from an EUL. For example, to delete the item sales.profit:
java -jar eulbuilder.jar -connect jchan/12345@my_database -delete -item sales.profit
What privileges do you require to use the Discoverer EUL Command Line for Java?
To use the Discoverer EUL Command Line for Java, the database username that you use to connect to a database must have the following database privileges:

CREATE SESSION CREATE TABLE CREATE VIEW CREATE SEQUENCE CREATE PROCEDURE
The database username also requires a default tablespace, and a quota set on the default tablespace. For more information about granting privileges, see Oracle Business Intelligence Discoverer Administration Guide.
About running the Discoverer EUL Command Line for Java (Linux, Solaris and HP-UX only)
About running the Discoverer EUL Command Line for Java (Linux, Solaris and HP-UX only)
To run the OracleBI Discoverer EUL Command Line for Java on Linux, Solaris, or HP-UX, a number of environment variables must be set correctly. You can either set the environment variables explicitly using the discwb.sh script or implicitly using the eulapi script, as described below:
to explicitly set the environment variables before issuing Discoverer EUL Command Line for Java commands, enter the following at the command line prompt from which you will be issuing those commands:
oracle_home_path/discoverer/discwb.sh
Subsequently, you can enter Discoverer EUL Command Line for Java commands as follows: java -jar oracle_home_path/discoverer/lib/eulbuilder.jar -command_list For example, to refresh a folder called "Sales1", you might enter the following: java -jar oracle_home_path/discoverer/lib/eulbuilder.jar -connect jchan/12345@my_database -refresh_folder Sales1
to implicitly set the environment variables when you run Discoverer EUL Command Line for Java commands, use the eulapi script in the directory oracle_home_path/bin to run commands. For example, to refresh a folder called "Sales1", you might enter the following:
oracle_home_path/bin/eulapi -connect jchan/12345@my_database -refresh_folder Sales1

Hint: To avoid entering oracle_home_path/bin each time you run the eulapi script, run discwb.sh first.
How to run a Discoverer EUL Command Line for Java command

You can run the Discoverer EUL Command Line for Java in two ways:
by entering commands directly at a command prompt (for more information, see "How to type commands directly at a command prompt") by running commands stored in command files (for more information, see "How to run commands stored in a command file")
Notes
OracleBI Administrator Command Line Interface commands are not compatible with Discoverer EUL Command Line for Java commands without amendment (for more information, see "What are the differences between the OracleBI Discoverer Administrator Command Line Interface and the Discoverer EUL Command Line for Java?"). Make sure that the <ORACLE_HOME>/lib directory is registered in the CLASS PATH. To see a list of EUL objects in an EUL, export all EUL objects so that you can inspect it. For example:
java -jar eulbuilder.jar -connect jchan/12345@my_database -export objectlist.xml -all % -wildcard
1-4
About troubleshooting the Discoverer EUL Command Line for Java
How to type commands directly at a command prompt

You might type commands directly at a command prompt when you want to patch an EUL from a UNIX machine. To type a command directly at a command prompt:
1. 2.
Open a command prompt (e.g. a UNIX command prompt). Type a command directly at the command prompt. For example, to refresh folders called Sales1 and Sales2, type the following (see figure below):
java -jar eulbuilder.jar -connect jchan/12345@my_database -refresh_folder Sales1 -refresh_folder Sales2 Figure 12 Using the Discoverer EUL Command Line for Java from a UNIX command prompt
How to run commands stored in a command file

You might run commands stored in a command file when you want to perform a regular EUL update. To run commands stored in a command file:
1. 2. 3.
Create a text file and type the commands into the text file (e.g. import.txt). Open a command prompt (e.g. a UNIX command prompt). Type the -cmdfile command at the command prompt followed by the name of a command file. For example, to run commands stored in import.txt, type the following:
java -jar eulbuilder.jar -connect jchan/12345@my_database -cmdfile import.txt
For more information about command files, see "What is a command file?".
Notes
You can also run more than one command file by repeating the -cmdfile command. For example, to run commands stored in the text file login.txt, then commands in import.txt, type:
java -jar eulbuilder.jar -cmdfile c:\scripts\login.txt -cmdfile c:\scripts\import.txt
About troubleshooting the Discoverer EUL Command Line for Java

The Discoverer EUL Command Line for Java provides a log facility. Use the log facility to test commands without changing data (i.e. for impact analysis) and troubleshoot problems as follows:
About using wildcards to identify EUL objects
Testing commands without changing data. To test commands without changing data, use the -log <log file name> -log_only modifiers. For example:
-log <log file name> -log_only
These modifiers produce a log file showing whether problems occurred during command execution without changing the data. For more information, see "-log_only".
Troubleshooting problems. To troubleshoot problems, use the -log <log file name> modifier to store command processing information. For example, after running a command you will see a 'Command completed' message, which means that Discoverer processing is complete. To verify that the operation was carried out successfully, check the log file created using the -log modifier. For example, if you attempt to delete a folder called 'Store 4' that is used in a summary folder, you will see the 'Command completed' message on screen. However, you will find details in the log file specifying why the command could not be executed, similar to the following:
java EulCommandLine -connect jchan/12345@my_database -delete -folder Store 4 -log Started <date and time>... Deleting folder Store 4... Element Store 4 cannot be deleted because it is used in a summary Completed <date and time>.
About using wildcards to identify EUL objects

When you use the Discoverer EUL Command Line for Java, you can use wildcards to specify groups of EUL objects that you want to manipulate. Wildcards are special characters that you use to substitute other characters. For example, you might want to import OLAP functions with names that begin with 'BI_'. There are two wildcards that you can use:

a percent sign (%) matches zero (i.e. none) or more characters an underscore (_) matches exactly one character
You can use wildcards when you:

delete EUL objects export EUL objects import EUL objects refresh folders, business areas, and summary folders grant and revoke privileges for workbooks and business areas
You can use wildcards with item names or identifiers. When you use wildcards, you append the command with the -wildcard modifier (for more information, see "-wildcard").
How to identify EUL objects using the percent wildcard:

1.
Use the percent sign (%) followed by the -wildcard modifier. For example, to delete all business areas with display names that begin with 'A':
1-6
What is a command file?
java -jar eulbuilder.jar -connect jchan/12345@my_database -delete -business_area A% -wildcard
How to identify EUL objects using the underscore wildcard:

1.
Use the underscore (_) followed by the -wildcard modifier. For example, to delete all business areas with an identifier 'A', followed by any character, followed by 'C':
java -jar eulbuilder.jar -connect jchan/12345@my_database -delete -business_area A_C -identifier -wildcard
Notes:
You can combine percent wildcard characters with underscore wildcard characters. If you omit the -wildcard modifier, the percent sign (%) or underscore (_) characters are interpreted as literal characters. In other words, the command '-delete -business_area A%' attempts to delete a business area called 'A%'.
Examples of commands
Example 1
To delete the Sales folder and Sum1 summary from the Sales EUL, use the following command:
java -jar eulbuilder.jar -connect jchan/12345@my_database -delete -folder Sales -summary Sum1 -eul Sales
Example 2
To refresh the Sales1 and Sales2 folders, use the following command:
java -jar eulbuilder.jar -connect jchan/12345@my_database -refresh_folder Sales1 -refresh_folder Sales2
Example 3
To create an Applications Mode EUL in the database under user jchan and grant access using the Applications username and password apps/apps, use the following command:
java -jar eulbuilder.jar -connect eul_owner:appsresp/appspwd -create_eul -apps_ mode -apps_grant_details apps/apps -user jchan -password 123456
Notes:
You can find more examples in "Discoverer EUL Command Line for Java Reference".
What is a command file?

Command files are text files that contain one or more Discoverer EUL Command Line for Java commands. You use command files to run commands automatically without having to type them manually at a command prompt. If you are familiar with MS-DOS or UNIX, command files work in a similar way to MS-DOS batch files and UNIX script files.
Examples of command files
Notes:
The commands in a command file are treated as though they were entered directly at the command prompt. Carriage returns embedded in a command file are ignored. A command file can in turn invoke other command files.
Examples of command files

Three example command files are described below:
1. 2. 3.
connect.txt contains '-connect jchan/12345@my_database' create.txt contains '-create_eul -log create.log' delete.txt contains '-delete_eul -log delete.log'
You can use these command files in different combinations as shown in the following examples:
Example 1
To connect to a database:
java -jar eulbuilder.jar -cmdfile connect.txt
Example 2
To connect to a database, create an EUL, and store processing information in a log file:
java -jar eulbuilder.jar -cmdfile connect.txt -cmdfile create.txt
Example 3
To connect to a database, delete an EUL, and store processing information in a log file:
java -jar eulbuilder.jar -cmdfile connect.txt -cmdfile delete.txt
List of Discoverer EUL Command Line for Java commands

The table below lists the Discoverer EUL Command Line for Java commands
Command: -asm <modifiers> -cmdfile <command file> -connect <username>/<password> [@<database] -create_eul <modifiers> -delete <modifiers> -delete_eul <modifiers> -export <export file> <modifiers> -grant_privilege <modifiers> -help [command name(s)] [-all] -import <import file(s)> <modifiers> Use to: Automate summary management ASM Run commands stored in a command file Connect to an EUL Create an EUL Delete an EUL object Delete an EUL Export EUL object Grant Discoverer privileges to a database user Display online help Import EUL objects
1-8
Command: -load <business area> <modifiers> -refresh_business_area <business area(s)> <modifiers> -refresh_folder <folder name(s)> <modifiers> -refresh_summary <summary name(s)> <modifiers> -revoke_privilege <modifiers>
Use to: Load a business area Refresh a business area Refresh a folder Refresh a summary folder Remove Discoverer privileges from a database user
Note: Detailed information about command modifiers is contained in the command reference section (for more information, see "Discoverer EUL Command Line for Java Reference").
1-10
2
This chapter provides detailed reference information for the Discoverer EUL Command Line for Java, and contains the following topics:

"What command syntax conventions does this guide use?" "What is the syntax for commands?" "Rules for using the Discoverer EUL Command Line for Java" "Setting OracleBI Discoverer Registry Variables for Use by OracleBI Discoverer EUL Command Line for Java Commands" "Discoverer EUL Command Line for Java command reference" "Discoverer EUL Command Line for Java command modifier reference"
What command syntax conventions does this guide use?

This guide uses the following command syntax conventions:
Commands and command modifiers are shown in plain type and are prefixed with a dash (-). Hint: Do type the dash.
Mandatory command arguments and command modifiers are enclosed in angle brackets < >. Hint: Do not type the angle brackets.
Optional command arguments and command modifiers are enclosed in square brackets []. Hint: Do not type the square brackets.
Variable command arguments (i.e. where you supply the value) are shown in italics. Where options are separated by a pipe character (i.e. |), choose one from the list. For example, 'source <server | gateway>' means type either 'source server' or 'source gateway'. Note: Do not type the pipe character.
2-1
What is the syntax for commands?
Figure 21 Command conventions used in this guide
Key to figure:
1. 2. 3. 4. 5.
Discoverer EUL Command Line for Java executable file. Command. Variable command arguments (mandatory), where you supply the user name and password separated by a forward slash (/) character. Optional command argument, where you supply the database name. Optional command modifier.
What is the syntax for commands?

Use the following syntax for Discoverer EUL Command Line for Java commands:
java -jar eulbuilder.jar -connect <username>/<password>[@database] <-command> [-argument(s)] [-modifiers] [-argument(s)]
Note: Before you can run Discoverer EUL Command Line for Java commands, you must set up the Discoverer environment. For more information, see "About running the Discoverer EUL Command Line for Java (Linux, Solaris and HP-UX only)".
Notes:
Commands and modifiers are not case-sensitive. In other words, you can use either upper-case or lower-case characters interchangeably. Variable command arguments can be case-sensitive. For example, EUL names and tablespace names. In other words, an EUL called VIDEO5 must be specified as 'VIDEO5', not 'Video5' or 'video5'. Commands can appear in any order as long as their arguments immediately follow them in the correct order. Command modifiers can appear in any order as long as their arguments immediately follow them in the correct order. You must type commands in a single line with no line breaks or carriage returns. When you want to perform an operation on more than one EUL object, repeat the optional command modifier for each EUL object. For example, to refresh the Sales1 and Sales2 folders, you repeat the -refresh_ folder command, as follows:
java -jar eulbuilder.jar -connect jchan/12345@my_database -refresh_folder Sales1 -refresh_folder Sales2
When specifying an item name or identifier that contain spaces or special characters, enclose it in double quotes (""). For example, if a folder is called Video Analysis Information, specify the folder name as "Video Analysis Information". If you include connection details in a command file (e.g. -connect username/password@database), you do not need to include the -connect command after the java -jar eulbuilder.jar section. In other words, if you store
2-2
Setting OracleBI Discoverer Registry Variables for Use by OracleBI Discoverer EUL Command Line for Java Commands
connection details in connect.txt, you might use the following command to connect to a database:
java -jar eulbuilder.jar -cmdfile connect.txt
Rules for using the Discoverer EUL Command Line for Java
When using the Discoverer EUL Command Line for Java, the following rules apply:
If you omit the optional <database> argument when you specify connection information, you connect to the Oracle database installed on your machine. Use the optional <database> argument if you have more than one database installed on your machine, or if you are connecting to a database on a different machine. If you do not specify an object name where one is required, Discoverer uses the default object for that database username. For example, if you do not specify an EUL using the -eul modifier, Discoverer uses the default EUL for the current database username. For more information about specifying an EUL, see "-eul". You can use nearly all commands with both Oracle or non-Oracle databases. There is one exception, the -refresh_summary command. You can only use the -refresh_ summary command with Oracle databases (for more information, see "-refresh_ summary"). When specifying Discoverer EUL objects, you can use either item names (e.g. folder names) or identifiers (i.e. unique IDs assigned to EUL objects). For example, if a Discoverer folder is called Sales, and its identifier is SALES_132388, you can specify this folder as an argument to the -refresh_folder command in either of the following ways:

-refresh_folder Sales -refresh_folder SALES_132388 -identifier
Hint: Where possible, use identifiers rather than item names to specify EUL objects. Using identifiers avoids translation issues and EUL update problems caused by names being changed arbitrarily (for more information, see -identifier). For more information about Discoverer identifiers, see Oracle Business Intelligence Discoverer Administration Guide.
To access a remote database, you must have the Transparent Network Substrate (TNS) settings for that database stored in the tnsnames.ora file. For more information about TNS settings, see Oracle Enterprise Manager Administrators Guide.
Setting OracleBI Discoverer Registry Variables for Use by OracleBI Discoverer EUL Command Line for Java Commands
When using some of the commands provided by the OracleBI Discoverer EUL Command Line for Java, you might want to explicitly set certain Discoverer registry variables, as shown below:
Command -export Discoverer Registry Variable

ArchiveCacheFlushInterval FormatXMLExportJoinFromMaster
2-3
Discoverer EUL Command Line for Java command reference
Command refresh_object
Discoverer Registry Variable

DefaultPreserveDisplayPropertyForRefresh EnableTriggers FormatXML AppsFNDNAM AppsGWYUID SetNULLItemHeadingOnBulkLoad MaxNumberJoinPredicates SqlTrace
-import -connect -apps_user
-load
all commands
On Windows platforms, Discoverer registry variables are stored in the Windows Registry. On Linux, Solaris, and HP-UX platforms, Discoverer registry variables are stored in the .reg_key.dc file. To set these Discoverer registry variables, do the following:
Specify values for registry variables as required by entering the following at a command prompt: dis51pr -setadminpref registry_variable_name value For example, before using the -import -refresh option, you might want to set the DefaultPreserveDisplayPropertyForRefresh value to 1 by entering the following command:
dis51pr -setadminpref DefaultPreserveDisplayPropertyForRefresh=1

For more information about Discoverer registry variables (including descriptions, default values and allowable values), see Oracle Business Intelligence Discoverer Administration Guide.

This section contains detailed reference information about each command in the Discoverer EUL Command Line for Java. Note the following:

commands are listed in alphabetical order you can refine commands using command modifiers (for more information, see "Discoverer EUL Command Line for Java command modifier reference")
-asm
Use this command to manage Discoverers Automated Summary Management facility (ASM).
Information Syntax: Details -asm -asm_space <bytes> [modifiers]| -asm_space <bytes> -asm_tablespace <tablespace name> [modifiers] -asm_space, -asm_tablespace -log <log file name> [-log_only]
Modifiers:
2-4
Information Notes:
Details If -asm_space, -asm_tablespace modifiers are not specified, the ASM policy tablespace and space will be used. java -jar eulbuilder.jar -connect jchan/12345@my_ database -asm -asm_space 2182 -asm_tablespace user_data
Examples:
Note: For more information about Automated Summary Management in Discoverer, see Oracle Business Intelligence Discoverer Administration Guide.
-cmdfile
Use this command to automatically run Discoverer EUL Command Line for Java commands stored in a text file.
Information Syntax: Modifiers: Notes: Details -cmdfile <command file> [modifiers] -character_set_encoding <character set> To create a command file, create a text file containing one or more Discoverer EUL Command Line for Java commands using a standard text editor. To run the command(s) in the text file, type the following at the command prompt: java -jar eulbuilder.jar -cmdfile <command file> If you omit a directory path when you specify <command file>, the default Discoverer EUL Command Line for Java directory is used. For more information, see "What is a command file?". Examples: Example 1: To run command(s) stored in the text file refresh.txt, type the following at the command prompt: java -jar eulbuilder.jar -connect jchan/12345@my_ database -cmdfile c:\scripts\refresh.txt
-connect
This command enables you to specify a database username and password, and to connect to an EUL.
Information Syntax: Modifiers: Details -connect <username>/<password>[@database][modifiers] -apps_fndnam <foundation name> -apps_fndnam_password <foundation name password> -apps_gwyuid <gateway user ID> -apps_responsibility <responsibility> -apps_security_group <security group> -apps_user -auto_upgrade -eul <EUL> -log <log file name> [-log_only]
2-5
Information Notes:
Details The database that you specify using <database> must either:

be included in the tnsnames.ora file on the machine include the full database details (e.g. address, protocol, port, SID) in the <database> string For example (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = hostname.organization.com)(PORT = 1523))) (CONNECT_ DATA = (SID = VIS)))
If no database is specified, Discoverer uses the default database for the specified username. Examples: Example 1: A typical Oracle Applications connection, specifying an Oracle Applications username and password: java -jar eulbuilder.jar connect sysapps/sysapps@apps_ db apps_user apps apps_responsibility sysresp1 UK -eul AppsEUL Example 2: A new Oracle Applications connection specifying a Oracle Applications username and FNDNAM password: java -jar eulbuilder.jar -connect sysapps/sysapps@apps_ db -apps_user -apps_responsibility sysresp1 -fndnam_ password APPS -eul AppsEUL Example 3: A non-Oracle Applications connection: java -jar eulbuilder.jar connect jchan/12345@my_ database -eul eultest
-create_eul
Use this command to create a Discoverer EUL. Note: To create an Oracle Applications Mode EUL, use the -apps_mode modifier.
Information Syntax: Modifiers: Details -create_eul [modifiers] -apps_grant_details <fnd user/password> -apps_mode [-apps_grant_details] -default_tablespace <default tablespace name> -eul_language <EUL language> -log <log file name> [-log_only] -overwrite -password <password> -private -temporary_tablespace <tablespace name> -user <username>
2-6
Information Notes:
Details Use the -user command modifier to specify the username that will own the new EUL. If you do not specify a username, the currently connected username becomes the owner of the new EUL. Use the -overwrite command modifier to overwrite any existing EUL owned by the intended owner of the new EUL. Use the -private command modifier to specify that the new EUL is private. The default setting for the new EUL is 'public'.
Examples:
Example 1: To create a private EUL for a user named 'Bob', whose password is 'welcome', overwriting any existing EUL and recording all log entries in a file named create.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -create_eul -overwrite -user bob -password welcome -private -log create.log Example 2: To create an Oracle Applications Mode EUL, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -create_eul -apps_mode -apps_grant_details apps/apps Example 3: To create an EUL and specify tablespace details to store EUL tables: java -jar eulbuilder.jar connect jchan/12345@my_ database -create_eul user bob password 3728372 default_tablespace usr temporary_tablespace temp
-delete
Use this command to remove EUL objects from an EUL. Note: To remove an entire EUL, use the -delete_eul command.
Information Syntax: Details -delete <modifiers>
2-7
Information Modifiers:
Details -asm_policy <ASM policy> -business_area <business area> -business_area_and_contents <business area> -ba_link <business area>.<folder> -condition <folder>.<condition> -folder <folder> -function <PL/SQL function> -hierarchy < hierarchy> -hier_node <hierarchy>.<hierarchy node> -identifier -item <folder>.<item> -item_class <item class> -join <join name> -log <log file name> [-log_only] -summary <summary> -wildcard -workbook <workbook>
Notes: Examples:
You can delete one or more EUL objects at a time (see examples below). Example 1: To delete two business areas named Test BA and Final BA from an EUL named eul51, and write to a log file named delba.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -business_area "Test BA" -business_ area "Final BA" -eul eul51 -log delba.log Example 2: To delete a folder named Sales, and a Summary named Sum1 from an EUL named eul51, and write to a log file named del.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -folder Sales -summary Sum1 -eul eul51 -log del.log Example 3: To delete three items from an EUL. You store the identifiers of the items you want to delete in a text file called delete.txt. The -identifier command modifier specifies that the EUL items are identified by identifier, rather than item name. Log information is stored in delete08082003.log. Note: The file delete.txt contains the following text: -item FII_ACCOUNTS.ACCOUNT_NO -item FII_ACCOUNTS.BANK -item FII_ACCOUNTS.LOCATION Enter: java -jar eulbuilder.jar -delete -identifier -connect jchan/12345@my_database -cmdfile delete.txt -log delete08082003.log
-delete_eul
Use this command to delete the current Discoverer EUL.
2-8 Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide
Note: To selectively remove individual EUL objects, use the -delete command.
Information Syntax: Modifiers: Notes: Examples: Details -delete_eul -log <log file name> [-log_only] You can only delete EULs for which you are the registered owner (i.e. the username specified by the -connect command). Example 1: To delete an EUL and store processing details in a log file. java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete_eul -log "c:\my log dir\delete_ eul.log"
-export
Use this command to export EUL objects to a Discoverer export file (i.e. a file with an EEX extension). You can selectively export individual EUL objects (e.g. folders, business areas, functions) or entire EULs (using the -all modifier).
Information Syntax: Modifiers: Details -export <export file> <modifiers> -all -asm_policy <ASM policy> -audit_info <audit details> -business_area <business area> -business_area_and_contents <business area> -external_element <name of external XML file> -folder <folder> -function <function> -hierarchy <hierarchy> -identifier -item_class <item_class> -log <log file name> [-log_only] -summary <summary> -wildcard -workbook <workbook> [-xml_workbooks]
2-9
Information Notes:
Details The <export file> argument specifies the name of the target EEX file into which you export EUL objects. If a directory path is not specified, the target file is created in the default Discoverer folder. To override the default target directory setting, specify a directory path for the file (e.g. c:\data\sales.eex). Note: The directory path must be an absolute path, not a relative path. Use the -business_area_and_contents modifier to export an entire business area and contents. If you only want to export the business area definition, use the -business_area modifier. When you export a business area using the -business_area modifier, Discoverer exports only business area definitions and links to the folders in the business area. Discoverer will export the folders and workbooks only when they are specified by name. When specifying EUL objects, you can use either their Display Name or Identifier. To maintain data relationships, you must also export linked (or joined) objects. The EUL export file produced using the export command is in XML format.
Examples:
Example 1: To export two business areas named Test BA and Final BA from an EUL named eul51, into a file named export.eex, and write to a log file named export.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -export export.eex -business_area "Test BA" -business_area "Final BA" -eul eul51 -log export.log Example 2: In another example, you want to export four items. You store the names of the items you want to export in a text file called export.txt. The -identifier command modifier specifies that the EUL items are identified by identifier, rather than item name. Log information is stored in export07222001.log. The -audit_info command modifier is also used to store update information. Note: The command file 'export.txt' contains this text: -folder FII_ACCOUNTS -hierarchy FII_BANK -hierarchy FII_ACCOUNT_LOCATION -item_class FII_LOCATION_NAME Enter: java -jar eulbuilder.jar -identifier -export test.eex -connect jchan/12345@my_database -audit_info -created_ by ORACLE_APPS -set_updated_by ORACLE_APPS -cmdfile export.txt -log export07222001.log
-grant_privilege
Use this command to grant Discoverer privileges to database users and roles for specified actions (e.g. using drills, saving workbooks).
Information Syntax: Details -grant_privilege <modifiers>
2-10
Information Modifiers:
Details -apps_responsibility <responsibility> -business_area_access <business area> -business_area_admin_access <business area> -identifier -log <log file name> [-log_only] -privilege <privilege> -role <role> -user <username> -wildcard -workbook_access <workbook>
Notes:
Examples of privileges include: administration, user_edition, format_business_area, and create_edit_business_area. For more information about privileges available, see "-privilege". See also: -revoke_privilege.
Examples:
Example 1: To grant the create edit business area privilege to user JOE: java -jar eulbuilder.jar connect jchan/12345@my_ database -eul eultest grant_privilege privilege create_edit_business_area user JOE Example 2: To grant workbook access to role USER_ROLE: java -jar eulbuilder.jar connect jchan/12345@my_ database -grant_privilege workbook_access jchan.Workbook one role USER_ROLE Note: When identifying EUL objects, you are recommended to use identifiers rather than display names. If you are using display names rather than identifiers to identify EUL objects, specify the owner of the object. For example, to specify a workbook owned by jchan, use jchan.Workbook one rather than Workbook one. For more information about identifiers, see "-identifier". Example 3: To grant all administration privileges to users JOE and JCHAN: java -jar eulbuilder.jar connect jchan/12345@my_ database -grant_privilege user JOE -user JCHAN privilege all_admin_privs
-help
This command displays a list of Discoverer commands and their syntax and arguments.
Information Syntax: Modifiers: Details -help [command name(s)] [-all] <command name(s)> -all
Discoverer EUL Command Line for Java Reference 2-11
Information Examples:
Details To see a terse list of commands: java -jar eulbuilder.jar -help To see detailed help on specific commands: java -jar eulbuilder.jar -help <command name(s)> Note: To see help on more than one command, separate commands with a comma. To see detailed help on all commands: java -jar eulbuilder.jar -help -all
-import
Use this command to selectively import EUL objects from one or more Discoverer export files (i.e. EEX files). Discoverer export files are created using the -export command, and contain EUL objects (e.g. folders, business areas, functions, or an entire EUL). For example, if you export a business area using the -export command, you can import the business area from the EEX file created by the export. When you import multiple files, Discoverer automatically resolves references between the files. For example, you can export the Emp folder in fileA.eex and the Dept folder in fileB.eex. If Emp and Dept are joined, the join information is in both files, but neither file contains the information for both folders. If you import both files, the join will be recreated when the second file is processed.
Information Syntax: Modifiers: Details -import <import file(s)> [modifiers] -auto_refresh -identifier -import_rename_mode <rename_new|rename_old|do_not_ import|refresh> -keep_format_properties -log <log file name> [-log_only] -preserve_workbook_owner -auto_gen_name Notes: The <import file(s)> argument specifies the name(s) of the source EEX file(s). You must specify the full path name for the files (e.g. c:\data\sales.eex). Note: The directory path of the EEX file must be an absolute path, not a relative path. Where an import filename include spaces, enclose the filename in double quotes (""). Separate multiple import filenames with a space.
2-12
Details Example 1: To import EUL objects from three files (file1.eex, file2.eex, and file3.exx), enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -import file1.eex -import file2.eex -import file3.eex Example 2: In another example, you want to import four files. You store the names of the files you want to import in a text file called import.txt. This file also contains the -import command. Log information is stored in import07222003.log. Note: The command file import.txt contains: -import C:\bblock\discover\US\file1.eex -import C:\bblock\discover\US\file2.eex -import C:\bblock\discover\US\file3.eex -import C:\bblock\discover\US\file4.eex Enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -eul EUL4_US -apps_user -apps_responsibility "System Administrator" -apps_gwyuid applsyspub/pub -apps_fndnam APPS -apps_security_group Standard -import_rename_mode refresh -auto_refresh -identifier -cmdfile import.txt -log import07222003.log
-load
Use this command to bulk load objects from a database into a Discoverer business area.
Information Syntax: Modifiers: Details -load <business area> [modifiers] -aggregate <SUM|MAX|MIN|COUNT|AVG|DETAIL> -auto_summaries -capitalize -date_hierarchy <date hierarchy> -db_link <database link> -eul <EUL> -description <description> -join <join policy> -log <log file name> [-log_only] -lov <CHAR|DATE|DECIMAL|INTEGER|KEY> -remove_prefix -replace_blanks -sort_folders -sort_items -source <source> -user <username>
Information Notes:
Details To maximize Discoverer performance, it is recommended that you use the -auto_summaries command modifier to automatically create summary folders. For more information, see "-auto_summaries". Use the -source modifier to specify the source of the data (default is the current database server). If you are loading data from an EUL Gateway, the source name must exactly match the EUL Gateway name. Use the -eul modifier to specify an EUL into which to load the objects (default is the Discoverer managers own EUL). If you specify an EUL, you must have access privileges to the named EUL in order for the operation to succeed. When doing a bulk load from an Oracle9i (and later) database, constraints on views are also considered when Discoverer creates joins.
Examples:
Example 1: To bulk load into an EUL named eul51 from an Oracle Designer source on the current connection, creating a new business area named Test BA, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -load "Test BA" -source "Designer 6i bobsworkarea" -eul eul51 -user bob -capitalize -remove_ prefix -replace_blanks -lov CHAR, INTEGER, DECIMAL -aggregate AVG -log load.log -description "Test BA"
-refresh_business_area
Use this command to refresh one or more Discoverer business areas by retrieving an up-to-date EUL structure from the database.
Information Syntax: Modifiers: Details -refresh_business_area <business area> [modifiers] -log <log file name> [-log_only] -identifier -schema -source <server|gateway> -user <username> -wildcard Examples: Example 1: To refresh two business areas named Test BA and Final BA that reside in an EUL named eul_a, from an Oracle Designer source on the current connection owned by user Bob, and summarize information in a log file named refba.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -refresh_business_area "Test BA" -refresh_ business_area "Final BA" -source "Designer 6i bobsworkarea" -eul eul_a -user bob -log refba.log Example 2: To refresh a number of business areas identified by identifier, enter:
2-14
Information
Details java -jar eulbuilder.jar -connect jchan/12345@my_ database -eul eul4138_us -apps_user -apps_ responsibility "Business Views Setup" -apps_gwyuid APPLSYSPUB/PUB -apps_fndnam apps -apps_security_group STANDARD -identifier -log refresh_all_bas_eul4138.log -refresh_business_area ABM_ACTIVITIES -refresh_ business_area ABM_COST_OBJECTS -refresh_business_area ABM_DEPARTMENTS -refresh_business_area ABM_MATERIALS -refresh_business_area AMS_MARKETING_ONLINE -refresh_ business_area...
-refresh_folder
Use this command to refresh one or more Discoverer folders. When you refresh folders, the metadata for the folder is updated. For example, if a new database column has been added to a table, the EUL is updated with details of the new column.
Information Syntax: Modifiers: Details -refresh_folder <folder> [modifiers] -identifier -log <log file name> [-log_only] -source <server|gateway> -user <username> -wildcard Examples: Example 1: To refresh two folders named Sales1 and Sales2 and write to a log file named reffol.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -refresh_folder Sales1 -refresh_folder Sales2 -log reffol.log
-refresh_summary
Use this command to refresh one or more Discoverer summary folders. The query on which the summary folder is based is re-run to retrieve up-to-date data.
Information Syntax: Modifiers: Details -refresh_summary <summary> [modifiers] -business_area <business area> -eul <EUL> -identifier -log <log file name> [-log_only] -wildcard Examples: Example 1: To refresh two summary folders named Summary1 and Summary2 from a business area named Test BA, in an EUL named eul51, and write to a log file named refsum.log, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -refresh_summary Summary1 -refresh_summary Summary2 -business_area "Test BA" -log refsum.log -eul eul51
Discoverer EUL Command Line for Java command modifier reference
-revoke_privilege
Use this command to remove Discoverer privileges from database users for specified actions (e.g using drills, saving workbooks).
Information Syntax: Modifiers: Details -revoke_privilege <modifiers> -apps_responsibility <responsibility> -business_area_access <business area> -business_area_admin_access <business area> -identifier -log <log file name> [-log_only] -privilege <privilege> -role <role> -user <username> -wildcard -workbook_access <workbook> Notes: Examples of privileges include: administration, user_edition, format_business_area, and create_edit_business_area. For a complete list of privileges, see the -privilege modifier. See also: -grant_privilege. Examples: Example 1: To revoke the create edit business area privilege from user JOE: java -jar eulbuilder.jar connect jchan/12345@my_ database -eul eultest revoke_privilege privilege create_edit_business_area user JOE Example 2: To revoke access to a workbook from a role: java -jar eulbuilder.jar connect jchan/12345@my_ database -revoke_privilege workbook_access Workbook one role USER_ROLE Example 3: To revoke all administration and user privileges from users JOE and JCHAN: java -jar eulbuilder.jar connect jchan/12345@my_ database -revoke_privilege privilege all_admin_privs privilege all_user_privs user JOE user JCHAN

This section contains detailed reference information about optional command modifiers available in the Discoverer EUL Command Line for Java. Command modifiers are used to refine or qualify Discoverer EUL Command Line for Java commands. Note the following:

command modifiers are listed in alphabetical order for more information about Discoverer EUL Command Line for Java commands, see "Discoverer EUL Command Line for Java command reference"
-aggregate
Use this command modifier to specify the default aggregate to be used during a bulk load.
2-16
Information Syntax: Used with:
Details -aggregate <SUM|MAX|MIN|COUNT|AVG|DETAIL> -load
-all
Use this command modifier to select every object in an EUL for export. Used with the -help command, this command modifier displays online help for all commands.
Information Syntax: Used with: Details -all -help -export
-apps_fndnam
Use this command modifier to override the value of the Applications Foundation name (FNDNAM).
Information Syntax: Used with: Examples: Details -apps_fndnam <foundation name> -connect java -jar eulbuilder.jar -connect appsuser:appsresp/appspwd -apps_fndnam apps
-apps_fndnam_password
Use this command modifier to specify a Foundation Name password instead of an Oracle Applications user password when you connect to an Applications mode EUL.
Information Syntax: Used with: Details -apps_fndnam_password <foundation name password> -connect
-apps_gwyuid
Use this command modifier to specify a Gateway User ID when you use the -apps_ fndnam modifier.
Information Syntax: Used with: Examples: Details -apps_gwyuid <gateway user ID>/<password> -connect Example 1: java -jar eulbuilder.jar -connect appsuser:appsresp/appspwd -apps_gwyuid applsyspub/pub
-apps_grant_details
Use this command modifier to specify an Oracle Applications schema and password when creating an Oracle Applications mode EUL.
Information Syntax: Used with: Details -apps_grant_details <schema>/<password> -create_eul
-apps_mode
Use this command modifier to create an Applications Mode EUL in the database, and connects you to it. This command modifier is used in conjunction with the -create_eul command.
Information Syntax: Used with: Notes: Details -apps_mode -create_eul See also -apps_grant_details.
-apps_responsibility
Use this command modifier to specify an Oracle Applications responsibility when connecting as an Oracle Applications user to grant (or revoke) privileges.
Information Syntax: Note: Details -apps_responsibility <Oracle Applications responsibility name> The Oracle Applications responsibility name can also be included immediately following a colon (:) placed after the Oracle Applications user name (before the password). For example: java -jar eulbuilder.jar -connect appsuser:appsresp/appspwd -apps_gwyuid applsyspub/pub Used with: -connect -grant_privilege -revoke_privilege
-apps_security_group
Use this command modifier to specify an Oracle Applications security group when connecting as an Oracle Applications user.
Information Syntax: Used with: Details -apps_security_group <Oracle Applications security group name> -connect
2-18
-apps_user
Use this command modifier to connect to Discoverer as an Oracle Applications user.
Information Syntax: Modifiers: Details -apps_user <Applications user> -apps_responsibility -apps_security_group Used with: Examples: -connect Example 1: java -jar eulbuilder.jar -connect appsuser/appspwd -apps_user -apps_responsibility UK_Purchasing -apps_ security_group UK_Managers Example 2: java -jar eulbuilder.jar -connect appsuser:UK_ Purchasing/appspwd -apps_user -apps_security_group UK_ Managers
-asm_policy
Use this command modifier to specify which Oracle Automated Summary Management (ASM) policy you want to delete or export. Note: There is one ASM policy per EUL.
Information Syntax: Used with: Details -asm_policy <ASM policy> -delete -export
-asm_space, -asm_tablespace
Use these command modifiers to override space and tablespace values set in the ASM policy and uses space and tablespace constraints that you specify. The following are valid combinations of tablespace and space values:
Information Syntax: Details -asm_space <bytes> OR -asm_space <bytes> -asm_tablespace <tablespace name> Use -asm_space <bytes> to specify the size of the ASM policy tablespace. Use -asm_tablespace <tablespace name> -asm_space <bytes> to specify a tablespace and tablespace size. Note: You must specify a valid tablespace name. Used with: -asm
Notes:
-audit_info
Use this command modifier to export audit fields with every Created By, Created Date, Updated By, or Updated Date object.
Information Syntax:
Details -audit_info [-set_created_by <name of creator>] [-set_created_date <date of creation>] [-set_updated_by <name of updater>] [-set_updated_date <date of update>] -export See also: -set_created_by -set_created_date -set_updated_by -set_updated_date
Used with: Notes:
-auto_gen_name
Use this command modifier to set the Auto Generate name property, of all secondary elements to Yes, for all folders imported. For example, you might export a business area called Performance to an EEX file. If you then import the Performance business area from the EEX file at a later date, Discoverer sets the Auto Generate name property of all secondary elements to Yes, irrespective of the value that exists in exported file. For more information about secondary elements and the Auto generate name property, see the Oracle Business Intelligence Discoverer Administration Guide.
Information Syntax: Used with: Details -auto_gen_name -import
-auto_refresh
Use this command modifier to automatically get up-to-date metadata from the database for all folders imported. For example, you might export a business area called Performance to an EEX file. If you then import the Performance business area from the EEX file at a later date, Discoverer retrieves up-to-date metadata from the data dictionary.
Information Syntax: Used with: Details -auto_refresh -import
-auto_summaries
Use this command modifier to automatically create summary folders during a bulk load using Discoverers powerful Automated Summary Management (ASM) facility. Summary folders contain data that has already been queried and processed so that it can be re-used. This enables you to improve Discoverers performance and minimize response times for Discoverer end-users.
Information Syntax: Used with: Details -auto_summaries -load
2-20
Notes:
For more information about summary folders and ASM, see Oracle Business Intelligence Discoverer Administration Guide.
-auto_upgrade
Use command modifier to enable Discoverer to automatically upgrade an EUL when you connect to an EUL. For example, you might need to upgrade when a new version of Discoverer is installed. If you do not use the -auto_upgrade modifier when an upgrade is required, the connect fails and an error message is displayed.
Information Syntax: Used with: Details -auto_upgrade -connect
-ba_link
Use this command modifier to remove a folder from a business area by removing the link between the two.
Information Syntax: Notes: Details -ba_link <business area>.<folder> The folders or business areas themselves are not removed, only the link between them. For example, to remove the folder Stores from the business area Video Analysis Information, you specify "Video Analysis Information".Stores. Used with: -delete
Hint: To remove a folder from an EUL completely, use '-delete -folder' (for more information, see "-folder").
-business_area
Use this command modifier to specify a business area for export or deletion. Note: Only the definition of the business area is exported or deleted, not the objects (e.g. folders, items, item classes) contained within it. To export or delete a business area and the objects contained within it, use -business_area_and_contents.
Information Syntax: Used with: Details -business_area <business area> -delete -export -refresh_summary
-business_area_access
Use this command modifier to grant (or revoke) access to business areas to (or from) database users, roles, and Oracle Applications responsibilities.
Details -business_area_access <business area> -grant_privilege -revoke_privilege
-business_area_admin_access
Use this command modifier to grant (or revoke) business area administration privileges to business areas to (or from) database users, roles, and Oracle Applications responsibilities.
Information Syntax: Used with: Details -business_area_admin_access <business area> -grant_privilege -revoke_privilege
-business_area_and_contents
Use this command modifier to specify a business area and objects (e.g. folders, items, item classes) contained within it for export or deletion. Note: To export or delete a business area definition but leave the objects (e.g. folders, items, item classes) contained within it intact, use -business_area).
Information Syntax: Used with: Details -business_area_and_contents <business area> -delete -export -refresh_business_area
-capitalize
Use this command modifier to request that folder names have initial capital letters when they are generated from their respective column names during a bulk load.
Information Syntax: Used with: Details -capitalize -load
-character_set_encoding
Use this command modifier to specify the character set in which command files are saved (e.g. EUC, Shift_JIS, UTF-8). For example, a command file created on Solaris with a Japanese locale is encoded in the default Java character set (i.e. EUC). However, on Windows, Japanese characters are usually encoded in Shift_JIS or UTF-8, which means that you need to specify a character set so that Java can interpret commands correctly.
2-22
Information Syntax: Used with: Notes:
Details -character_set_encoding <character set> -cmdfile You must specify this modifier at the command prompt immediately following the -cmdfile command. In other words, you cannot include the -character_set_encoding command modifier inside the command file itself.
-condition
Use this command modifier to specify a condition for deletion.
Information Syntax: Used with: Details -condition <condition> -delete
-date_hierarchy
Use this command modifier to specify the date hierarchy to be used during a bulk load. If you do not specify a date hierarchy, the default date hierarchy is used.
Information Syntax: Used with: Details -date_hierarchy <date hierarchy> -load
-db_link
Use this command modifier to specify the database link to be used during a bulk load.
Information Syntax: Used with: Details -db_link <database link> -load
-default_tablespace
Use this command modifier to specify a default tablespace for the current username when you create an EUL. The value specified changes the default tablespace value for the current username (for more information, see "What privileges do you require to use the Discoverer EUL Command Line for Java?").
Information Syntax: Used with: Notes: Details -default_tablespace <tablespace name> -create_eul Database tablespace names are case sensitive.
-description
Use this command modifier to specify a description for an object.
Details -description <description> -load If a description contains spaces, enclose the <description> value in double quotes ("").
-eul
Use this command modifier to specify an EUL on which to run a command. You must have access privileges to the specified EUL. If not specified, the default EUL for the database user is used.
Information Syntax: Used with: Details -eul <EUL> -connect -load -refresh_summary Notes: <EUL> must be the name of a valid EUL. This modifier does not change the default EUL for the user.
-eul_language
Use this command modifier to specify a language for the EUL.
Information Syntax: Used with: Details -eul_language <language> -create_eul
-external_element
Use this command modifier to place XML code from a specified file at the top of an export file. The -external_element command modifier is used only with the -export command.
Information Syntax: Used with: Notes: Details -external_element <filename> -export To use this command modifier, type the XML that you want to place at the top of the export file into a separate file and specify the name of this file as the <filename> argument. You can use the -external_element command modifier multiple times in the same export operation (see example below). <filename> is the name of the file containing the xml that you want to include in the EEX file.
2-24
Details Example 1: To place the xml from the files custom1.xml and custom2.xml into the top of the export file myBA.eex, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -export myBA.eex -business_area bus_area1 -external_element custom1.xml -external_element custom2.xml
-folder
Use this command modifier to specify a folder for export or deletion.
Information Syntax: Used with: Details -folder <folder> -delete -export
Hint: If you want to remove a folder from a business area without removing the folder from the EUL, use -ba_link.
-function
Use this command modifier to specify a function for export or deletion.
Information Syntax: Used with: Details -function <PL/SQL function> -delete -export
-hier_node
Use this command modifier to specify a node in a hierarchy for deletion.
Information Syntax: Used with: Details -hier_node <hierarchy>.<hierarchy node> -delete
-hierarchy
Use this command modifier to specify a hierarchy for export or deletion.
Information Syntax: Used with: Details -hierarchy <hierarchy> -delete -export
-identifier
Use this command modifier to specify EUL objects by identifier, rather than by display name.
Information Syntax: Used with: Details -identifier -delete -export -grant_privilege -refresh_business_area -refresh_folder -refresh_summary -revoke_privilege Notes: If you reference an object prefixed with a parent object name, you must also reference the parent object name using its identifier. For example, to delete the item Region.City, you must use identifiers for both objects, as follows: -delete -item REGION_01.CITY_01 -identifier Examples: Example 1: To delete the item Video Analysis Information.Store Name using identifiers, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -item DC_VIDEO_ANALYSIS_ INFORMATION4.STORE_NAME01 -identifier Example 2: To delete a folder with the identifier FOLDER_01, enter: java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -folder FOLDER_01 -identifier
-import_rename_mode
Use this command modifier to specify how to manage imported EUL objects that match EUL objects in your current EUL.
Information Syntax: Used with: Notes: Details -import_rename_mode <rename_new|rename_old|do_not_ import|refresh> -import Use rename_new to rename imported objects that match existing objects. Use rename_old to rename existing objects that match imported objects. Use do_not_import to not import objects that match existing objects. Use refresh to merge imported objects with existing objects. By default, merged objects are matched on display name. Use the -identifier command modifier to match on identifier.
-item
Use this command modifier to specify an item for deletion.
2-26 Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide
Details -item <item> -delete -export
-item_class
Use this command modifier to specify an item class for export or deletion.
Information Syntax: Used with: Details -item_class <item class> -delete -export
-join
This command modifier is used in two ways depending on which command you use it with:
used with the -load command, the -join command modifier enables you to specify how Discoverer creates joins during a bulk load used with the -delete command, the -join command modifier enables you to remove a specific join
Information Syntax: Details -load -join <NONE|COLUMN_NAME|PRIMARY_KEY> -delete -join <join name> Used with: -delete -load
-keep_format_properties
Use this command modifier to keep existing format properties (e.g. display names, descriptions) on import. If you do not use this command modifier, you update existing format properties with the display names and descriptions in the import file (i.e. the EEX file).
Information Syntax: Used with: Details -keep_format_properties -import
-log
This enables you to specify a name for the log file that stores command status messages. After each command is executed, Discoverer writes a status message indicating whether the command was successful. You can use -log with the optional -log_only command modifier.
Details -log < log file name> [-log_only] All commands except -help. If the file specified by <log file name> already exists, the existing log file is overwritten. If the file specified by <log file name> does not exist, a new file is created.
-log_only
Use this command modifier to perform impact analysis by simulating a command and generating a log, without changing live data. Using this command modifier enables you to check for errors and exceptions before changing data. This command is used in conjunction with the -log command modifier.
Information Syntax: Details -log < log file name> [-log_only] -log
Used with:
-lov
Use this command modifier to specify the data types for which a list of values are generated during a bulk load.
Information Syntax: Used with: Details -lov <CHAR|DATE|DECIMAL|INTEGER|KEY> -load
-overwrite
Use this command modifier to overwrite an existing EUL owned by the intended owner when you create an EUL. If omitted, the default is to not overwrite an existing EUL.
Information Syntax: Used with: Details -overwrite -create_eul
-password
Use this command modifier to specify the password for a new user created using the -create_eul command.
Information Syntax: Details -password <password>
2-28
Information Used with:
Details -create_eul
-preserve_workbook_owner
Use this command modifier to specify that the original workbook owners maintain ownership of an imported workbook when you import an EUL.
Information Syntax: Used with: Details -preserve_workbook_owner -import
-private
Use this command modifier to specify that public access is not granted to a newly created EUL. In other words, only the EUL owner can access the newly created EUL. If omitted, public access is granted to the newly created EUL.
Information Syntax: Used with: Details -private -create_eul
-privilege
Use this command modifier to specify the privileges to grant (or revoke) to (or from) database users. For more information about granting and revoking privileges, see "-grant_privilege" and "-revoke_privilege".
Information Syntax: Used with: Details -privilege <privilege> -grant_privilege -revoke_privilege
Information Notes:
Details <privileges> can be one of the following: Use 'administration' to enable the user or role to log in to Discoverer Administrator. Note that to allow the user to access the features in Discoverer Administrator, you must select individual Administration privileges (e.g. create_summaries, collect_qpp). Use 'user_edition' to enable the user or role to log in to Discoverer Desktop and Discoverer Plus. Note that to allow the user to access the features in Discoverer Desktop and Discoverer Plus, you must select individual Desktop/Plus privileges (e.g. drill out, schedule_workbook). Use 'format_business_area' to enable the user or role to edit formatting information (e.g. folders, summary folders, joins) in an existing business area to which they have access. Use 'create_edit_business_area' to enable the user or role to create and modify business areas, folders, summary folders, joins, calculations, conditions, hierarchies and item classes. Use 'create_summaries' to enable the user or role to create summary folders. This privilege also requires database resource privileges. Use 'set_privilege' to enable the user to maintain and modify user privileges. Note: You cannot grant this privilege to a role. Use 'manage_scheduled_workbooks' to enable the user or role to monitor and maintain scheduled workbooks. Use 'create_edit_query' to enable the user or role to create new worksheets (queries) and modify existing ones. Without this privilege, the user can only open and run existing workbooks and worksheets. Use 'collect_qpp' to collect performance statistics when the user opens workbooks and worksheets. Use 'item_drill' to enable the user or role to drill down into worksheet data. Use 'drill_out' to enable the user or role to launch another application to see related information by drilling on an item in a worksheet.
2-30
Information Notes continued:
Details Use 'grant_workbook' to enable the user or role to grant access to their workbooks so that other users can access them. Use 'schedule_workbook' to enable the user to schedule a workbook to run at a later time or at regular intervals (i.e. daily, weekly, monthly). Note: You cannot grant this privilege to a role. Use 'save_workbook_database' to enable the user or role to save the workbooks in the database. Use 'all_admin_privs' to enable the user or role to following privileges:

administration format_business_area create_edit_business_area create_summaries set_privilege manage_scheduled_workbooks
Use 'all_user_privs' to enable the user or role to following privileges:

user_edition create_edit_query collect_qpp item_drill drill_out grant_workbook schedule_workbook save_workbook_database
-remove_prefix
Use this command modifier to specify that item names do not include the column name prefix when they are generated from their respective column names during a bulk load.
Information Syntax: Used with: Examples: Details -remove_prefix -load java -jar eulbuilder.jar -connect jchan/12345@my_ database -load "Test BA" -remove_prefix In this example, an item named Stores_Store_name would be loaded as Store_name.
-replace_blanks
Use this command modifier to replace underscores with spaces in EUL object names during a bulk load.
Information Syntax: Used with: Examples:
Details -replace_blanks -load java -jar eulbuilder.jar -connect jchan/12345@my_ database -load "Test BA" -replace_blanks In this example, an item named Store_name would be loaded as Store name.
-role
Use this command modifier to specify a database role when you grant (or revoke) privileges to (or from) database users.
Information Syntax: Used with: Details -role <role> -grant_privilege -revoke_privilege
-schema
Use this command modifier to specify a schema (user) during a business area refresh.
Information Syntax: Used with: Details -schema <schema> -refresh_business_area
-set_created_by
Use this command modifier to specify who performed an export for audit purposes (during an export).
Information Syntax: Used with: Examples: Details -audit_info -set_created_by <name of creator> -audit_info Example 1: To export a business areas Test BA from an EUL named eul51, into a file named export.eex, and specify that the export was performed by jchan, enter: java -jar eulbuilder.jar -connect jchan/12345@my_database -export export.eex -business_area "Test BA" -audit_info -set_ created_by jchan
-set_created_date
Use this command modifier to specify an export date for audit purposes (during an export).
Information Syntax: Details -audit_info -set_created_date <date of creation>
2-32
Information Used with: Examples:
Details -audit_info Example 1: To export a business areas Test BA from an EUL named eul51, into a file named export.eex, and specify that the export was performed on January 1st 2004, enter: java -jar eulbuilder.jar -connect jchan/12345@my_database -export export.eex -business_area "Test BA" -audit_info -set_ created_date "1st January 2004"
-set_updated_by
Use this command modifier to specify who updated an EUL for audit purposes (during an export).
Information Syntax: Used with: Details -audit_info -set_updated_by <name of updater> -audit_info
-set_updated_date
Use this command modifier to specify a date of update for audit purposes (during an export).
Information Syntax: Used with: Details -audit_info -set_updated_date <date of update> -audit_info
-sort_folders
Use this command modifier to specify that Discoverer will alphabetically sort folders during a bulk load.
Information Syntax: Used with: Details -sort_folders -load
-sort_items
Use this command modifier to specify that Discoverer will alphabetically sort items during a bulk load.
Information Syntax: Used with: Details -sort_items -load
-source
Use this command modifier to specify a data source.
Details -source <gateway name> -load -refresh_business_area
Notes:
Use gateway name to specify the name of an Oracle Designer object or other gateway. The gateway name must exactly match the gateway name displayed in the Load Wizard. In the case of Oracle Designer, specify "Designer 6i - <workarea name>" (if you are using a version of Oracle Designer prior to Oracle Designer 6i, simply specify "Oracle Designer repository"). If you do not specify a gateway using -source, Discoverer uses the online dictionary.
-summary
Use this command modifier to specify a summary for export or deletion.
Information Syntax: Used with: Details -summary <summary> -delete -export
-temporary_tablespace
Use this command modifier to specify a temporary tablespace when you create an EUL.
Information Syntax: Used with: Details -temporary_tablespace <temporary tablespace name> -create_eul
-user
Use this command modifier to specify the username to be used for the operation. When used with the -create_eul command, this command modifier enables you to create a new database user.
Information Syntax: Used with: Details -user <username> -create_eul -grant_privilege -refresh_business_area -refresh_folder -refresh_summary -revoke_privilege Notes: Any valid username.
2-34
-wildcard
Use this command modifier to specify EUL objects using wildcard characters (for more information, see About using wildcards to identify EUL objects).
Information Syntax: Used with: Details -wildcard -delete -export Examples: Example 1: For example, to delete all business areas with display names beginning with 'A': java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -business_area A% -wildcard Example 2: To delete all business areas with a developer key of 'A' followed by exactly two more characters: java -jar eulbuilder.jar -connect jchan/12345@my_ database -delete -business_area A__ -identifier -wildcard In the above example, a business area with a developer key 'ABC' would be deleted, but not a business area with a developer key 'ABCD'.
-workbook
Use this command modifier to specify a workbook for export or deletion.
Information Syntax: Used with: Details -workbook <workbook> [-xml_workbooks] -delete -export
-workbook_access
Use this command modifier to grant (or revoke) access to workbooks to (or from) database users, roles, or responsibilities.
Information Syntax: Used with: Details -workbook_access <workbook> -grant_privilege -revoke_privilege
-xml_workbooks
This command modifier (used with the -export command) forces all workbooks to be exported in XML format and binary large object (BLOB) format. Exporting workbooks in XML format enables you to view the definition of exported workbooks in a text editor or XML browser.
Information Syntax: Details -xml_workbooks
Information Used with:
Details -export
2-36
A
This appendix describes error messages used by the Discoverer EUL Command Line for Java.

This appendix provides reference information about error message used by the Discoverer EUL Command Line for Java.
Error text Delete requested without specifying any objects to delete Error creating export file Error creating impact analysis file Error creating log file Error parsing command file <option> Export requested without specifying any objects to export Incomplete option Error description A delete request has been specified without providing any EUL objects to delete. A file error on creating the EEX file during an export. A file error on creating the impact analysis file using the -log -log_only command. A file error on creating the log file. The command file contained syntax errors. An export request was specified without specifying any EUL elements to export (and without specifying the -all option). A valid option has been specified but without specifying all the additional options required. For example, if you type '-delete -folder' without specifying a folder name. An invalid aggregate option has been specified for the bulk load operation. Valid options are sum, max, min, count, avg, and detail. During an export request you can specify the Created Date and Updated Date this must be in the format 'dd/mm/yyyy hh:mm:ss' or SYSDATE otherwise you will return this error. An invalid gateway option has been specified for the bulk load operation. Valid options are online_dictionary, designer, and external. An import request was made specifying an unrecognized rename mode. Valid options are rename_old, rename_new, do_not_import, and refresh.
Invalid aggregate
Invalid date format - use dd/mm/yyyy hh:mm:ss Invalid gateway type
Invalid import rename mode
Discoverer EUL Command Line for Java error messages A-1
Error text Invalid join option
Error description An invalid join option has been specified for the bulk load operation. Valid options are primary_key, column_name, and none. An invalid LOV option has been specified for the bulk load operation. Valid options are char, integer, decimal, date, and key. An unrecognized command line option has been specified. An option has been requested without specifying the parent option. For example, specifying -lov without being in the context of a bulk load request. An option has been requested without specifying a valid parent option. This is the same as above but for options which make sense in more than context. For example, -folder can be valid both for export and delete requests. A create Applications mode EUL request has been made without specifying the Applications password. A create Applications mode EUL request has been made without specifying the Applications user. A command file request was made without specifying a command file to use. A command request was made without a connection having been made to an EUL. A command request was made without specifying a database username (or Applications username). A command request was made without specifying a database password (or Applications password). A refresh request was made without specifying any folders or business areas to refresh. A connect request has been specified but no connect string provided. A request has been specified without requesting a connection. The -log option has been specified without a filename for the log file. An export request was made without specifying an EEX file to export to. An import request was specified without specifying any EEX files to import.
Invalid LOV option
Invalid option Invalid option - cannot set <option> without setting <option> Invalid option - cannot set <option> without setting one of <option> No Apps password specified for create Apps EUL operation No Apps user specified for create Apps EUL operation No command file specified No connection to an EUL has been established No user specified for create EUL operation. No password specified for create EUL operation. Refresh requested without specifying any folders or business areas to refresh You must specify a connect string You must specify a connection to an EUL You must specify a name for the log file You must specify an export file You must specify some .EEX files to import
A-2 Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide
B
This appendix describes the differences between the Discoverer EUL Command Line for Java and the Discoverer Administrator Command Line Interface.

The Discoverer EUL Command Line for Java is similar to the Oracle Discoverer Administrator Command Line Interface. If you are migrating commands from Oracle Discoverer Administrator Command Line Interface to Discoverer EUL Command Line for Java, note the following differences:
Oracle9iAS Discoverer Administrator Command Line Interface command commands and command modifiers are prefixed with the '/' character /insert_blanks /refresh /refresh_bus_area /rename
Equivalent Discoverer EUL Command Line for Java command commands and command modifiers are prefixed with the '-' character -replace_blanks -import_rename_mode has values <rename_new|rename_ old|do_not_import|refresh> -refresh_business_area -import_rename_mode has values <rename_new|rename_ old|do_not_import|refresh>
Differences in syntax between Discoverer command line interfaces B-1
B-2 Oracle Business Intelligence Discoverer EUL Command Line for Java Users Guide
Index
C
character set encoding, 2-22 EUC Shift_JS UTF-8, 2-22 command examples, 1-7 examples of command files, 1-8 how to enter, 1-4 syntax, 2-2 testing before use, 1-5 command modifiers aggregate, 2-16 all, 2-17 apps_fndnam, 2-17 apps_fndnam_password, 2-17 apps_grant_details, 2-18 apps_gwyuid, 2-17 apps_mode, 2-18 apps_responsibility, 2-18 apps_security_group, 2-18 apps_user, 2-19 asm_space, 2-19 asm_tablespace, 2-19 audit_info, 2-19 auto_gen_name, 2-20 auto_refresh, 2-20 auto_summaries, 2-20 auto_upgrade, 2-21 ba_link, 2-21 business_area, 2-21 business_area_access, 2-21 business_area_admin_access, 2-22 business_area_and_contents, 2-22 capitalize, 2-22 character_set_encoding, 2-22 condition, 2-23 date_hierarchy, 2-23 db_link, 2-23 default_tablespace, 2-23 description, 2-23 eul, 2-24 eul_language, 2-24 external_element, 2-24 folder, 2-25 function, 2-25 hier_node, 2-25 hierarchy, 2-25 identifier, 2-26 import_rename_mode, 2-26 item, 2-26 item_class, 2-27 join, 2-27 keep_format_properties, 2-27 log, 2-27 log_only, 2-28 lov, 2-28 overwrite, 2-28 password, 2-28 preserve_workbook_owner, 2-29 private, 2-29 privilege, 2-29 remove_prefix, 2-31 replace_blanks, 2-31 role, 2-32 schema, 2-32 set_created_by, 2-32 set_created_date, 2-32 set_updated_by, 2-33 set_updated_date, 2-33 sort_folders, 2-33 sort_items, 2-33 source, 2-33 summary, 2-34 temporary_tablespace, 2-34 user, 2-34 wildcard, 2-35 workbook, 2-35 workbook_access, 2-35 xml_workbooks, 2-35 commands asm, 2-4 character set encoding, 2-22 cmdfile, 2-5 connect, 2-5 create_eul, 2-6 delete, 2-7 delete_eul, 2-8 export, 2-9 grant_privilege, 2-10 help, 2-11 import, 2-12 load, 2-13
Index-1
refresh_business_area, 2-14 refresh_folder, 2-15 refresh_summary, 2-15 revoke_privilege, 2-16 compatibility Linux, 1-1 UNIX, 1-1 Windows, 1-1 conventions command syntax, x
HP-UX, 1-4 registry variables,
2-3
P
prerequisites to running commands, 2-2 privileges database, 1-3 granting, 2-10 quota, 1-3 revoking, 2-16 tablespace, 1-3 problems diagnosing, 1-5
D
database specifying, 2-6 tnsnames.ora, 2-6 database privileges, 1-3 Discoverer EUL Command Line for Java about, 1-1 about command modifiers, 1-3 about commands, 1-3 command file examples, 1-8 command files, 1-7 command reference, 2-4 example commands, 1-7 quick guide, 1-8 required database privileges, 1-3 syntax conventions, 2-1
Q
quick guide to commands, 1-8
R
registry. See Windows registry
S
shell script, 2-2 syntax command syntax, 2-2 conventions, 2-1
E
environment variables, 2-2 eulapi shell script, 2-2 export files adding XML code to, 2-24
T
testing commands before use, 1-5 tnsnames.ora, 2-6 troubleshooting, 1-5 environment prerequisites, 2-2 error messages, A-1
H
help online, 2-11 Heterogeneous Connectivity, 1-1 Heterogeneous Services, 1-1
U
UNIX compatibility, 1-1
W I
impact analysis, 1-5, 2-28 wildcards example using %, 1-6 example using _, 1-7 using to specify EUL objects, Windows compatibility, 1-1 Windows registry Discoverer, 2-3 workbook export XML format, 2-35
J
Java compatibility, 1-1
1-6
L
Linux compatibility, log files, 1-5 1-1
X
XML adding to export file, 2-24 format for workbook export, 2-35
O
online help, 2-11 OracleBI Discoverer EUL command line in Linux, Solaris, and
Index-2

Oracle® Business Intelligence Discoverer EUL Command Line For Java

Uploaded by

Copyright:

Available Formats

You might also like

Oracle® Business Intelligence Discoverer EUL Command Line For Java

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle® Business Intelligence Discoverer EUL Command Line For Java

Uploaded by

Copyright:

Available Formats

Oracle Business Intelligence Discoverer EUL Command Line for Java

Users Guide 10g Release 2 (10.1.2.0.0)

Discoverer EUL Command Line for Java Reference

Discoverer EUL Command Line for Java error messages

Differences in syntax between Discoverer command line interfaces

Send Us Your Comments

JGoodies License Agreement

What is the OracleBI Discoverer EUL Command Line for Java?

Figure 11 Discoverer interfaces to the Discoverer EUL

What is a Discoverer EUL Command Line for Java command?

What is a Discoverer EUL Command Line for Java command modifier?

oracle_home_path/bin/eulapi -connect jchan/12345@my_database -refresh_folder Sales1

How to run a Discoverer EUL Command Line for Java command

java -jar eulbuilder.jar -connect jchan/12345@my_database -export objectlist.xml -all % -wildcard

About troubleshooting the Discoverer EUL Command Line for Java

How to type commands directly at a command prompt

How to run commands stored in a command file

java -jar eulbuilder.jar -connect jchan/12345@my_database -cmdfile import.txt

About troubleshooting the Discoverer EUL Command Line for Java

About using wildcards to identify EUL objects

-log <log file name> -log_only

About using wildcards to identify EUL objects

You can use wildcards when you:

How to identify EUL objects using the percent wildcard:

What is a command file?

java -jar eulbuilder.jar -connect jchan/12345@my_database -delete -business_area A% -wildcard

How to identify EUL objects using the underscore wildcard:

What is a command file?

Examples of command files

Examples of command files

List of Discoverer EUL Command Line for Java commands

List of Discoverer EUL Command Line for Java commands

List of Discoverer EUL Command Line for Java commands

What command syntax conventions does this guide use?

Discoverer EUL Command Line for Java Reference

What is the syntax for commands?

Figure 21 Command conventions used in this guide

What is the syntax for commands?

-refresh_folder Sales -refresh_folder SALES_132388 -identifier

Discoverer EUL Command Line for Java Reference

Discoverer EUL Command Line for Java command reference

Discoverer Registry Variable

DefaultPreserveDisplayPropertyForRefresh EnableTriggers FormatXML AppsFNDNAM AppsGWYUID SetNULLItemHeadingOnBulkLoad MaxNumberJoinPredicates SqlTrace

-import -connect -apps_user

dis51pr -setadminpref DefaultPreserveDisplayPropertyForRefresh=1

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java Reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java Reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java Reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java command reference

Discoverer EUL Command Line for Java Reference 2-11

Discoverer EUL Command Line for Java command reference