‘non-default' Schemas

I would like to ask again my earlier question (https://community.emc.com/thread/121561) again because it is important for me:

I would like to understand what are ‘non-default Schemas’ on ‘full’ (non-Developed Edition) Documentum servers? Because of my application will eventually run on these ‘full’ servers. It turns out, a Documentum server can have, in addition to default Schema, also several other Schemas? Will these non-default schemas be used in parallel with the default one? If so, how this will look like - I cannot imagine? Where can I read more about this?

Find more posts tagged with

Comments

DCTM_Guru

I believe what you are asking is related to other database tables. You can have non-default (system generated) tables to store application data. For example, you may want to populate lookup table for customer ID list. This design pattern was more prevalent in the days before web services and the easiest way to exchange data between two systems was via database tables. Once you create the tables within the Documentum schema instance, you just need to "register" it so that it is recognized by DQL. This may have been the issue with your other post.

GlenLantz

Thank you for the response,

Well, my application needs to know TypeInfo of dm_document and its children. The DFS requires to specify Schema for that. From your words I conclude: for this given task I need the ‘default Schema’ only, correct?

DCTM_Guru

I presume so, but then again I havent program much with DFS.