SOAPAction Header field case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

Gourav,
This is W3 Standard:
HTTP verbs are case sensitive. (http://www.w3.org/TR/wsdl)
In my case, the webservice provider was implemented in JAVA code and in Linux server. Java and Linux are case sensitive.
I agree with you if we are working with .NET implementation.
I already have tried to consume a .Net asmx webservice and works fine.

Similar Messages

Are idoc fields case sensitive?

Hello, there has been an error during idoc processing. The trading partner field was filled in lowercase and this is bringing me error Message no. FB279 ' Company dp0017 is not defined'. The other idocs had DP0017 filled in and were processed fine.
Any input on this? thx.
Edited by: Antish Awootar on Jun 7, 2011 8:02 AM

Hi Antish,
It actually depends on the value that is stored in the IDOC, if the IDOC has company code in lower case then that is exactly how it will be used in the program for all purpose and no automatic conversion is applied. The below message is thrown in the FM - FI_COMPANY_CHECK This FM will look up the table T880 - If you check the entry in this table will be DP0017 and not dp0017. Hence it is throwing the error message.
If your question is it works fine when i try in SE37 with the FM "FI_COMPANY_CHECK" or if i input "dp0017" in WE19 or in SE11 against T880, then the reason for that is a conversion is applied automatically and it is changed to DP0017.
To answer your question "Are idoc fields case sensitive?", it depends on the context, does it retain the case when it is filled in, yes it does.
Regards,
Chen
Edited by: Chen K V on Jun 7, 2011 4:10 PM

Column header sort - case sensitivity issue

Hi guys,
I'm having an issue with the built in column sorting when you click the headers on a report. Basically case sensitivity is taken into account and capital letters get sorted before smaller case letters, for example:
Cats
Dogs
Zebra
ants
bears
How would I be able to fix this built in sort?
Thanks,
Luis

Luis,
See if Denes's solution helps: Report sort by column header question .
Scott

CSS cookieurl: case sensitive?

Hello,
As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
The settings look like this:
content stickyCookie
advanced-balance cookieurl
string prefix "SESSION_ID="
On the HTTP header the cookie field looks like this:
Set Cookie: SESSION_ID=ABCDEF
But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
http://localhost/Info/index;session_id=ABCDEF?page=home.
Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
So I am afraid there is no way of making this work on a CSS?
Any help will be much appreciated!

Hi Javier,
The Cisco CSS is case-sensitive when searching for this string.
When configuring the CSS 11000 and 11500, determine first if you need a server cookie string. If the string operation under the content rule is match-service-cookie, which is the default setting, this parameter must be configured. In this case the service cookie string is matched against the cookie contained in the HTTP header for load balancing decision.
If the string operation under the content rule is set to the hash method, this parameter is not needed. In order to select one of the available servers, the cookie contained in the HTTP header is mathematically processed using a hashing algorithm. If available, the hash algorithm assigna the connection carrying a certain cookie to the same server. This example focuses on the match-service-cookie case.
Note: Cookies are case sensitive.
Configuring the Service
training4(config># service server_g
training4(config-service[server_g])# string LV2KJK (the server cookie text)
training4(config># service server_h
training4(config-service[server_h])# string AARIKA
Configuring the Content Rule
Note: Cookies require a Layer 5 rule.
You can create a Layer 5 rule by adding a URL.
For example, .
A Layer 4 rule can be promoted to a Layer 5 rule by issuing the advanced-balance cookies command.
Choose the advanced-balance method.
training4(config-owner-content[cookie-layer5])# advanced-balance cookies
Configure the string operation.
training4(config-owner-content[cookie-layer5])# string operation ?
match-service-cookie (DEFAULT)
hash-crc32
hash-xor
hash-a
Define the starting/ending bytes.
training4(config-owner-content[cookie-layer5])# string range 1 to 200
Start byte position of cookie/url after header (Range:1-600)
Specify the prefix located in the string range.
training4(config-owner-content[cookie-layer5])# string prefix "ASPSESSION"
"Quoted textual information"(Len: 0-32)
Indicate how many bytes to skip after the starting prefix.
training4(config-owner-content[cookie-layer5])# string skip-length 9
"Quoted textual information"(Len: 0-32)
Indicate how many bytes after the prefix/skip-length make-up the string.
training4(config-owner-content[cookie-layer5])# string process-length 6
Integer value(Range: 0-64)
If no string process length is configured, search after end of string character.
training4(config-owner-content[cookie-layer5])# string eos-char "&"
"Quoted textual information"(Len: 0-5)
Specify the failover in the event that a server goes down or is suspended.
training4(config-owner-content[cookie-layer5])# sticky-serverdown-failoversticky-srcip
sticky-srcip-dstport
sticky-srcip
balance (Default)
redirect
reject
Below is an example of a cookie string, and how some of the parameters work.
ASPSESSIONJJKKJJKK=LV2KJK44444444
!--- The string prefix = ASPSESSION.
!--- The string skip-length = 9. Skip
!--- nine characters after the prefix.
!--- The string process-length = 6, which would make
!--- the string LV2KJK matching service server_g.
ASPSESSIONSQPMMJHK=AARIKAMDESLD
!--- Matches service server_h.
Below is a sample configuration for the cookie strings.
!************************** SERVICE **************************
service server_g
ip address 172.17.63.240
string LV2KJK
active
service server_h
ip address 172.17.63.241
string AARIKA
active
!*************************** OWNER ***************************
owner braden
content server-cookie
protocol tcp
vip address 172.17.63.199
port 80
advanced-balance cookies
string range 1 to 200
string prefix "ASPSESSION"
string skip-length 9
string process-length 6
add service server_g
add service server_h
active
Kindly tell if this information is of any use to you.
Sachin garg

Table and Primary Key Case Sensitive in Automated Row Fetch

Why are the table and primary key fields case sensitive in the Automated Row Fetch process? I'm debugging an error in this process and I'm not sure what the case should be.

Russ - It's a defect of sorts. Use upper case in the process definition. I don't think these processes will work with tables or columns whose names are not known to the database as upper-case values, i.e., defined using double-quoted non-upper case.
Scott

Make material number in MM01 case sensitive

Hi Experts,
I got an requirement like to make MM01 transaction while creating material number it has to accept both Lower and Upper Case..
Say for example : "a12" as one material
"A12" as another one material
any suggestions please send.....
Thanks.
Preethi jose

First check conversion-exit of domain MATNR (something like MATN1) with Customizing behind, you will have to analyze your Customizing (and the list of extensions, solutions installed on your system) to find the actual field(s) which contains the external format of the material master id (e.g. MARA-MFRPN for a sample) AND look at table MATERIALID (domain MATNR_EXT is also not case sensitive), then you may, with a SSCR key for the object as it will be a change of the standard, change the domain(s) definition to allow lowercase. But consider before some problems like search help becoming case sensitive, it is usually (at least) not a good idea to have key fields case-sensitive...
If possible, my advice is to not make this change by a developement, but to look for Customizing, check
Regards,
Raymond

SOAPAction HTTP header case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be exactly like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

> The value of the required verb attribute indicates the HTTP verb. Common values are GET or POST, but others may be used. Note that HTTP verbs are case sensitive.
This section does not say anything about HTTP headers. GET and POST are not headers, but HTTP methods.
> Acording to my Webservice vendor, the SOAPAction are indicated into this section.
This section has nothing to do with SOAPAction
> Also, I am working with SAP Support and got this repply:
> ... Yes, the value should be SOAPAction
> instead of SOAPACTION....
I do not comment this.
You have now following possibilities:
1. Convince your vendor to accept HTTP headers according to above mentioned RFC
2. Convince SAP that to change SOAPAction
Good luck.

Change Case-sensitivity of field ASKTX in Search Help ASMD

Hi experts,
In Collective Search help ASMD, there is a elementory search help /SAPBOQ/ASMD_MITEM where field ASKTX is Case sensitive.
How can I remove the case-sensitivity of this field ?
Thnks in advance,
Goutam

owngoal wrote:
You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
See #C13 in Time Machine - Troubleshooting for details.
And by this stage is it too late to recover anything?
Sometimes. Sometimes they can be repaired by Disk Utility. Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them. Sometimes nothing can. Sometimes you can restore some individual items, sometimes not. Sometimes you can do a full system restore from some backups, other times not.
does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
Probably -- you won't have WIFI interference.
But if you have an iMac, why not just connect the external HD directly to your Mac? That's much faster and more reliable (and supported).
You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup. Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

Case sensitive field in to_date function

update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input string
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.

Hi,
Welcome the the forum!
882431 wrote:
update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)It looks like you're missing a single-quote right before the last ')'.
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input stringThat error occurs when when you have characters in the 1st argument that do not correspond to anything in the 2nd argument. For example:
TO_DATE ( '30-Aug-2011 12:00'
, 'dd-Mon-yyyy'
)In this example, TO_DATE doesn;t know what to do with the ' 12:00' at the end of the 1st argument. According to the 2nd arguemnt, there's only supposed to be 11 characters in the string. So it raises the ORA-01830 error.
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.Case sensitive column names are a bad idea because they cause so amny problems, but I don't think this is one of those problems. It's more likely that you need to use SUBSTR (or some other string manipulation function) on "Order Date String" before using it in TO_DATE.
Whenever you have a problem, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, so people can re-create the problem and test their ideas.
Also post the results you want from that data, and an explanation of how you get those results from that data, with specific examples.
Always say which version of Oracle you're using.

ALV grid case-sensitive edit field

Hello,
i've a editable field on a alv grid.
The field is case-sensitive in the domain.
But when i enter a field an click rturn, the letters get uppercase.
What's the problem?
Best regards,
TomSd

Hi,
Add the attribute lowercase = 'X' while preapring field catalog for this field.
Regards,
Gopi.
Reward points if helpfull.

How do I make the my login page username field not case-sensitive?

Can anyone tell me how to make my username field not case-sensitive?
This is my code
<html>
<body>
<%@ page import="java.sql.*" %>
<%
String username = request.getParameter("username");
String password = request.getParameter("password");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
Connection login = DriverManager.getConnection("jdbc:odbc:Testing","abc","abc");
Statement stmtLogin = login.createStatement();
String sqlLogin = "SELECT UserName, UserPassword FROM Users WHERE UserName='"+username+"'";
ResultSet rsLogin = stmtLogin.executeQuery(sqlLogin);
while(rsLogin.next())
String suser = rsLogin.getString("UserName");
String spass = rsLogin.getString("UserPassword");
if(username.equals(suser) && password.equals(spass))
HttpSession mysession = request.getSession(true);
mysession.setAttribute("username",request.getParameter("username"));
response.sendRedirect("hello.jsp");
else if(!(username.equals(suser) && password.equals(spass)))
response.sendRedirect("index.jsp?message=Invalid%20Username%20or%20Password");
login.close();
%>
</body>
</html>

if(username.equalsIgnoreCase(suser) && password.equals(spass))Hope this helps!

Case sensitivity for text fields

Does anyone know how to turn off case sensitivity for a text field??
Your help is appreciated.

Do you recommend another field type that can be used that does not use case sensitivity?
Thank you

Case sensitive sql - table and field names

I have a weird problem.
I have a client which works with MS SQL SERVER 2000.
database collation name is: Turkish_CI_AS
at the beginning I have this sql statement:
"select value from [OWNER].setting"
but because this table exists in database as "SETTING", I get java.sql.SQLException -
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'setting'.
while I change the sql statement to:
"select VALUE from [OWNER].SETTING"
it works ok.
I uses also other databases, but it works ok with small letters.
How can avoid this problem? should I change all the sql statements to
upper case?
I will appreciate any help.
Thanks.

I am not sure about case sensitivity of tables, but as a convention, I always use table names in UpperCase separated only by _.
I don't remember this to be a problem with Oracle or Sybase.
***Annie***

HTTP Header fields in SOAP adapter - Part 2

Hi All,
With regards to my previous thread HTTP Header fields in SOAP adapter
my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER". Due to case-sensitive in vendor server the connection is not gettingestablished.
Please help me out how to solve the problem.
Note: Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
Regards,
Dhill

Hi Neaves,
Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
To use the nosoap mode, the channel must be configured to use no SOAP envelope.
If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities. I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
Regards,
Dhill

Header Fields not picked in Http Adapter

Hi ,
I am sending a few custom header fields that have been set up in the HTTP adapter but for some reason they are not picked.
Any suggestions..
-Teresa

Thanks Sameer,
This note did help us pick up the header fields but on picking up it returns the header fields in lower case instead of the case Sensitive format I sent it in ..I looked at the trace log too and its in case sensitive format but when my 3rd party receives it, it is in lower case format...funny even the <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
is also in lowercase..I am running XI 3.0 SP4..Is it an XI issue or something to do with my integration server which processes my HTTP adapter??? Or any other notes also needs to be applied??
Please help..
Trace level="1" type="T">---- Plain HTTP Adapter Outbound----</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_OUTBOUND-ENTER_PLSRV">
<Trace level="3" type="T">Quality of Service EO</Trace>
<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>
<Trace level="3" type="T">URL http://xkqbdev.ampton.net:50080/abc/Web/servlet/XMLChannelServlet</Trace>
<Trace level="3" type="T">Proxy Host: 10.69.14.98</Trace>
<Trace level="3" type="T">Proxy Service: 80</Trace>
<Trace level="3" type="T">Authorization: Basic NDQ0NDQ0NDQ0OjQ0NDQ0NDQ0NA==</Trace>
<Trace level="3" type="T">~request_method POST</Trace>
<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>
<Trace level="3" type="T">accept: /</Trace>
<Trace level="3" type="T">content-type: text/xml</Trace>
<Trace level="3" type="T">Header-Fields</Trace>
<Trace level="3" type="T">X-Extricity-Sender-ID 444444444</Trace>
<Trace level="3" type="T">X-Extricity-BO-Type-ID http://xml.cXML.org/schemas/cXML/1.2.011/cXML.dtd</Trace>
<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">content-length 3023</Trace>
<Trace level="2" type="T">HTTP-Response :</Trace>
<Trace level="2" type="T">Code : 500</Trace>
<Trace level="2" type="T">Reason: Internal Server Error</Trace>
<Trace level="2" type="T">Code : 500</Trace>
<Trace level="2" type="T">Reason: Internal Server Error</Trace>
</Trace>
</Trace>
-Teresa

SOAPAction Header field case sensitive

Similar Messages

Maybe you are looking for