Maximo Open Forum

I've added a customization archive to MAS, everything worked (I think, not sure if the class files were added.. if anyone knows of an easy way to see the class files, please share that info) I can see the database changes that are outlined in the dbc file, and the maxvars variable indicates the archive was processed successfully.

I'm now adding an additional customization archive that builds on the first archive, but it's never processed.

The customer.xml for the first archive is below.  After processing, the maxvars variable MYCUSTOMIZATION has the value "V8000-01".

<?xml version="1.0" encoding="UTF-8" ?>
<product  xmlns="http://www.ibm.com/maximo/product.xml">
    <name>My Customization</name>
    <version>
        <major>8</major>
        <minor>0</minor>
        <modlevel>0</modlevel>
        <patch>0</patch>
        <build>20710413-0001</build>
    </version>
    <dbmaxvarname>MYCUSTOMIZATION</dbmaxvarname>
    <dbscripts>customization</dbscripts>
    <dbversion>V8000-01</dbversion>
    <lastdbversion>V8000-00</lastdbversion>
    <extensions>
    </extensions>
</product>

The customer.xml for the second archive is below.  This one is never processed.  The dbc files V8000-02 to V8000-10 are in the customization archive zip file.  Can anyone see what I am doing wrong, and why this second archive is being ignored?

<?xml version="1.0" encoding="UTF-8" ?>
<product  xmlns="http://www.ibm.com/maximo/product.xml">
    <name>My Customization</name>
    <version>
        <major>8</major>
        <minor>0</minor>
        <modlevel>0</modlevel>
        <patch>0</patch>
        <build>20710413-0002</build>
    </version>
    <dbmaxvarname>MYCUSTOMIZATION</dbmaxvarname>
    <dbscripts>customization</dbscripts>
    <dbversion>V8000-10</dbversion>
    <lastdbversion>V8000-01</lastdbversion>
    <extensions>
    </extensions>
</product>

An update: The maxinst log file has the error listed below.  8000_02.dbc does exist, and it's in the correct place in the customization archive zip file.  It's in the same location as 8000_01.dbc, in the initial archive that worked.

------------------------------
Jose Nodeland
JedaWorks
------------------------------

Resolved... when creating the zip file, the folder structure was not correct... moral of the story, don't rush.