Hi,
The ARXMLCreateEntry()-call was noted in the arapires/cmd.log files, I
have not seen it before. Maybe they have ARXML-equivalents for many of the
ordinary API-calls?
The dotnet-client was created on Mid-Tier 7.1/AR Server 7.1.
The dotnet-client was then moved to the Mid-Tier 7.1/AR Server 6.3 where
it does not work.
The Web Service itself was created on AR Server 6.3 and then imported into
the 7.1 system along with the rest of the form and workflow objects.
All the Web Services for reading, GetEntry and GetList, works fine. I have
not checked which API-calls those functions use.
BMC Remedy Support called us up and stated that there were known
compatibility issues between Mid-Tier 7.1 and AR Server 6.3, and that they
had no plans to fix this...
Best Regards - Misi, RRR AB, http://rrr.se
> Misi,
>
> A lot of questions in there.... let me see what I can do with some of
> them.
>
> ARXMLCreateEntry() is a new API call to me. However, I do find a Java
> method in the JavaDriver by that name. ( I wonder if it is the same
> method that you are talking about?) I do not see any docs on this
> method in any of the published PDF from BMC.
>
> "InputDoc" is defined in the C-APIGuide-630.pdf pg 113.
> And..
> "InputDoc" is defined in the C-API-Ref-710.pdf pg 97.
>
> ( and they look the same to me )
>
> My guess is this is the definition of the "InputMap" part of the Web
> Service XML doc. (Which is why I am skeptical that the client is
> sending a valid "ARS Web Service XML doc" to the server. However...
> you said it worked with a v7.1 Mid-Tier... So maybe they changed stuff
> that they did not document? or maybe the .Net client is doing
> something different due to a different WSDL from v7.1?)
>
> --
> 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 29, 2008 9:02 AM, Misi Mladoniczky <[EMAIL PROTECTED]> wrote:
>> Hi Carey,
>>
>> The working environment with the exact same definitions, orginiating
>> from
>> the 6.3 server, was Mid-Tier 7.1.0 patch 1 and AR Server 7.1.0 patch 1.
>>
>> The .net-developer then moved his code the customer network and accessed
>> the 6.3.0 patch 18 server through another Mid-Tier 7.1.0 patch 1
>> instance.
>> This is where it broke.
>>
>> We have not tested this with Mid-Tier 6.3 at all, but it is a very
>> simple
>> thing, so it will probably work.
>>
>> As the ARXMLCreateEntry() call returns a reference to "InputDoc" rather
>> than a specific Field ID, I feel that the API-call is somehow
>> incompatible.
>>
>> By the way, where is ARXMLCreateEntry() documented?
>>
>> What does "InputDoc" refer to? Is it the XML-code sent to the AR Server?
>> Why can't I see this data in my ARAPILOGGING=2 files?
>>
>> Where is the different values for ARAPILOGGING defined?
>>
>> The log file snippet was from the Mid-Tier log. I do not know why the
>> Authentication info etc is not there.
>>
>> For some reason we change the Element=True flag to False for
>> 'Mottagare',
>> 'Telefon' and 'Tilldelad_Grupp'. I do not think that this is the reason
>> for the failiure, but it is probably the reason for these fields ending
>> upp as attributes in ther ROOT-tag.
>>
>>
>> Best Regards - Misi, RRR AB, http://rrr.se
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
