I found the error by myself.
the bug was that I added a variable named sqlString to the parameterlist.
If a variable (which will keep the complete SQL-String) is defined in the SQL-Field, it is automatically added by webMethods into the parameter Input List. You don’t have to add this parameter manually.
So the correct steps are:
a.) place a SQL-Variable into the SQL-Field e.g. ${sqlString}
b.) webMethods adds automatically this variable to the Input-List
c.) run the service. It will ask for input adapterservice/sqlString
of course in previous steps the sqlString may be generated dynamically by various conditions.
It would be a good job for webMethods to give more detailed examples and information in the JDBC-Adapters Guide.
hope this helps someone
#Integration-Server-and-ESB#Adapters-and-E-Standards#webMethods