http://www.nnseek.com/e/ibm.software.websphere.business-integration.modeler/ Posts for ibm.software.websphere.business-integration.modeler Wed, 22 Nov 2006 08:58:07 PST http://www.nnseek.com/ http://www.nnseek.com/img/64.png 64 64 NNSeek http://www.nnseek.com/e/ibm.software.websphere.business-integration.modeler/mainframosaurus_encounters_problems_installing_ibm_6452015t.html http://www.nnseek.com/e/ibm.software.websphere.business-integration.modeler/mainframosaurus_encounters_problems_installing_ibm_6452015t.html to frequent before.

Our team determined that we need to install the software specified in
the title on one of our machines.

I downloaded the install package and we expected a one-click
installation. Instead, in the Installation Guide we find a list as long
as your arm of pre-reqs and detailed step-by-step instructions on how to
proceed.

I easily got past the allocation of a static IP address.

Creation of a UserID was optional, so an existing administrator was used
as instructed and was able to skip over a load of requirements for the ID.

Then I was instructed to create a db2admin ID. This time, it explicitly
stated that:

This user must have administer rights *and* (my highlight) have the
following policies:

* Act as part of the operating system
* Create a token object
* Log on as a service
* Replace a process level token

I have asked the best-qualified person in my department what these mean
and his eyes glazed over, just like mine.

Can anybody offer help or direction to this Mainframe dinosaur?

All help gratefully received.

Neil Adamson
Hursley
7-246549

Posted In: ibm.software.websphere.business-integration.modeler

1 Comment

Reply

]]> Wed, 22 Nov 2006 08:58:07 PST http://www.nnseek.com/e/ibm.software.websphere.business-integration.modeler/business_modeler_xml_problems_19320879t.html http://www.nnseek.com/e/ibm.software.websphere.business-integration.modeler/business_modeler_xml_problems_19320879t.html
I am writing a program which generates XML for import into WebSphere
Business Modeler, using the schema provided with version 6 under
samples/impor/xml/wbimodeler.xsd. The first problem is that upon importing I
am getting errors that the document is not valid, in the past this was
usually a mistake and sure enough when I found it the document did not
conform to the schema. I have isolated the current problem to the addition
of an associatedData attribute being added to an output tag, but only when
it is an output of a Decision. The schema makes no reference to this being
invalid and sure enough the associated Data attribute is quite fine to add
to any other output anywhere else. If I remove it the import will complete
but then there is another problem. According to documentation within the
schema outputs must be listed in the same order as inputs with the same
data, but how can i do this when I am not allowed to associate data?
Apparently the answer is it gets decided for me upon import according to the
order the tages are actually found in the file. This presents a problem
because now a piece of data has been associated to it within the program,
but my XML may contain a connection that tries to connect this output to
another input which has a different piece of data associated to it and thus
no connection occurs. Maybe I'm missing something but I feel if I write XML
that conforms to the schema it should be imported, and successful import
should not rely on the order of children under a parent tag as that is
against the concept of XML. I'd be really happy to hear some advice on how
to proceed even if it is just a work-around.

Thanks.

Justin Everett

Posted In: ibm.software.websphere.business-integration.modeler

no comments

Reply

]]> Tue, 22 Aug 2006 13:30:18 PDT