Import export metadata

Why does this command work
exportMetadata(application='MyPortal', server='DefaultServer',toLocation='/tmp/testmar')
whereas , this does not? It complains about location which works for the previous command.
exportMetadata(application='MyPortal', server='OtherServer',fromLocation=/tmp/testmar')
Both integrated ('DefaultServer') and standalone server ('OtherServer') are running on the same machine.
and it gives me the following errors:
Location changed to custom tree. This is a writable tree with No root.
For more help, use help(custom)
Executing operation: exportMetadata.
Traceback (innermost last):
File "<console>", line 1, in ?
File "C:\JDEVEL~2\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", li
ne 257, in exportMetadata
File "C:\JDEVEL~2\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", li
ne 801, in executeAppRuntimeMBeanOperation
File "C:\JDEVEL~2\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", li
ne 1079, in saveStackAndRaiseException
WLSTException: MDS-90035: The target directory or archive "/tmp/testmar" for e
xporting metadata is invalid.MDS-91009: Operation "exportMetadata" failure. Use
dumpStack() to view the full stacktrace.

Hi RuchaChavan,
If I don't misunderstand that you want to export all your config of Portal Application at runtime? If that's correct, you can using em to export their to zip file very easy.
You can go into Application Deployments on the left,select Portal Application which you want export MDS. Then select MDS Configuration in here you can see the button Export and Import. And now you can do what you want
Hope it help you
Best regard!

Similar Messages

EIF Export/Import Only Metadata

The following export statement 'export' entire AW with data. And import also imports everything.
exec dbms_aw.execute('export all to eif file ''MYDIR/TEST_OLAP.eif'' api');
exec dbms_aw.execute('import all from eif file ''MYDIR/TEST_OLAP.eif'' api');
Can I only export and import the metadata(like we do XML template) using commands like above?

Just learned... Try below.
jarname_ is the name of the AWM jar. e.g. awm11.2.0.2.0.jar
user is the name of your user. e.g. TESTOLAP
password is the password for your user
url is the url for a node in your RAC cluster. e.g. jdbc:oracle:thin:@myserver:1521:orcl
filename is the name of the XML file to create. e.g. testolap.xml
java -classpath jarname_ oracle.olapi.metadata.util.ExportXML -user user -password password -url url > filename
The java version should be "1.6.0_24".

Import/Export of Metadata Needed

We need the ability to Import and Export metadata in CSV format or equivalent. Our office currently works with Extensis Portfolio which allows us to Import and Export large amounts of data so it can be taken into Excel and worked on, cleaned up, changed or whatever. We then reimport it back into the Portfolio catalog. It's very easy and very efficient. Would love to see something similar in Lightroom.

Anton
If you want to do this, I think the best route would be through hitting the back end database. You could use Excel formulae (the ampersand) to concatenate cell values and create a SQL statement that you run against the SQLite database. You would need to be decent at Excel, at SQL, and understand the database structure.
Mature DAM programs often have features that allow users to map text file data to the program's fields, and professional-grade programs usually have scripting that allows you to roll your own data updating, which could include external sources.
You might have a look at Portfolio and its 30 day trial. This has mapping, so you can get that text file into its database, and it can also be scripted from Excel VBA. It can then write that metadata directly into jpegs or tifs - no other formats.
John

Exporting/Importing Transformation metadata

Hello All,
I have a custom written package which we use as a post-mapping process.
I compile this package in the database external to OWB and then I import the definition into OWB. Where it becomes a transformation.
We are currently in Dev and I now want to migrate to Test.
So I tried to export the metadata for this package so I can import it into the Test Design Center. This is because I want everything contained in OWB.
The export appears to work but when I import it into Test (which also seems to work) and try to generate the code it produces an empty file.
Is it possible to export and import the metadata of a custome transformation? If so are there any particular options I should use?
I'm sorry this seems to be a basic task but I can't find anything in the documentation and I wondered if anyone else had come across it.
Thanks in advance.

Hi,
you cannot redesign a package with an import. You will only get the package header, not the body. You must create the custom transformation in the design center and then deploy it to the target database - not the other way round.
Regards,
Detlef

How can I export metadata to a csv file in CS4?

Help please, I used Workflow Automation Scripts on CS3 but it doesn't seem to work on CS4.

OK,
after combing through these posts and trying various 'solutions' I have found that the Barred Rock export metadata script is the only one I have been able to get to work in CS4, kinda. It is a superior script to the original workflow automation script that edo75 refers to, as it does not seem to have the comma issue encountered by jesse and others, where if there are any commas in your metadata it creates a new column and your excel file becomes nonsensical and disorganized. There is a way to avoid this by the way, simply by opening a new file in excel and importing the csv file as text, you then tell excel to read the data the right way by selecting various delimiter combinations. It is not a perfect solution but I have found that by doing this it places most of my metadata in the proper columns, and I end up doing a minimal amount of editing. The barred rock version, which I assume is a modified version of the original script available from adobe as the interface is exactly the same, does not seem to have this issue with commas at all, I am unsure why. If B. Stucky is still reading these posts he may be able to answer, as I think he wrote this script?
Anyhow I was able to get the script to load in CS4 and then I had to tweek the script to recognize my custom metadata schema, which I was able to do. Now however there is an issue with it recognizing the actual metadata in the image files. I suspect it is a mynamespace issue, that is, I do not have the right path for it to locate the actual metadata for export.
here is where I suspect the problem lay, where this "http://NPSAlaskaImageStandard" is incorrect.
new MdNs.MetadataNamespace( "NPS Alaska Image Standard", "http://NPSAlaskaImageStandard", "NPSAlaskaImageStandard" );
I am a total novice with this stuff so this may not be it at all, however this is my best guess, anyone know the answer?

Error while exporting metadata file /iam-features-ldap-sync/LDAPUser.xml

Hi All,
i am trying to export /iam-features-ldap-sync/LDAPUser.xml metadata file with the weblogic properties mentioned below
# Weblogic Server Name on which OIM application is running
wls_servername=oim_server1
# If you are importing or exporting any out of box event handlers, value is oim.
# For rest of the out of box metadata, value is OIMMetadata.
# If you are importing or exporting any custom data, always use application name as OIMMetadata.
application_name=OIMMetadata
# Directory location from which XML file should be imported.
# Lets say I want to import User.xml and it is in the location /scratc/asmaram/temp/oim/file/User.xml,
# I should give from location value as /scratc/asmaram/temp/oim. Make sure no other files exist
# in this folder or in its sub folders. Import utility tries to recursively import all the files under the
# from location folder. This property is only used by weblogicImportMetadata.sh
metadata_from_loc=@metadata_from_loc
# Directory location to which XML file should be exported to
metadata_to_loc=D:/MDS
# For example /file/User.xml to export user entity definition. You can specify multiple xml files as comma separated values.
# This property is only used by weblogicExportMetadata.sh and weblogicDeleteMetadata.sh scripts
metadata_files=/metadata/iam-features-ldap-sync/LDAPUser.xml
# Application version
application_version=11.1.1.3.0
i get the following error
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting export metadata script ....
Please enter your username [weblogic] :weblogic
Please enter your password [welcome1] :
Please enter your server URL [t3://localhost:7001] :t3://hostname:7001
Connecting to t3://hostname:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'OIMDOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBea
n as the root.
For more help, use help(domainRuntime)
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\Oracle_IDM1\server\bin\weblogicExportMetadata.py";,
line 22, in ?
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 134, i
n exportMetadata
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 568, i
n executeAppRuntimeMBeanOperation
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 538, i
n getMDSAppRuntimeMBean
UserWarning: MDS-91002: MDS Application runtime MBean for "OIMMetadata" is not available. "exportMetadata" operation failure.
i have exported these files multiple times, it never gave an errror, but this time i see this error, please help.
Thanks in advance

Glad that worked.
Working with MDS, another way is to use the EM console for exporting/importing data from/to MDS. This I find lot easier rather than working with the OOTB script.
Steps are:
http://ADMINSTRATION_SERVER/em
Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.
Under Application Defined MBeans, navigate to oracle.mds.lcm, Server:oim_server1, Application:oim, MDSAppRuntime.
To export the configuration files:
•     Click the Operations tab, and then click exportMetaData.
•     In the toLocation field, enter /tmp or the name of another directory.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This exports the file specified in the docs field to the directory specified in the toLocation field.
To import the configuration files:
•     Click importMetaData
•     In the fromLocation field, enter /tmp or the name of the directory in which you have the configuration files.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element. For example, /db/oim-config.xml.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This imports the file specified in the docs field to MDS in the toLocation field.
HTH

Exporting Metadata (caption information) from JPEGS to a comma separated value (CSV) file

Here is my dilemma. I am an archivist at an arts organization and we are in the process of digitizing many of our materials to post them on the web and make them available to internet users. One of the principle components of our collection is a large trove of photographs. We have been in the process of digitizing these images and embedding metadata (in the Caption/Description, Author/Photographer and Copyright fields) via PhotoShops File Info command.
Now I am at a crossroads. We need to extract this metadata and transfer it into a comma separated value form, like an Excel spreadsheet or a FileMakerPro database. I have been told that it is not possible to do this through PhotoShop, that I must run a script through Acrobat or Bridge. I have no clue how to do this. I have been directed to a couple of links.
First I was directed to this (now dead) link: http://www.barredrocksoftware.com/products.html
The BSExportMetadata script allegedly exports the metadata from files selected in Adobe's Bridge into a comma separated value (CSV) file suitable for import into Excel, Access and most database programs. It installs as a Bridge menu item making it simple to use. The the Export Metadata script provides you with an easy to use wizard allowing you to select associated information about a set of images that you can then export. This script requires Creative Suite 2 (CS2). This script sounds like it does exactly what I want to do, but unfortunately, it no longer exists.
Then I found this:
Arnold Dubin, "Script to Export and Import Keywords and Metadata" #13, 8 Aug 2005 7:23 am
I tried this procedure, but nothing seemed to happen. I also tried to copy the script into the JAVASCRIPT action option in Acrobat, but I received a message that the script had an error. It also seems to me that this script does not set up a dumping point, that is, a file into which this information will be exported to.
I am a novice, not a code writer or a programmer/developer. I need a step-by-step explanation of how to implement this filtering of information. We have about 2000 jpeg and tiff files, so I would rather not go through each file and copy and paste this information elsewhere. I need to find out how to create a batch process that will do this procedure for me. Can anyone help?

Hello -
Is anyone aware of a tool that will do the above that is available for mac? Everything I've found so far seems to be PC only.
Any help is appreciated, thanks!

Importing the METADATA ONLY using DBMS_DATAPUMP

Hi DBAs,
Using the DBMS_DATAPUMP , how can I import the metadata only for a particular table . Also I dont want to import any associated INDEXES and TRIGGERS. I have the following codes but it is trying to import every thing. Also if the table exist, it is not importing the METADATA rather erroring out.
handle1 := DBMS_DATAPUMP.OPEN('IMPORT','SCHEMA', 'QAXDB.WORLD');
DBMS_DATAPUMP.METADATA_FILTER(handle1, 'SCHEMA_EXPR', 'IN (''HR'')');
DBMS_DATAPUMP.SET_PARAMETER(handle1, 'INCLUDE_METADATA', 1);
Thanks
-Samar-

See the below link,
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_datpmp.htm
Hope this helps,
Regards,
http://www.oracleracexpert.com
Click here for [Cross platform Transportable tablespace using Datapump|http://www.oracleracexpert.com/2009/08/transportable-tablespace-export-import.html]
Click here to learn [Oracle data pump export/import with examples.|http://www.oracleracexpert.com/2009/08/oracle-data-pump-exportimport.html]

Using XML Import/Export in Transport Connection

Hi, I was investigating the feasibility of copying a query definition from one BW system to another using the XML Import/Export functionality in Transport Connection. This is not to replace our current transport process across the landscape (Dev -> QA -> Prod), but merely just looking at possibilities for end users who develop queries in QA & then recreate them in Prod.
My question is: has anyone worked with the XML Export/Import for types Queries & Query Elements? I was trying this out between a Dev and Sandbox system and only had limited success. I was able to take a small query and perform the Export to a local .xml file without much difficulty. But when I try to do the Import, my query never shows up. The Import function shows a green light, but I get a couple of error messages on the Import such as the following:
==========================================================
SAP object 3WROG4HZ3NKP1PIYHCR1H24CQ () cannot be imported
Diagnosis
You attempted to import SAP object 3WROG4HZ3NKP1PIYHCR1H24CQ of type into the system via the XMI interface. However, you are not allowed to import SAP objects.
System response
The object was ignored during the import.
Note: It can be that the import is incomplete when the required SAP objects are still not active in the system.
Procedure
Install the specified objects from Business Content. Only import the metadata afterwards.
=========================================================
The portion returned for Saving and Activating returns green lights. The two sample objects mentioned appear to just be custom InfoObjects used in my query & don't look to be any different than others that work OK.
Just curious if anyone else has worked with this and could help advise.
Thanks... Jody

This is an old subject, but I think XML import only works for datamodeling objects like InfoObjects, InfoCubes, and ODS objects. If you try to export a query, and open the XML file in a text editor, there is not enough information (in my opinion) to build the query. As an example you don't see how key figures are to be displayed, filter or free characteristics.
However, when an InfoObject is collected, you get all the attributes, texts in all languages.
If anyone has more insight, please enlighten us.
-John

Is it possible to copy or export metadata from Folio Producer?

Hi,
Is it possible to copy or export metadata from one issue in Folio Producer and import/apply it to a different issue in Folio Producer? Or create a master metadata template that every issue build could use? It would save a lot of time and typing not having to re-enter the same information every month when releasing the next issue for departments, bylines, etc.
Thanks!

Bob,
Do you know when exporting metadata from Folio Producer will be available, and will it export directly to another rendition, or would it export to a sidecar.xml file?
The workflow my team prefers is to build our 1024x768 folio first, add metadata via Properties in the Folio Builder as we add articles, share the folio with editors and advertising sales, make edits and updates, then when all content is approved, create the 2048x1536 rendition folio using multiple importing of articles.
Having the ability to export from an existing folio in Folio Producer would save tons of tedious copying/pasting to get a sidecar.xml.
Hopefully when this becomes available you'll have a big announcement. (Please?)
Thanks in advance.
Mark

Exporting Metadata

I've created custom metadata views and presets for cataloging my images. Is it possible to export this metadata into an Excel spreadsheet as a CSV or TSV file? File/Export/Metadata exports standard metadata, but not my custom fields and entries. Or, is it possible to export XMP sidecar files and somehow import those into Excel? All that data is there somewhere within Aperture - please help me get it out and into a spreadsheet! Thanks.

You have to use some Applescript, but it's a relatively simple script.
tell application "Aperture"
set tSelection to the selection -- this gets all the Versions currently selected
set tValues to ""
repeat with i from 1 to number of items in tSelection -- now loop through selection
set tImg to item i of tSelection
set tValues to tValues & "Version Name: " & name of tImg -- add the name
try
set tValues to tValues & "Aperture: " & value of EXIF tag "ApertureValue" of tImg -- add the aperture
set tValues to tValues & tab -- replace with "," for comma-delimted values
end try
try
set tValues to tValues & "Shutter: " & value of EXIF tag "ShutterSpeed" of tImg
end try
set tValues to tValues & return -- make a new line for each image
end repeat
end tell
Copy and paste into Script Editor (in Applications/AppleScript) and hit the Run button, in the bottom pane you'll get the results. Note that you'll have to change 'EXIF tag' to 'custom tag' for your custom tags, and to 'IPTC tag' for IPTC data.
The 'try/end try' bits are in there so that the script doesn't fail if it comes up against an empty tag.
Ian

Import XMP Metadata From File

In Beta4, the Import XMP Metadata From File command would import data found in an xmp file.
In V1, it's not working...or am I missing something.
(I do understand that Export XMP to File will write the data into the image file itself.)
Ideas?
Pete

Here's a sample xmp I created...in case it's wrong..but it was working in B4. <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Toolkit 3.3-016, build -num-, -date-"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:dc="http://purl.org/dc/elements/1.1/"> <dc:description> <rdf:Alt> <rdf:li xml:lang="x-default">: Geese at sunset. Finley National Wildlife Refuge, Oregon</rdf:li> </rdf:Alt> </dc:description> <dc:creator> <rdf:Seq> <rdf:li xml:lang="x-default">Peter K. Ziminski</rdf:li> </rdf:Seq> </dc:creator> <dc:rights> <rdf:Alt> <rdf:li xml:lang="x-default">Peter K. Ziminski</rdf:li> </rdf:Alt> </dc:rights> <dc:subject> <rdf:Bag> <rdf:li>Sunrises and Sunsets</rdf:li> <rdf:li>Birds</rdf:li> <rdf:li>Landscapes</rdf:li> <rdf:li>Animals</rdf:li> <rdf:li>Oregon</rdf:li> <rdf:li>Finley National Wildlife Refuge</rdf:li> </rdf:Bag> </dc:subject> </rdf:Description> <rdf:Description rdf:about="" xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"> <Iptc4xmpCore:Location>Finley National Wildlife Refuge, Oregon</Iptc4xmpCore:Location> </rdf:Description> </rdf:RDF> </x:xmpmeta>

CMSDK import/export utility

Can the 9i CMSDK import/export utility be used to export the content of the an iFS 1.1.6 schema to subsequently import into a 9i database? Once imported into the 9i database, then migrate/upgrade the 9i iFS schema to CMSDK 9 for testing purposes?

Thank you for your advice Luis.
What I really need to be able to do is keep my iFS 1.1.6/RDBMS8.1.7.4 development environment intact, while creating a CMSDK/Oracle9i environment for regression testing. I have multiple iFS schemas (6) in our 8.1.7.4 dev database (source). And, what I would like to do is copy one of the iFS environments (including Metadata) out of source and move it into the CMSKD/Oracle9i environment(target). Both environments need to remain accessible, and the source environment needs to remain at version iFS1.1.6 / 8.1.7.4 for regression testing.
Here's a list of actions that I have taken:
1. install oracle9i rdbms software.
2. create 9i database from scratch.
3. install 9iAS software
4. install CMSDK software in 9iAS root.
5. export one iFS schema out of the dev source database. (Using the plain RDBMS export utility)
6. import this schema into the newly created Oracle9i database.
7. Run CMSDK configuration tool to upgrade the imported iFS 1.1.6 schema. <== FAILED HERE!!!!
I run into a problem at the start of the upgrade, when using the configuration tool. It complains that the credential manager username IFSSYS$CM does not exist and fails. So, I simply created a user called IFSSYS$CM in the 9i target database to see if this would allow the configuration tool upgrade process to progress and the result was another error of "Insufficient Privileges". How can manually set a the crediential manager so that the imported iFS schema can be upgraded successfully?
I realize that be doing an in-place upgrade of my entire Oracle 8i source database. I will be able to migrate both the RDBMS and iFS using the installation/configuration tools.
If there is a limitation of not being able to copy (credential manager metadata) an iFS 1.1.6 schema out of the source and into a target database, and then upgrading/migrating the schema to CMSDK/Oracle9i. Then I may be forced into cloning my entire development instance (giving it a different name) and then doing in-place migration of the entire cloned database (all 6 iFS schemas). Our source dev database is 18G and includes much more (probably garbage data) than will be needed for our regression testing. My hope was to take only a subset of the 18G (1 of the 6 iFS schemas) and move it into CMSDK/Oracle9i to perform the testing. We are very low on available disk space and taking only a subset would be a more efficient use.
I have even attempted to use the CMSDK export utility to export the iFS1.1.6 schema. I was hoping this would export the iFS1.1.6 schema, metadata, contents, and credential manager. This was not successful due to missing Java packages not installed in the Oracle8i (8.1.7.4 database).
These are all the details of my dilemma. Can you help guide me in the right direction. I've spent a lot time already fumbling through and have had a number of false starts with my proposed approach. I need someone to tell me the recommended way of approaching my issue. Thanks again.

Exporting Metadata to AE problem

Hi- Has anyone run into an issue with exporting metadata to AE? I imported an audio track and did a content analysis. I attached a text file and the speech recognition worked perfectly.
I exported the clip and brought it into After Effects, and the markers showed up with each word, just as planned. The problem is, many (but not all) the markers had duplicates, separated by 1 frame. Once I removed the duplicate markers, it was exactly what I was looking for.
Any idea whats going on?
Much thanks

Hi Bob and Happy 4th!
Thanks for replying.
I'm exporting the file, and everything works great and looks great. Have made first level new chapters, and each is now separate xhtml file. toc looks good. Only thing is the last chapter is not included (although the glossary after that is). If I rearrange the order of the chapters the one now in the last position doesn't make it to the epub. My guess is there is a limit on length or size, but from what I've read that shouldn't be a problem with numerous xhtml files in this version.
Thanks!

Migrating owb using import/export

Hi All,
Please could anyone throw some light on how to Migrate owb using import/export.
we are presently having owb installed on 32 bit database with RHEL 4 os. we planning to migrate to 64 bit database with 0el5 os.
we have planned to do export/import. my question in this is could we use export/import for migrating owb schemas with owb installed in the new server.
Thanks in advance,
Regrads,
Prajwal

Hi Prajwal,
I do not recommend exporting and importing the owb repository schema, it will not work properly.
First, create a new repository on the new db. Then export your projects (make sure you select include all dependencies) using owb metadata export and evetnually import it into the new database.
Note that you wil loose all deployment status information.
If you also have target schemas in your db, then unregister them first before migrating the data to the new db. In the new db you have to register them at the new repository. Finally you have to redeploy all mappings (using replace) in order to make them work again.
Regards,
Carsten.

Import export metadata

Similar Messages

Maybe you are looking for