Removing a Data Source Administrative Redefining a Data Source

7-4 Oracle Fusion Middleware Users Guide for Oracle MapViewer and the string associated with the comment attribute gives the reason for the failure data source already exists. ?xml version=1.0 ? non_map_response add_data_source succeed=true comment=data source already exists non_map_response

7.1.2 Removing a Data Source Administrative

The remove_data_source element can be used to remove a permanent data source or a dynamically added data source. This element has the following definition: ELEMENT non_map_request remove_data_source ELEMENT remove_data_source EMPTY ATTLIST remove_data_source data_source CDATA REQUIRED jdbc_password CDATA REQUIRED The data_source attribute identifies the name of the data source to be removed. The jdbc_password attribute identifies the login password for the database user in the data source. jdbc_password is required for security reasons to prevent people from accidentally removing data sources from MapViewer. Removing a data source only affects the ability of MapViewer to use the corresponding database schema; nothing in that schema is actually removed. Example 7–3 removes a data source named mvdemo. Example 7–3 Removing a Data Source ?xml version=1.0 standalone=yes? non_map_request remove_data_source data_source=mvdemo jdbc_password=password non_map_request The DTD for the response to a remove_data_source request has the following format: ELEMENT non_map_response remove_data_source ELEMENT remove_data_source EMPTY ATTLIST remove_data_source succeed true | false REQUIRED For example: ?xml version=1.0 ? non_map_response remove_data_source succeed=true non_map_response

7.1.3 Redefining a Data Source

Note: You should use request only during development or testing, and not for production work. MapViewer XML Requests: Administrative and Other 7-5 For convenience, MapViewer lets you redefine a data source. Specifically, if a data source with the same name already exists, it is removed and then added using the new definition. If no data source with the name exists, a new data source is added. If an existing data source has the same name, host, port, SID, user name, password, mode, and number of mappers as specified in the request, the request is ignored. The redefine_data_source element has the following definition: ELEMENT non_map_request redefine_data_source ELEMENT redefine_data_source EMPTY ATTLIST redefine_data_source name CDATA REQUIRED container_ds CDATA IMPLIED jdbc_tns_name CDATA IMPLIED jdbc_host CDATA IMPLIED jdbc_port CDATA IMPLIED jdbc_sid CDATA IMPLIED jdbc_user CDATA IMPLIED jdbc_password CDATA IMPLIED jdbc_mode oci8 | thin IMPLIED number_of_mappers INTEGER REQUIRED The attributes and their explanations are the same as for the add_data_source element, which is described in Section 7.1.1 . The DTD for the response to a redefine_data_source request has the following format: ELEMENT non_map_response redefine_data_source ELEMENT redefine_data_source EMPTY ATTLIST redefine_data_source succeed true | false REQUIRED For example: ?xml version=1.0 ? non_map_response redefine_data_source succeed=true non_map_response

7.1.4 Listing All Data Sources Administrative or General-Purpose