Misi,

That is truly a sad report. ( What happened to the "promise" of a
backwards/forwards compatible API and clients? What happened to
support of 2 full versions back? Sigh... but I digress.... )

On the other hand... that snip of XML really does not look right to
me. Have you tested your WebServices client against a v6.3 Mid-Tier
and proved that it worked in with that Mid-tier? And it breaks when
you ONLY point it as the v7.1 Mid-Tier? (If so, then I have some
adjustments that need to be made in our environment too. <sigh>)

"
2008-jan-25 09:19:28 - FINE (com.remedy.log.WEBSERVICES) : input document:
 <?xml version="1.0" encoding="UTF-8"?>
 <ROOT Mottagare="MinSida" Telefon="-" Tilldelad_Grupp="-"
xmlns="urn:MinSida_HD">
 <Kategori>Mjukvara</Kategori>
 <Omrade>Bestallning</Omrade>
 <Typ>Licens RK/UM-LAN</Typ>
 <Arendemening>test</Arendemening>
 <Detaljbeskrivning>test</Detaljbeskrivning>
 <Login_id>FA_URT</Login_id>
</ROOT>
"

I would have expected something more like...

"
2008-jan-25 09:19:28 - FINE (com.remedy.log.WEBSERVICES) : input document:
<?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
    <SOAP-ENV:Header>
    <AuthenticationInfo>
    <userName>user_name</userName>
    <password>pwd_str</password>
    <authentication/>
    <locale/>
    <timeZone/>
    </AuthenticationInfo>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <namesp1:OpGet xmlns:namesp1="ws1">
    <Case_ID xsi:type="xsd:string">ABC00000000001</Case_ID>
    </namesp1:OpGet>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
"

But maybe the mid-tier log is only showing part of the XML that is
actually being sent? Maybe it is incorrectly parsing XML like the
example above? ( I do not see the "OpGet" or "Op***" element in your
log that I would expect to see in a valid ARS XML WebService doc.)

-- 
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.



On Jan 28, 2008 10:20 AM, Misi Mladoniczky <[EMAIL PROTECTED]> wrote:
> Hi,
>
> BMC Support has informed us that the specific combination MidTier 7.1 /
> Web Services / AR Server 6.3 has known errors, and that they have no plans
> to fix the issue.
>
> I will try to get the customer to upgrade to AR Server 7.1, or possibly to
> downgrade MidTier...
>
>         Best Regards - Misi, RRR AB, http://rrr.se
>
>
> > Hi,
> >
> > We have published an AR System Web Service for creating tickets.
> >
> > ERROR (326): Required field cannot be reset to a NULL value; InputDoc
> >
> > The above error is shown in the browser. Usually there should be a field
> > ID appended rather than the InputDoc.
> >
> > Note that Get and GetList operations works fine, it is the Create
> > operation we have a problem with!
> >
> > The develpment environment worked with the following setup:
> > Windows, AR Server 7.1.0 patch 1, Mid Tier 7.1.0 patch 1, Tomcat
> >
> > The test environment has the following setup:
> > Windows, AR Server 6.3.0 patch 18, Mid Tier 7.1.0 patch 1, Tomcat
> >
> > The problems seems to be related to the server version. Does anyone have
> > any input on the configuration?
> >
> > It looks like the mapping from version 7.1 to 6.3 of the
> > ARXMLCreateEntry()-call does not work. The InputDoc may be blank or
> > something like this.
> >
> > I set up ARAPILOGGING=1 and 2 on the MidTier-server. This gave us the
> > following output:
> >
> > ### arapicmd.log ###
> >
> > #
> > # ARXMLCreateEntry
> > #
> > xmlce
> >
> > ### arapires.log ###
> >
> >    ARXMLCreateEntry results
> > Return Code: ERROR
> > Status List: 1 items
> > Status Struct:
> >    Message type: ERROR
> >    Message number: 326
> >    Message: Required field cannot be reset to a NULL value
> >    Appended: InputDoc
> >
> > ### armidtier.log ###
> >
> > 2008-jan-25 09:19:28 - FINE (com.remedy.log.WEBSERVICES) : input document:
> >   <?xml version="1.0" encoding="UTF-8"?>
> >   <ROOT Mottagare="MinSida" Telefon="-" Tilldelad_Grupp="-"
> > xmlns="urn:MinSida_HD">
> >   <Kategori>Mjukvara</Kategori>
> >   <Omrade>Bestallning</Omrade>
> >   <Typ>Licens RK/UM-LAN</Typ>
> >   <Arendemening>test</Arendemening>
> >   <Detaljbeskrivning>test</Detaljbeskrivning>
> >   <Login_id>FA_URT</Login_id>
> > </ROOT>
> > 2008-jan-25 09:19:28 - SEVERE (com.remedy.log.WEBSERVICES) : AxisFault :
> > ERROR (326): Required field cannot be reset to a NULL value; InputDoc
> >
> >         Best Regards - Misi, RRR AB, http://www.rrr.se
> >
> > Products from RRR Scandinavia:
> > * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> > * RRR|Translator - Manage and automate your language translations.
> > Find these products, and many free tools and utilities, at http://rrr.se.
> >
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to