OIR and burst configuration files not working

Sure, please tell me what you notice.

(OIR) dynamicdocument.xml

<AttributeValues objType="com.SAMPLE.DynamicDocument">
<!-- set the number to a generated number -->
<AttrValue id="number"
algorithm="com.ptc.windchill.enterprise.revisionControlled.server.impl.NumberGenerator">
<Arg>{GEN:wt.enterprise.SequenceGenerator:EPM_seq:10:0}</Arg>
</AttrValue>
<!-- specify AttrConstraint tag -->
<AttrConstraint id="number"
algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
<Value
algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>
<Value
algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>
</AttrConstraint>
</AttributeValues>

<?xml version="1.0" encoding="UTF-8"?>
<!--Arbortext, Inc., 1988-2013, v.4002-->
<!DOCTYPE createdefaults PUBLIC "-//Arbortext//DTD CreateDefaults 1.0//EN"
 "createdefaults/createdefaults.dtd">
<!-- atidefaults.xml

This file contains 'global' defaults for object creation
parameters, i.e. these settings are applied independently
of the DTD/Schema when no user-defined or DTD/Schema-specific
setting is available.
-->
<!-- createdefaults

NOTE:

If the 'useroverride' attribute has a value of "on" then the
user will be in full control of where new objects are located.
All settings in this file or in a DTD/Schema-specific configuration
file will be ignored in this case. Such settings are only honored
if 'useroverride' is "off".
For compatibility with earlier releases, the twowaymetadata feature is 
disabled by default. The feature must be enabled (twowaymetadata="on") 
for twowaymetadatarule elements in DTD/Schema-specific configuration
files to work. 
-->
<createdefaults maxnamelen="72" objectreuse="on" twowaymetadata="on"
useroverride="on">
<!-- dmsobjtype dmsgraphicobjtype

A 'default' attribute value of the dmsobjtype or dmsgraphicobjtype
elements can be used to control the soft type which will be used
when new objects are created in Windchill. This setting will only
be used if the equivalent DTD/Schema-specific setting is absent.

The 'default' attribute must specify a fully-qualified
soft type name which derives from DynamicDocument
(which is a built-in type deriving from EPMDocument).

The format of this attribute is as follows:

wt.epm.EPMDocument|<child-name-1>| ... |<child-name-N>

Each component must specify the 'Name' of each soft type
(not the 'Display Name') as given in the Type Manager
interface. An example 'default' attribute value follows:

wt.epm.EPMDocument|com.acme.DynamicDocument|com.acme.CustomType
-->
<dmsobjtype default=""/>
<dmsgraphicobjtype
default="wt.epm.EPMDocument|com.irobot.DynamicDocument|com.irobot.Graphic"/>
<!-- dmslocation

A 'default' attribute value of "" indicates to use the home
directory of the Context associated with the workspace the
user selected during login.
-->
<dmslocation default="">
</dmslocation>
<dmsgraphiclocn default="/Wilsonville Products/User Documentation"/>
<defaultnamecriteria>
<namerule rule="division-head-content"/>
<namerule rule="element-content"/>
<namerule rule="element-name"/>
</defaultnamecriteria><?Pub Caret -2?>
</createdefaults>

bookmap.bcf

<?xml version="1.0" encoding="UTF-8"?>
<!--Arbortext, Inc., 1988-2013, v.4002-->
<!DOCTYPE createdefaults PUBLIC "-//Arbortext//DTD CreateDefaults 1.0//EN"
 "createdefaults/createdefaults.dtd">
<!-- atidefaults.xml

This file contains 'global' defaults for object creation
parameters, i.e. these settings are applied independently
of the DTD/Schema when no user-defined or DTD/Schema-specific
setting is available.
-->
<!-- createdefaults

NOTE:

If the 'useroverride' attribute has a value of "on" then the
user will be in full control of where new objects are located.
All settings in this file or in a DTD/Schema-specific configuration
file will be ignored in this case. Such settings are only honored
if 'useroverride' is "off".
For compatibility with earlier releases, the twowaymetadata feature is 
disabled by default. The feature must be enabled (twowaymetadata="on") 
for twowaymetadatarule elements in DTD/Schema-specific configuration
files to work. 
-->
<createdefaults maxnamelen="72" objectreuse="on" twowaymetadata="on"
useroverride="on">
<!-- dmsobjtype dmsgraphicobjtype

A 'default' attribute value of the dmsobjtype or dmsgraphicobjtype
elements can be used to control the soft type which will be used
when new objects are created in Windchill. This setting will only
be used if the equivalent DTD/Schema-specific setting is absent.

The 'default' attribute must specify a fully-qualified
soft type name which derives from DynamicDocument
(which is a built-in type deriving from EPMDocument).

The format of this attribute is as follows:

wt.epm.EPMDocument|<child-name-1>| ... |<child-name-N>

Each component must specify the 'Name' of each soft type
(not the 'Display Name') as given in the Type Manager
interface. An example 'default' attribute value follows:

wt.epm.EPMDocument|com.acme.DynamicDocument|com.acme.CustomType
-->
<dmsobjtype default=""/>
<dmsgraphicobjtype
default="wt.epm.EPMDocument|com.irobot.DynamicDocument|com.irobot.Graphic"/>
<!-- dmslocation

A 'default' attribute value of "" indicates to use the home
directory of the Context associated with the workspace the
user selected during login.
-->
<dmslocation default="">
</dmslocation>
<dmsgraphiclocn default="/Wilsonville Products/User Documentation"/>
<defaultnamecriteria>
<namerule rule="division-head-content"/>
<namerule rule="element-content"/>
<namerule rule="element-name"/>
</defaultnamecriteria><?Pub Caret -2?>
</createdefaults>