Skip to main content
1-Visitor
June 21, 2012
Question

Bursting Configuration

  • June 21, 2012
  • 15 replies
  • 6342 views

Hello All, new to the board, so any advice would be appreciated.


I'm trying to recreate our parent company's approach to our PTC solution, however our communication with them is limited.


In doing so, I can begin to revise their approach and procedures for our needs and build our Windchill ditabase. We receive their XML files for our manuals, and I obtained a copy of their custom folders with their stylesheets. I also received their bursting rules. When I try to burst a book from the map level, it comes back with an error saying, "Cannot modify the following attributes: lang, because they are not defined. I'm still a novice, although I have gone through all the AE and WC PTC courses I can go through, but I'm not sure where to fix this issue. The attributes are defined in the bursting rules, I see language under the attribute root in the Type and Attribute Mgr in WC, and it is a valid element attribute in the dcf. Where shouldI look, or should I post this in a better suited forum?


Thanks


Another question. If you're realtively new to the PTC family, and you have gone through AE, WC and Styler courses from PTC and read through a lot of their manuals, where would you look next for additional training and understanding? A lot of these courses teach basic application, but not understanding of what to do.


Thanks again!

    15 replies

    1-Visitor
    June 21, 2012
    I don't think there are a lot of hands-on, button-clicking classes you can take. Probably one of the best things you can do is what you are doing right now: ask the Adepters. Trial-and-error and asking questions here may turn out to be your best bet.
    10-Marble
    June 21, 2012
    Hi Bryon,

    You may need to upload the burst config file(s) to the Windchill
    server from Editor (Save as Server Object), usually in a Library
    that other users also have access to.

    Regards,
    Richard

    1-Visitor
    June 21, 2012

    I might try that. Up until now, I have been using the APTOBJCFG environment variable.


    I'm responsible for the Windchill server test, and I have hesitated uploading the burst files to windchill at the moment. The reason is, once I successfully upload books to windchill using my parent's system, I plan to blow them away and reconfigure the bursting rules and dita filesto build a simpler, more reusable library. Unfortunately, our parent company bursted their files too deeply for acceptable reuse on our part. Although, I could upload the burst files and change them over, I just didn't want to add another variable to the plate.


    Is there a difference in using the environment variable versus uploading the burst files to windchill?


    Thanks

    15-Moonstone
    June 22, 2012
    Thomas,

    You have checked for the attribute in three places:


    1. In the bursting rules (in a section like the following):
    <dmsobjtype>
    <typerule elementname="topic" targettype="WCTYPE|wt.epm.EPMDocument|PREFIX.DynamicDocument|PREFIX.Topic"/">
    </dmsobjtype>

    <dmsmetadata>
    <metadatarule elementname="topic" expr="@xml:lang" metadata="lang"/">
    </dmsmetadata>


    2. In the Attribute Manager in Windchill (it has a name, internal name, and description)

    3. In the .dcf

    There is a fourth place where you should reference it: in an actual type defined in the Type Manager in Windchill: just defining an attribute is not enough, you should also tell Windchill in which types that is attribute used.
    In this example a topic is burst as a PREFIX.Topic type in Windchill (see burstspec snippet above), hence this type should use that attribute: you need to add a global attribute to that type, picking the attribute defined in the Attribute Manager.
    The rationale for having first to define an attribute in the Attribute Manager, and then reference it from a Type, is that you might want to reuse the same attribute in multiple types with different constraints for each type.

    See Help Center:

    * Windchill 10.0:
    16-Pearl
    June 22, 2012
    Hi Bryon,

    I'm pretty sure APTOBJCFG is only for pointing to atidefaults.xml which is the basic bursting defaults. The doctype-specific burst rules are usually in the doctype folder itself (as a .bcf file) or as Richard said up in Windchill.

    Cheers,
    Gareth
    1-Visitor
    June 22, 2012
    Alessio,
    Saw your response - thank you for taking this time to help!
    Cindy
    18-Opal
    June 22, 2012
    Hi Gareth--



    Actually, if APTOBJCFG is defined, then that's the ONLY place the
    Windchill adapter will look for ANY burst rule files. If it's defined,
    then any burst rule files that are checked into Windchill are ignored.



    To see what burst rule files are actually loaded by the adapter:



    1) Establish the WC connection from Arbortext Editor

    2) On the Arbortext command line, type
    "response(wcconfig::findBurstConfigFiles())"



    That can help you determine if you are inadvertently loading the wrong
    burst config files.



    --Clay





    Clay Helberg

    Senior Consultant

    TerraXML


    1-Visitor
    September 29, 2016


    Hi Clay

    How do I use TerraXML to automatically burst documents in Windchill?

    16-Pearl
    June 22, 2012
    Hi Clay,

    Great debugging tips!

    I don't know if it's relevant to the OP or not but I checked one of our projects and it seems APTOBJCFG may be used in conjunction with regular doctypes .bcf files. Eg. we have an atidefaults in the location indicated by APTOBJCFG and the adapter is also picking up doctype-specific burst files from the relevant doctypes folder in the APTCUSTOM location.

    -G
    18-Opal
    June 22, 2012
    Hi Gareth--



    That's interesting, I'd like to see how that works. If you look at the
    code in wcconfig.acl (in adapters/com.ptc.prowt.arbortext/init), you can
    see that it explicitly skips looking anywhere else when APTOBJCFG is
    defined. I'd be curious to see the output of the command I mentioned for
    that project to verify that it's picking up the burst config files from
    both APTOBJCFG and the doctype directories.



    --Clay



    Clay Helberg

    Senior Consultant

    TerraXML


    1-Visitor
    June 22, 2012

    Alessio,


    Thanks for the tip. I tried that, and it didn't work. Not your fault, I checked the lang attributes in the xml book, and noticed there was 1 that was an undeclared .psu file for british. I reverted the profile back to the original (I translated it from japanese), and that error stopped popping up (the undeclared element is still there, but it can't understand the profiling so I don't think it's trying to anymore).


    However, since this book is a zipped book from the parent company's windchill, the files are still saying they are dependent on each others revision levelsto upload (Since some pulled from different books). Here is an example below. How do I prevent the books from carrying this, since for my new database they would all be A.1 anyway? The error comes back with a different referenced file every time, I assume because they are all dependent.


    Also, would my windchill have a problem if the master language defined in wc is english, and the master language of the xml files was japanese (translated to english as xml:lang=en)?