Scurity within =?iso-8859-1?Q?Fort=E9?=

I saw some exchanges on this forum talking about security of
database access.
The first asked question is one generic Oracle user or one Oracle user
per final user.
One Oracle user per final user guarantees that password are anywhere
except in the users' mind. But it's an heavy task to define this users
and also risky because with tools like ACCESS and SQL/NET, you are
directly connected to the whole database.
It seems that one generic user on Oracle for example is preferable
than one per final user.
Where do you manage this generic user and its password :
a- in a flat file on the server.
In this case, someone having the same code as my code is able to run
it and then access to my datas.
I think I'm true when I say anybody is able to run any piece of code
on a production machine if he knows the machine name and the TCP/IP
port ?
b- because a- seems to be risky, a better solution seems to be putting
in a DBSession the name of the generic user and its password.
Has anybody good practice on this concern ?
What are your choices for securing a Forté Environment.
If I know the machine name and its TCP/IP port, I can shutdown,
uninstall partitions.
I can run my own partitions. Because Forté directories are in a
read/write mode, I can delete a lot of files on the machine, etc ...
I am right ?
Thank you.

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Similar Messages

=?iso-8859-1?Q?Fort=E9_CGI_problem?=

Messaggio a più sezioni in formato MIME.
------=_NextPart_000_008F_01BEFB9C.9ADF54B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
------=_NextPart_000_008F_01BEFB9C.9ADF54B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<DEFANGED-META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<DEFANGED-META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY><DEFANGED-BODY bgColor=3D#ffffff>
<DIV>
<DIV>
We have encountered the following problem:

Using the basic authentication on a web server, there =
is an=20
problem passing the information between web server and Forté.
In the attribute REMOTE_USER in the object =
Request.cgienv=20
should be present the value of the user authentication, so in =
Forté we=20
should access to it.
Instead, many of the values in the Request.cgienv not =
exists=20
and we show the list: 

