Search results for query: *

can provide ..... 1) better utilisation of available cpu's and server resources 2) more control of configuration of each event server so it can be tuned for a specific purpose. 3) ability to stop parts of processing with switch off all launcher functions. 4) more opportunity for headaches when...

Scrap that post. That teaches me not to read IBM documentation during hours of darkness.

We are on 6.7.1 on windows now and looking to do an upgrade without recompiling everything (long list of reasons). It looks like 8.1 and 8.2 don't support older version maps running in the event server - thats according to the Whats New docs. Which 8.0* build is considered stable by those...

There is an R/3 extender pack. Its changing from 8.2 onwards by the looks of it but the information you require is here http://www-306.ibm.com/software/integration/wdatastagetx/entpacks/

These are different product sets with a little overlap. Gentran is an Edi Partner Manager with the ability to transform data from any Edi standard to a flat file format. It provides the connect layer to the VAN. Its ability around XML appears poor. Mercator is purely a data transformation...

I have used the following to override an MQ output "-OMMQS1K'"+GETDIRECTORY()+"KIMeta_Listed_"+ FROMDATETIME(CURRENTDATETIME("{CCYYMMDDHH24MMSS}"))+"_O10.bak' '-qmn ROUTER.V15 -qn APP_TO_ROUTER -dh' " I'd imagine this would translate to "-ID1KU'd:\mydirectory'" or "-ID1KU'd:\mydirectory\'"

Hi Has anyone run 8.x on 64bit Windows 2003 at all? I do realise WTX is a 32 bit app. Thanks Tim

janhes I using a get("java" command and the problem arises in both Event Server and Command Server. I thought the JVM options were only available in 7.5 and we are on 6.7.1 at present. Tim

Hi Using 6.7.1 on Windows and having a problem passing larger chunks of data to a java class. The problem appears to be that the data exceeds the jvm heap size but we can't find anywhere to put the options to set the max and min. Found details of solutions for v7.5 in thread842-1123436 but...

Hi What version of Xerces is supported in WTX 8.1 and is only the version bundled with the product or can we point to another version on the server Thanks Tim

We had problems with sticking idocs very early on in using it. We are now on version 6.7.2(342_ec87746) on a Windows platform. We don't use load balancing. That suggests there are later patches available that you have deployed (even given the different platform). Have you tried producing rfc...

We were looking to see what our options were moving on from the Event Server. Message Broker is one option but there are other ESB style products deployed here that could do just the job. Thanks for the reply Olly.

Does anybody used the extender pack for Web Services on 6.7 or above? If so could you give some feedback. In what environment is it deployed, how good is the wsdl support, performance etc etc Anybody else service enabled their Mctr in another way? Thanks Tim

On Windows you can get 2 Event Servers running using the same .msl's and you get double triggering. With MQ one of the maps will work ok and the other will fail often siting MQ connection error -13 and map error 12 (source not available) I'm not sure what the requirement is for increasing from...

What version and platform are you running, do you have the relevant patches for that release for the ale component? What do you count as high volume? We process about 10,000 from SAP per day with no issues on 6.7.1+, Wink2k tim

We have had this problem a long time in the past and it was caused because we had miss configured the queue manager (according to the wtx manual). The QM maxhands setting should be >1024 while the default is 256 (I think). If the QM is busy it may not be able to keep track of all the threads in...

We are also planning a move from 6.7.1 to 8.x on a windows platform. We are only going to recompile the utility maps used by all users (routing, logging etc), not the individual transformations at this point. We will test the non recompile strategy and if it is successful will save us 6 months...

IBM do have a defined roadmap for the product but its not published yet. Olly's comments are all the in the ball park from what I know. Its likely to be Q1 2009 before a totally seamless solution is in place.

6.7.1 is still supported - assuming mainternance support has been paid - as no end of life date has been published yet. We thought it was to be eol in April 08 but that has never been confirmed

We have a number of MQ queues being monitored and when the load is heavy enough for the InitPendingHigh and Low settings to be used it appears that the queues are processed in alphabetical order. For example if there are 100 messages on 2 queues and the InitPendingHigh is 90 then all messages...