Hi Hannes,
I have replied to your email too with the screenshot of how to enable logging.
The Text...for 801367
<b>Caution:</b> This refers to the old text. SAP may be releasing a new one.
<i>Symptom
The JDBC Adapter documentation states that parameter settings
for the parameter table in the "advanced mode" section of the
configuration are documented via OSS note.
Other terms
J2EE XI 3.0 30 Adapter Engine JDBC Adapter
Reason and Prerequisites
You are looking for additional parameter settings. There are two
possible reasons why a feature is available via the "additional
parameters" table in the "advanced mode" section of the configuration,
but not as documented parameter in the configuration UI itself:
o Category 1: The parameter has been introduced for a patch or a SP
upgrade where no UI upgrade and/or documentation upgrade was
possible. In this case, the parameter will be moved to the UI and
the documentation as soon as possible. The parameter in the
"additional parameters" table will be deprecated after this move,
but still be working. The parameter belongs to the supported
adapter functionality and can be used in all, also productive,
scenarios.
o Category 2. The parameter has been introduced for testing
purposes, proof-of-concept scenarios, as workaround or as
pre-released functionality. In this case, the parameter may or
may not be moved to the UI and documentation, and the
functionality may be changed, replaced or removed. For this
parameter category there is no guaranteed support and usage in
productive scenarios is not supported.
When you want to use a parameter documented here, please be aware to
which category it belongs!
Solution
The following list shows all available parameters of category 1 or 2.
Please note:
o Parameter names are always case-sensitive! Parameter values may
be case-sensitive, this is documented for each parameter.
o Parameter names and values as documented below must be used
always without quotaton marks ("), if not explicitly stated
otherwise.
Page 2
o The default value of a parameter is always chosen that it does
not change the standard functionality
JDBC Sender Adapter Parameters
1. Parameter name: "normalizeFieldNames"
Parameter type: boolean
Parameter value: true for any capitalization of the string "true",
false otherwise
Parameter value default: false
Available with: SP11 Patch 5 and SP12 Patch 1
Category: 2
Description:
Assume a scenario involving a JDBC Sender communication channel to
select table rows from a database. The table's column names might
contain characters (e.g. a forward slash), which are not allowed
within XML element names. By default, the JDBC Adapter uses these
column names as is when building the query result XML document. This
results in the creation of an invalid XML response document.
In order to maintain backward compatibility with existing
implementations that rely on the old element name generation scheme,
a configuration change is required to activate the new element
naming convention. By configuring the advanced mode parameter above,
any invalid characters that would become part of an XML element name
are replaced with an underscore ("_") character.
JDBC Receiver Adapter Parameters
2. Parameter name: "logSQLStatement"
Parameter type: boolean
Parameter value: true for any string value, false only for empty
string
Parameter value default: false (empty String)
Available with: SP9
Category: 2
Description:
When implementing a scenario with the JDBC receiver adapter, it may
be helpful to see which SQL statement is generated by the JDBC
adapter from the XI message content for error analysis. Before SP9,
this can only be found in the trace of the JDBC adapter if trace
level DEBUG is activated. With SP9, the generated SQL statement will
be shown in the details page (audit protocol) of the message monitor
for each message directly.
This should be used only during the test phase and not in productive
scenarios.
________________________________________________________________________
Page 3
Valid releases
Software Component Release
from to
SAP-XIAFC XI ADAPTER FRAMEWORK CORE
3.0 - 3.0
<i> Symptom
The JDBC Adapter documentation states that parameter settings
for the parameter table in the "advanced mode" section of the
configuration are documented via OSS note.
Other terms
J2EE XI 3.0 30 Adapter Engine JDBC Adapter
Reason and Prerequisites
You are looking for additional parameter settings. There are two
possible reasons why a feature is available via the "additional
parameters" table in the "advanced mode" section of the configuration,
but not as documented parameter in the configuration UI itself:
o Category 1: The parameter has been introduced for a patch or a SP
upgrade where no UI upgrade and/or documentation upgrade was
possible. In this case, the parameter will be moved to the UI and
the documentation as soon as possible. The parameter in the
"additional parameters" table will be deprecated after this move,
but still be working. The parameter belongs to the supported
adapter functionality and can be used in all, also productive,
scenarios.
o Category 2. The parameter has been introduced for testing
purposes, proof-of-concept scenarios, as workaround or as
pre-released functionality. In this case, the parameter may or
may not be moved to the UI and documentation, and the
functionality may be changed, replaced or removed. For this
parameter category there is no guaranteed support and usage in
productive scenarios is not supported.
When you want to use a parameter documented here, please be aware to
which category it belongs!
Solution
The following list shows all available parameters of category 1 or 2.
Please note:
o Parameter names are always case-sensitive! Parameter values may
be case-sensitive, this is documented for each parameter.
o Parameter names and values as documented below must be used
always without quotaton marks ("), if not explicitly stated
otherwise.
Page 2
o The default value of a parameter is always chosen that it does
not change the standard functionality
JDBC Sender Adapter Parameters
1. Parameter name: "normalizeFieldNames"
Parameter type: boolean
Parameter value: true for any capitalization of the string "true",
false otherwise
Parameter value default: false
Available with: SP11 Patch 5 and SP12 Patch 1
Category: 2
Description:
Assume a scenario involving a JDBC Sender communication channel to
select table rows from a database. The table's column names might
contain characters (e.g. a forward slash), which are not allowed
within XML element names. By default, the JDBC Adapter uses these
column names as is when building the query result XML document. This
results in the creation of an invalid XML response document.
In order to maintain backward compatibility with existing
implementations that rely on the old element name generation scheme,
a configuration change is required to activate the new element
naming convention. By configuring the advanced mode parameter above,
any invalid characters that would become part of an XML element name
are replaced with an underscore ("_") character.
JDBC Receiver Adapter Parameters
2. Parameter name: "logSQLStatement"
Parameter type: boolean
Parameter value: true for any string value, false only for empty
string
Parameter value default: false (empty String)
Available with: SP9
Category: 2
Description:
When implementing a scenario with the JDBC receiver adapter, it may
be helpful to see which SQL statement is generated by the JDBC
adapter from the XI message content for error analysis. Before SP9,
this can only be found in the trace of the JDBC adapter if trace
level DEBUG is activated. With SP9, the generated SQL statement will
be shown in the details page (audit protocol) of the message monitor
for each message directly.
This should be used only during the test phase and not in productive
scenarios.
________________________________________________________________________
Page 3
Valid releases
Software Component Release
from to
SAP-XIAFC XI ADAPTER FRAMEWORK CORE
3.0 - 3.0</i></i>
Regards,
Sridhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.