**************** Attributes CGI in Request.cgienv=20
**************** 
Value of AUTH_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of CONTENT_LENGTH 0 <FONT=20
face=3DArial size=3D2>
Value of CONTENT_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of GATEWAY_INTERFACE (nil)<FONT=20
size=3D2> 
Value of HTTP_ACCEPT (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_COOKIE (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_USER_AGENT (nil) <FONT=20
face=3DArial size=3D2>
Value of PATH_INFO /frte_cs0 <FONT=20
face=3DArial size=3D2>
Value of PATH_TRANSLATED (nil) <FONT=20
face=3DArial size=3D2>
Value of QUERY_STRING=20
 ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm</F=
ONT><FONT=20
size=3D2> 
Value of REMOTE_ADDR (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_HOST (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_IDENT (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_USER (nil) <FONT=20
face=3DArial size=3D2>
Value of REQUEST_METHOD GET <FONT=20
face=3DArial size=3D2>
Value of SCRIPT_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_PORT 0 <FONT=20
face=3DArial size=3D2>
Value of SERVER_PROTOCOL (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_SOFTWARE (nil) <FONT=20
face=3DArial size=3D2>
In the environment are installed the followings versions of =
products:
Forté 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Forté 3.G.2 and WebEnterprise 1.B, =
the=20
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of =
the=20
basic authentication in a Forté variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.</DIV></DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV></BODY><=
/HTML>
------=_NextPart_000_008F_01BEFB9C.9ADF54B0--

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Are there any books out about =?iso-8859-1?Q?Fort=E9?= or=?iso-8859-1

I am trying to find books on Forté or Forté Express.
Could anyone help me answer this question.
Thank You
John Schaefer
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

that try/catch was just a lazy way to get passed the compiler for this tiny test program. on Sun, both
x = new String(bytes, 0, 2, "ISO-8859-1" );and
x = new String(bytes );produced the same incorrect result. Sun's default is US-ASCII, so it looks like something either wasn't set right, either in the code, or in the OS, or in the java invocation, that it made both ISO-8859-1 and US-ASCII the same or that ISO-8859-1 doesn't even exists and it reverted back to the default. it didn't throw exception, that i know, otherwise, x would not have been set.
Might there be something in the OS or jvm that might relate to ISO-8859-1 support?

Xslt ecc6 ISO-8859-1 problem when download xml file

Hello,
i create an ABAP test program:
*& Report Z_ABAP_TO_XML *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:\Users\Marco Consultant\Desktop\test.xml'.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4) TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_itab TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person TYPE STANDARD TABLE OF ts_person,
 gs_person TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
 gs_source_wa TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex TYPE REF TO cx_root,
 gs_var_text TYPE string.
* Fill the internal table
gs_person-cust_id = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
TRY.
 CALL TRANSFORMATION z_abap_to_xml
 SOURCE (gt_source_itab)
 RESULT XML gt_itab.
CATCH cx_root INTO gs_rif_ex.
 gs_var_text = gs_rif_ex->get_text( ).
 gs_var_text = gs_rif_ex->get_text( ).
 MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
 filename = gs_file
CHANGING
 data_tab = gt_itab
EXCEPTIONS
 file_write_error = 1
 no_batch = 2
 gui_refuse_filetransfer = 3
 invalid_type = 4
 no_authority = 5
 unknown_error = 6
 header_not_allowed = 7
 separator_not_allowed = 8
 filesize_not_allowed = 9
 header_too_long = 10
 dp_error_create = 11
 dp_error_send = 12
 dp_error_write = 13
 unknown_dp_error = 14
 access_denied = 15
 dp_out_of_memory = 16
 disk_full = 17
 dp_timeout = 18
 file_not_found = 19
 dataprovider_exception = 20
 control_flush_error = 21
 not_supported_by_gui = 22
 error_no_gui = 23
 OTHERS = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
and i created XSLT test conversion:
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output encoding="iso-8859-1" indent="yes" method="xml" version="1.0"/>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
 <CUSTOMERS>
 <xsl:apply-templates select="//IPERSON/item"/>
 </CUSTOMERS>
</xsl:template>
<xsl:template match="IPERSON/item">
 <item>
 <customer_id>
 <xsl:value-of select="CUST_ID"/>
 </customer_id>
 <first_name>
 <xsl:value-of select="FIRSTNAME"/>
 </first_name>
 <last_name>
 <xsl:value-of select="LASTNAME"/>
 </last_name>
 </item>
</xsl:template>
</xsl:transform>
Seem all correct infact the program download a file XML but the file have the encoding="UTF-16" also if i have specified "iso-8859-1" and if i tried to opend the xml file the file appears not correct because is generated with as first character "#", why?
Below the xml generated..
What i have to do to generate a correct XML without errors?
#<?xml version="1.0" encoding="utf-16"?>
<CUSTOMERS>
<item>
 <customer_id>0003</customer_id>
 <first_name>Bill</first_name>
 <last_name>Gates</last_name>
</item>
<item>
 <customer_id>0004</customer_id>
 <first_name>Frodo</first_name>
 <last_name>Baggins</last_name>
</item>
</CUSTOMERS>

hello all!
i resolve the problem using:
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
 byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
 exporting encoding = g_encoding.
I think it's the right way, i put all my ABAP program updated:
*& Report Z_ABAP_TO_XML *
*& Write the data from an internal ABAP table into an XML document, *
*& and write it onto your frontend computer *
REPORT z_abap_to_xml.
TYPE-POOLS: abap.
CONSTANTS gs_file TYPE string VALUE 'C:UsersMarco ConsultantDesktop est.xml'.
data: g_ixml type ref to if_ixml.
data: g_stream_factory type ref to IF_IXML_STREAM_FACTORY.
data: resstream type ref to if_ixml_ostream.
data: g_encoding type ref to if_ixml_encoding.
* This is the structure for the data to go into the XML file
TYPES: BEGIN OF ts_person,
cust_id(4) TYPE n,
firstname(20) TYPE c,
lastname(20) TYPE c,
END OF ts_person.
* Table for the XML content
DATA: gt_xml_itab TYPE STANDARD TABLE OF char2048.
* Table and work area for the data to fill the XML file with
DATA: gt_person TYPE STANDARD TABLE OF ts_person,
 gs_person TYPE ts_person.
* Source table that contains references
* of the internal tables that go into the XML file
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
 gs_source_wa TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex TYPE REF TO cx_root,
 gs_var_text TYPE string.
* Fill the internal table
gs_person-cust_id = '3'.
gs_person-firstname = 'Bill'.
gs_person-lastname = 'Gates'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '4'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '5'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '6'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '7'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '8'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '9'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '10'.
gs_person-firstname = 'Frodo'.
gs_person-lastname = 'Baggins'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '11'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
gs_person-cust_id = '88'.
gs_person-firstname = 'Frodoèé'.
gs_person-lastname = 'Baggins~¦Üu0192'.
APPEND gs_person TO gt_person.
* Fill the source table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_person INTO gs_source_wa-value.
gs_source_wa-name = 'IPERSON'.
APPEND gs_source_wa TO gt_source_itab.
* Perform the XSLT stylesheet
g_ixml = cl_ixml=>create( ).
g_stream_factory = g_ixml->CREATE_STREAM_FACTORY( ).
g_encoding = g_ixml->create_encoding( character_set = 'utf-16' "unicode
 byte_order = 0 ).
resstream = g_stream_factory->CREATE_OSTREAM_ITABLE( table = gt_xml_itab ).
call method resstream->set_encoding
 exporting encoding = g_encoding.
TRY.
 CALL TRANSFORMATION z_abap_to_xml
 SOURCE (gt_source_itab)
 RESULT XML gt_xml_itab.
CATCH cx_root INTO gs_rif_ex.
 gs_var_text = gs_rif_ex->get_text( ).
 gs_var_text = gs_rif_ex->get_text( ).
 MESSAGE gs_var_text TYPE 'E'.
ENDTRY.
* Download the XML file to your client
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
 filename = gs_file
 FILETYPE = 'BIN'
CHANGING
 data_tab = gt_xml_itab
EXCEPTIONS
 file_write_error = 1
 no_batch = 2
 gui_refuse_filetransfer = 3
 invalid_type = 4
 no_authority = 5
 unknown_error = 6
 header_not_allowed = 7
 separator_not_allowed = 8
 filesize_not_allowed = 9
 header_too_long = 10
 dp_error_create = 11
 dp_error_send = 12
 dp_error_write = 13
 unknown_dp_error = 14
 access_denied = 15
 dp_out_of_memory = 16
 disk_full = 17
 dp_timeout = 18
 file_not_found = 19
 dataprovider_exception = 20
 control_flush_error = 21
 not_supported_by_gui = 22
 error_no_gui = 23
 OTHERS = 24.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*-- we don't need the stream any more, so let's close it...
CALL METHOD resstream->CLOSE( ).
CLEAR resstream.

Not a valid SOAP Content-Type: text/html; charset=iso-8859-1

Friends
JDEV and SOA suite 10134
I have multiple domains on my BPEL Server. In one of the domain since I deployed the new process, all the processes of that domain are now failing on execution with following error in opmn/soa_instance/*.err log files. No errors in domain.log
+"Caused by: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; cha+
+rset=iso-8859-1"+
At the same time we get Internal Server Error on BPEL Console.
I have sync processes with 1 or two invokes, so I am generally losing the instances, cannot provide the details in the process execution. All BPEL processes are invoking Siebel Web Services, that is the common part.
When I restart my system, it may or may not work; even if it works then within few instances execution again starts giving the same error. I can see that after the errors the instance are going through and getting completed successfully few times. All these processes were working successfully earlier.
Any idea about this !!!!
Thanks

Thanks Anirudh,
I don't use compensation handlers. Moreover I have properly defined the scopes and sequences throughout the bpel process. My processes are sync in nature and I'm not able say at what step exactly the processes are failing and throwing the SOAP content Type error though the instances are getting completed with delay soemtimes.

British Pound Sterling with UTF-8 and ISO-8859-15

Please excuse my long-windedness ... I'm simply trying to answer all possible questions up front and give the most possible information. I've searched through tons of forums and all over various sites and references and am not able to come up with a concrete solution to this. I'd appreciate any help anyone has.
I'm having some trouble with character sets and international currencies.
Our server was recently upgraded from Red Hat 7.3 to Red Hat 8.0. I understand that the default system encoding thus changed from ISO-8859-15 to UTF-8. I have verified this by executing the following:
public class WhichEncoding {
public static void main(String args[])
    String p = System.getProperty("file.encoding");
    System.out.println(p);
}I have two machines, one which represents the old system (7.3) and one representing the new (8.0), which I will call machine73 and machine80 respectively.
[machine73:~]# java WhichEncoding
ISO-8859-15
[machine80:~]# java WhichEncoding
UTF-8I have also verified that the JVM is using the correct default character set by executing the following:
import java.io.ByteArrayOutputStream;
import java.io.OutputStreamWriter;
public class WhichCharset {
    public static void main (String[] args) {
        String foo = (String)(new OutputStreamWriter(new ByteArrayOutputStream())).getEncoding();
        System.out.println(foo);
}which yields:
[machine73:~]# java WhichCharset
ISO-8859-15
[machine80:~]# java WhichCharset
UTF8Here comes the problem. I have the following piece of code:
import java.text.NumberFormat;
import java.util.Locale;
public class TestPoundSterling
    public static void main (String[] args)
        NumberFormat nf = NumberFormat.getCurrencyInstance(new Locale("en", "GB"));
        System.out.println(nf.format(1.23));
}When I compile and execute this, I see mixed results. On machine73, I see what I would expect to see, the British Pound Sterling followed by 1.23. To be sure, I outputted the results to a file which I viewed in a hex editor, and observed [A3 31 2E 32 33 0A], which seems to be correct.
However, when I execute it on machine80, I see a capital A with a circumflex (carat) preceding the British Pound Sterling and the 1.23. The hex editor shows [C2 A3 31 2E 32 33 0A].
I looked up these hexadecimal values:
Extended ASCII
0xC2 = "T symbol"
0xA3 = lowercase "u" with grave
ISO-8859-1
0xC2 = Capital "A" with circumflex (carat)
0xA3 = British Pound Sterling
Unicode Latin-1
0x00C2 = Capital "A" with circumflex (carat)
0x00A3 = British Pound Sterling
(This explains why, when I remove /bin/unicode_start and reboot, I see a "T symbol" and "u" with a grave in place of what I saw before ... probably an irrelevant sidenote).
I found a possible answer on http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8 under the Examples section. Apparently, a conversion between Unicode and UTF-8 acts differently based on the original Unicode value. Since the Pound Sterling falls between U-00000080 � U-000007FF (using the chart on the mentioned site), the conversion would be (as far as I can tell):
U-000000A3 = 11000010 10101001 = 0xC2 0xA3
This appears to be where the extra 0xC2 pops up.
Finally, to the whole point of this: How can I fix this so that things work as they should on machine80 like they did on machine73. All I want to see at the command line is the Pound Sterling. Getting the 0xC2 preceding the Pound Sterling causes some parts of my applications to fail.
Here's some additional information that might be of use:
[machine73:~]# cat /etc/sysconfig/i18n
LANG="en_US.iso885915"
SUPPORTED="en_US.iso885915:en_US:en"
SYSFONT="lat0-sun16"
SYSFONTACM="iso15"
[machine73:~]# echo $LANG
en_US.iso885915
[machine80:~]# cat /etc/sysconfig/i18n
LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"
[machine80:~]# echo $LANG
en_US.UTF-8Any help is very, very much appreciated. Thanks.

you didn't look hard enough, this is a faq...
there three options:
1) change the system encoding by setting LANG or LC_CTYPE environment variables... assuming you use bash:bash$ export LC_CTYPE=en_GB.iso88591 you can check the available locales with locale -a ... pipe it to grep en_GB to filter out the non-british english locales
-OR-
2) change the java default encoding from the command line with -Dfile.encoding... run with$ java -Dfile.encoding=ISO-8859-1 yourclass-OR-
3) set the encoding from within the program with OutputStreamWriter, or use a PrintStream that has the encoding set..PrintStream out = new PrintStream(new FileOutputStream(FileDescriptor.out), true, "ISO-8859-1");
System.setOut(out);see also the internationalization tutorial & the javadoc of the related classes....

Website not displaying correctly. Firefox is changing the character set to Western (ISO-8859-1) automatically.

Normally I have set Firefox (or it's set by default) to Character Set Unicode (UTF-8) and everything displays perfectly. I've never had a problem before.
Now however, whenever I upload my own website, for some bizarre reason on that particular tab (and only that tab) the Character Set is changed over to Western (ISO-8859-1) and then there's a few characters within my site that do not display correctly, namely apostrophes and hypens.
It definitely isn't my software (Serif WebPlus X4) because the page displays correctly in every other browser. Plus it displays correctly in Firefox if I change the Character set back to Unicode.
PS The site is a work in progress

That happens because the server sends a content-type (text/html; charset=ISO-8859-1) via the HTTP response headers and in that case that content type prevails. The page code is saved with an UTF-8 byte order mark (ï»¿) that you see in this case.
*http://web-sniffer.net/?url=http%3A%2F%2Fwww.valuevisionglasses.co.uk&http=1.1&gzip=yes&type=HEAD&uak=0
*http://httpd.apache.org/docs/current/mod/mod_mime.html#AddType

=?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Messaggio a più sezioni in formato MIME.
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
*------------------------------------------------------------------------=
Massimiliano Delsante
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
-----Messaggio originale-----
Da: Massimilano Delsante <[email protected]>
A: forte users <[email protected]>
Data: venerd=EC 10 settembre 1999 14.56
Oggetto: Fort=E9 CGI problem
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
------=_NextPart_000_00A9_01BEFB9D.13EFC330
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<DEFANGED-META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<DEFANGED-META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY><DEFANGED-BODY bgColor=3D#ffffff>
<DIV> </DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV>
<DIV>-----Messaggio =
originale----- Da:=20
Massimilano Delsante <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>&g=
t; A:=20
forte users <<A=20
href=3D"<a href=
"mailto:[email protected]">mailto:[email protected]</a>">[email protected]</A>> =
Data:=20
venerdì 10 settembre 1999 14.56 Oggetto: =
Forté CGI=20
problem </DIV>
<DIV>
<DIV>
We have encountered the following problem:

Using the basic authentication on a web server, there =
is an=20
problem passing the information between web server and Forté.
In the attribute REMOTE_USER in the object =
Request.cgienv=20
should be present the value of the user authentication, so in =
Forté we=20
should access to it.
Instead, many of the values in the Request.cgienv not =
exists=20
and we show the list: 

**************** Attributes CGI in Request.cgienv=20
**************** 
Value of AUTH_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of CONTENT_LENGTH 0 <FONT=20
face=3DArial size=3D2>
Value of CONTENT_TYPE (nil) <FONT=20
face=3DArial size=3D2>
Value of GATEWAY_INTERFACE (nil)<FONT=20
size=3D2> 
Value of HTTP_ACCEPT (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_COOKIE (nil) <FONT=20
face=3DArial size=3D2>
Value of HTTP_USER_AGENT (nil) <FONT=20
face=3DArial size=3D2>
Value of PATH_INFO /frte_cs0 <FONT=20
face=3DArial size=3D2>
Value of PATH_TRANSLATED (nil) <FONT=20
face=3DArial size=3D2>
Value of QUERY_STRING=20
 ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm</F=
ONT><FONT=20
size=3D2> 
Value of REMOTE_ADDR (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_HOST (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_IDENT (nil) <FONT=20
face=3DArial size=3D2>
Value of REMOTE_USER (nil) <FONT=20
face=3DArial size=3D2>
Value of REQUEST_METHOD GET <FONT=20
face=3DArial size=3D2>
Value of SCRIPT_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_NAME (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_PORT 0 <FONT=20
face=3DArial size=3D2>
Value of SERVER_PROTOCOL (nil) <FONT=20
face=3DArial size=3D2>
Value of SERVER_SOFTWARE (nil) <FONT=20
face=3DArial size=3D2>
In the environment are installed the followings versions of =
products:
Forté 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Forté 3.G.2 and WebEnterprise 1.B, =
the=20
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of =
the=20
basic authentication in a Forté variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.</DIV></DIV>
<DIV>*---------------------------------------------------------------=
----------------------------------------------* Massimiliano=20
Delsante</DIV>
<DIV> </DIV>
<DIV>O.T. Consulting S.r.l - <A=20
href=3D"<a href=
"http://www.otconsulting.com">http://www.otconsulting.com</a>">www.otconsulting.com</A> Via =
della=20
Previdenza Sociale N° 11 - 42100 - Reggio Emilia Tel. +39 0522 =
271550 -=20
Fax +39 0522=20
230710 *--------------------------------------------------------------=
-----------------------------------------------* </DIV></BODY><=
/HTML>
------=_NextPart_000_00A9_01BEFB9D.13EFC330--

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Re: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=

Massimilano,
We have just experienced this with
Forte 3.0.L.2
WebEnterprise 1.0.D.1
on DEC alpha OSF environment.
There is a forte defect report #48399
relating an unfixed problem in this version of Web Enterprise
"HTTPRequest missing CGI variables, including REMOTE_ADDR and REMOTE_HOST"
which looks like the problem.
Have you had any suggestions to get around this?
John
To: <[email protected]>
Subject: =?iso-8859-1?Q?I:_Fort=E9_CGI_problem?=
From: "Massimilano Delsante" <[email protected]>
Date: Fri, 10 Sep 1999 14:59:27 +0200
Reply-To: "Massimilano Delsante" <[email protected]>
We have encountered the following problem:
Using the basic authentication on a web server, there is an problem =
passing the information between web server and Fort=E9.
In the attribute REMOTE_USER in the object Request.cgienv should be =
present the value of the user authentication, so in Fort=E9 we should =
access to it.
Instead, many of the values in the Request.cgienv not exists and we show =
the list:=20
**************** Attributes CGI in Request.cgienv ****************=20
Value of AUTH_TYPE=20
(nil)=20
Value of CONTENT_LENGTH=20
0=20
Value of CONTENT_TYPE=20
(nil)=20
Value of GATEWAY_INTERFACE=20
(nil)=20
Value of HTTP_ACCEPT=20
(nil)=20
Value of HTTP_COOKIE=20
(nil)=20
Value of HTTP_USER_AGENT=20
(nil)=20
Value of PATH_INFO=20
/frte_cs0=20
Value of PATH_TRANSLATED=20
(nil)=20
Value of QUERY_STRING=20
ServiceName=3DPRCCservice&TemplateName=3D/190Online/login3.htm=20
Value of REMOTE_ADDR=20
(nil)=20
Value of REMOTE_HOST=20
(nil)=20
Value of REMOTE_IDENT=20
(nil)=20
Value of REMOTE_USER=20
(nil)=20
Value of REQUEST_METHOD=20
GET=20
Value of SCRIPT_NAME=20
(nil)=20
Value of SERVER_NAME=20
(nil)=20
Value of SERVER_PORT=20
0=20
Value of SERVER_PROTOCOL=20
(nil)=20
Value of SERVER_SOFTWARE=20
(nil)=20
In the environment are installed the followings versions of products:
Fort=E9 3.0.L.2
WebEnterprise 1.0.D.1
Web Server Microsoft iis 1.0 (on other node)
Using an environment with Fort=E9 3.G.2 and WebEnterprise 1.B, the =
attribute REMOTE_USER has a correct value
Which alternative solutions can we use in order to know the value of the =
basic authentication in a Fort=E9 variable?
Is it possible to store it in an other attribute?
Thanks in advance for your help.
*------------------------------------------------------------------------=
Massimiliano Delsante
=20
O.T. Consulting S.r.l - www.otconsulting.com
Via della Previdenza Sociale N=B0 11 - 42100 - Reggio Emilia
Tel. +39 0522 271550 - Fax +39 0522 230710
*------------------------------------------------------------------------=
John Soper, Information Systems Development, ITS, The University of Melbourne
email: [email protected] >>>> Tel: 9344 5612

With Forte Release2 supporting only OLE callout, you can use DDE
to pass data; but with Release 3 which supports OLE callin , you
should be able to pass data both ways.
- Arvind
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arvind Kumar Krishnaswamy
Digital/Forte Software Products Group
Digital Equipment Corporation ______________________
1800,Harrison Street,Suite 1700, | | | | | | | |
Oakland.CA 94612 USA |d |i |g |i |t |a |l |
| | | | | | | |
Tel : 510-251-6537 ----------------------
Fax : 510-251-6531
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ISO-8859-1 characters in xmlDom.domDocument

-- Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
-- JServer Release 8.1.7.0.0 - Production
-- Oracle XML Parser 2.0.2.9.0 Production
-- OS: Windows 2000 Professional
-- NLS_LANG in Oracle is: AMERICAN_AMERICA.UTF8
-- NLS_LANG in registry (client) is set to: SWEDISH_SWEDEN.WE8ISO8859P1
-- Description: Getting corrupt characters instead of the
-- Swedish characters "edv" after parsing the clob.
-- Output after running this script in sqlplus:
--| BEFORE
--| -----------------------------------------------------------------------
--| AFTER
--| -----------------------------------------------------------------------
--| <?xml version="1.0" encoding="ISO-8859-1"?><asdf>aaa edv aaa</asdf>
--| <?xml version = '1.0' encoding = 'ISO-8859-1'?>
--| <asdf>aaa ??? aaa</asdf>
--|
set serveroutput on
drop table xmltest;
create table xmltest
(before clob
,after clob);
declare
beforeClob clob;
afterClob clob;
xdoc xmldom.domdocument;
parser xmlparser.Parser;
begin
insert into xmltest
values('<?xml version="1.0" encoding="ISO-8859-1"?><asdf>aaa edv aaa</asdf>', empty_clob())
returning after into afterClob;
select before
into beforeClob
from xmltest;
parser := xmlparser.newParser;
xmlparser.parseCLOB(parser,beforeClob);
xdoc := xmlparser.getDocument(parser);
xmlparser.freeParser(parser);
dbms_output.put_line('Parsed xml charset: '||xmldom.getCharset(xdoc));
xmldom.writeToClob(xdoc, afterClob, 'WE8ISO8859P1');
commit;
end;
select * from xmltest;

Hi,
This is a known issue. Within CLOB, Oracle DB will always store data in UTF-8, so the encoding setups will not work.
Thanks.

XML file containing an ISO-8859-1encoded string not able to see charcater

We have an XML file with the following encoding:
<?xml version="1.0" encoding="ISO-8859-1"?>
The Oracle 10gR2 database is set with the following encoding.
PARAMETER VALUE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_CHARACTERSET WE8ISO8859P1
There are some characters that are not displaying within SQL Developer, how do I diagnose this as a database or a client issue?

Guys, why nobody takes care of at least telling us what characters you cannot see. You describe two random elements of the whole application and expect people to give reasonable answers. Please, read through this forum a bit and you will see how many configuration elements may matter. Then, take some time to describe your problem, including version of software, exact (!) symptoms of the problem, etc. Otherwise, you can just get some guesses instead of a solution!
-- Sergiusz

Como deixar a codificação padrão "iso-8859-1" ao invés de "utf-8" no navegador?

Quando faço o acesso ao banco do meu cartão de crédito, a primeira pagina deles é codificada com "UTF-8" e também existe o comando "charset=utf-8" no código HTML, após digitar o número do cartão, ele direciona para outra página, porém codificada com "iso-8859-1", mas sem nenhuma codificação no código HTML.
Identifiquei que o navegador usa por padrão o "utf-8" quando não existe codificação no código HTML, então gostaria de modificar esse padrão para "iso-8859-1".
O único lugar que encontrei para essa codificação foi ao pressionar o botão de avançado em "Fontes e cores", porém não funcionou.
A versão do meu navegado é 23.0.1, entretanto desde a versão 18 que encontro esse problema.

It is possible that the server sends the file(s) by default with UTF-8 and in such a case this encoding send by the server prevails over all other settings.
You can see the encoding here: Tools > Page Info > General
*Press the F10 key or tap the Alt key to bring up the hidden "Menu Bar" temporarily.

Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default]

When trying to load data into Essbase I get this error dialogue
Object [65313270] is locked by user [admin@Native Directory]
Unable to load database, locales [Arabic_SaudiArabia.ISO-8859-6@Default] and [English_UnitedStates.Latin1@Binary] are not compatible
Object [65313270] unlocked by user [admin@Native Directory]
Unexpected Essbase error 1019057
Have checked essbase.properties files (all 10 of them!) and the 2 references that I could find both point to the default value of [English_UnitedStates.Latin1@Binary]
So is the problem with the CSV file?

Have you looked at the Load Rule (yes, I know, developed in Studio, but it generates Load Rules which I believe you can open in EAS)? Is the dimension that contains BON accounted for?
Your second issue(s) seems to be that you have conflicting locales -- are you in SA? Could it be that Studio is installed with English as the language and EAS with Arabic (or vice versa)? Sorry, I have hardly any experience in languages other than English. Maybe one of the non-English language posters can chime in.
I can't say whether that load buffer issue means anything at all or not -- it could be a red herring.
Regards,
Cameron Lackpour

UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Codepage coverting error utf-8 from System codepage to iso-8859-1 (PI 7.1)

Hello Experts,
In our Prcess, we receive an Idoc from an IS-U system and then we send this Idoc with some Header-Information via http-Adapter to a Seeburger System.
In the outbound communication Channel we have a XI Payload manipulation with xml-Code iso-8859-1.
We get the Error: Codepage coverting error utf-8 from System codepage to iso-8859-1, and only for this Idoc, where othe similar Idocs runs correctly.
Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
PS: another XI in our landscape uses a http-Channel with the same configuration in a similar process, an it work, so guess the Problem is not in the communication channel.
thanks,
best regards

> Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
A would rather think, that there could be any non-iso-8859-1 character be in the IDoc. For example an czech or polish character.

Scurity within =?iso-8859-1?Q?Fort=E9?=

Similar Messages

Maybe you are looking for