OD-DD

In doing a OD-DD SYNC - I have this working but the following questions arise:

WHY DO THE TABLES WHICH I GENERATE
(IDEALLY I'D LOVE TO JUST KEEP THE SAME SHORTID NAMES BETWEEN DATABASES) HAVE DIFFERENT LONG_ID NAMES - EXAMPLE ON MY STAGING BOX THE LONGID's ARE ALL SIMILIAR TO THE FOLLOWING:

DEFAULT_ABOUT_US_ABOUT_US__ABOUT_US__MAIN_WORKAREA

HOWEVER AFTER I RUN DDSYNC.IPL - THE TABLE NAMES GET GENERATED AS SUCH ON OUR PRODUCTION DATABASE:

ABOUT_US_ABOUT_US__ABOUT_US_KEY

THUS - THE FIRST AND LAST SECTION OF THE NAME GET TRUNCATED - WHY?

IT APPEARS THE DDSYNC.IPL - IS A VERY WATERED DOWN VERSION OF IWSYNC.IPL OR SHOULD I SAY IT APPEARS THAT DDSYNC.IPL IS A ONE-OFF JUST FOR SYNCS?

ALSO - CAN SOMEONE TELL ME WHY THE TYPE IN MY IWOV_IDMAPS TABLE IS 4 AFTER I RUN A OD-DD SYNC -
EVERYWHERE ELSE THIS TYPE IS 1?

I must say and Mr. Scallon if your reading this - the od-dd sync documentation is terrible - I will e-mail you when I get a chance all the inconsistent information I've found - your really left to guess a lot of this information yourself - instead of having a clear cut methodlogy - thus far the od-dd documentation is the most vague I've read - I can't believe I've gotten as far as I have - (3 full days to figure this stuff out - and support isn't up on the best practices for the od-dd sync at all!)

Thanks

Find more posts tagged with

Comments

Migrateduser

Kevin,

In general, the OD-DD sync process is being looked at to see how set-up and usage can be improved. But in the meantime, I'll look forward to receiving your email with comments on the OD-DD documentation. If you wouldn't mind, please also include any details about your use case regarding synchronized deployments. That kind of info is very helpful to the product team. Thanks.

I'll also touch base with Tech Support on the issue of supporting OD-DD cases.

Cheers,
Todd

Todd Scallan
Senior Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

You probably created the tables
DEFAULT_ABOUT_US_ABOUT_US__ABOUT_US__MAIN_WORKAREA and
DEFAULT_ABOUT_US_ABOUT_US__ABOUT_US__MAIN_STAGING using DAS.
DAS table naming conventions uses the store name (DEFAULT) and the AREA name (MAIN_WORKAREA or MAIN_STAGING) and the datacategory datatype name (templating or metadata types ) since its associated with a specific datatype which is present in a particular area in the Teamsite filesystem.
As far as the type 4 in your IWOV_IDMAPS it stands for a constraint name so maybe you have a constraint created during your table creation. Check your log files to see what constraint was created.