Java client connecting to multiple weblogic instances

We have a standalone java client JMS application that needs to connect to multiple
Weblogic instances running in different domains.
The client works fine when we obtain an initial context to the multiple instances
without specifying a security principle and password. As soon as we add in this
information, we get problems: The initial context is still successfully retrieved
for each of the weblogic instances, but we cannot send JMS messages to destinations
on one of the Weblogic instances due to a security exception which states that
there is an 'Invalid Principal'.
Any advice would be appreciated.

You should first establish a trust relationship between your Weblogic
servers:
http://e-docs.bea.com/wls/docs70/secmanage/domain.html#1171534
It is very poorly documented since this is a change in the behavior with
previous versions and should have been in the Release Notes but instead
is inside the normal documentation.
--dejan
jonathan wrote:
Thanks Arvind, but both JVMs are the same (1.3.1) and there is no jsse stuff in
the classpath.
"Arvind Gudipati" <[email protected]> wrote:
check if yr client's jvm version is the same as server's jvm.. ive noticed
this problem a few times when i was using client jvm (1.4.x) connecting
to
server jvm (1.3.x).. also check if u have any jsse libraries in yr
classpath.. if so remove 'em
+arvind
"Jonathan" <[email protected]> wrote in message
news:3f2f9f19$[email protected]..
We have a standalone java client JMS application that needs to connect
to
multiple
Weblogic instances running in different domains.
The client works fine when we obtain an initial context to the multiple
instances
without specifying a security principle and password. As soon as we
add in
this
information, we get problems: The initial context is still successfully
retrieved
for each of the weblogic instances, but we cannot send JMS messages
to
destinations
on one of the Weblogic instances due to a security exception which
states
that
there is an 'Invalid Principal'.
Any advice would be appreciated.

Similar Messages

How Can I Use Multiple Weblogic Instances in a Single OS

Hello Everyone,
Actually I have to install Some different applications. Few of them need weblogic 10.3.6 and others need 10.3.4. The OS am using is Oracle Enterprise Linux 5.
Now I am able to install 2 separate(One of 10.3.4 and 10.3.6) instances with two different users,In two different directories.
I have installed the weblogic 10.3.6 version with a user webadmin and installed node manager with port 5556. This is working fine.
The main problem here is :
In the second instance (10.3.4 ) installed with a a different user and gave the port number to NodeManager as 1600 and its not getting started. Its throwing error and also after some errors in the terminal am able to see that its reverting to port number 5556 only.
What might be the issue?
I have to install 2 different versions of weblogic in a single Server. But am failing with NodeManager. What Can I do to have multiple weblogic instances with multiple versions in a single server ?
Can anyone suggest a resolution for this please ?
Thanks in advance.

Pl do not spam these forums with multiple posts - How Can I Use Multiple Weblogic Instances in a Single OS

R/3 connected to multiple XI instances

Can a single R/3 instance be connected to multiple XI instances at the same time? If so are there any limitations and is there any special considerations that should be taken into account?

Limitation is only when you are using proxy because here you are using native XI protocol and depend on these administration settings in SXMB_ADM. In SXMB_ADM there is one selection you can choose either INTEGRATION SERVER or NON INTEGRATION SERVER. If you choose non integration you have to point to your current integration server and here you can only fill one destination.
Assuming :
Type XI : R/3
RFC N : M
IDOC N : M
Proxy (XI) 1:N
other adapters N : M
where
N,M - any number
By the way using few XI servers connected to one R/3 is a little bizzare
Regards,
wojtek

Multiple weblogic instances using IIS to proxy the requests

I have a need to run multiple weblogic instances using IIS as the web
server.
Does anyone know if this is possible. I am aware and have been able to run
multiple weblogic servers as an nt service,
but in those cases weblogic was being called and IIS was being bypassed.
Now the user base wishes to use IIS to proxy the requests.
I have been able to set IIS to forward using the .jhtml and .jsp file
extensions to the iisproxy.dll, but have not been able to forward these
requests to multiple weblogic instances. When the request is made it is
only looking in the first instance of weblogic for the request.
Is it possible to use weblogic and IIS with two or more weblogic instances,
without weblogic acting as a webserver.
I dont believe this is possible but I need to find out if this really is the
case.
Thanks for any help you can provide.
Ed

You need run each IIS web server instance in its own memory space. This can
be set through the Management Console for IIS.
Keith
Mike Kendzierski <[email protected]> wrote in message
news:[email protected]..
We tried to do this & Weblogic doesn't support this config. We opened upa
support call with them regarding this, but there is a problem with the way
that IIS & NT proxies .JSP pages to the weblogic servers. It's very
unstable this way & I wouldn't recommend this config.
We switched to Apache with virtual hosts to do this & it works fine. It's
probably not the answer you want to hear, but it works very well.
If you have any questions, just ask away.
"Ed" <[email protected]> wrote in message
news:3a296c2d$[email protected]..
We are using IIS4 with weblogic 4.5.1 sp11,
I thought I read someplace, their was a problem between wls 4.5.1 sp7
and
wls 5.1 where it didnt look in the folder where the dll was.
I will give it a try on monday.
Peter Mergaerts wrote in message <[email protected]>...
We tried to do the same thing.
We copied iisproxy.dll and iisproxy.ini to server1 and let IIS use this.dll
instance for proxying .jsp etc.
We copied the iisproxy.dll and iisproxy.ini to server 2, renamed
iisproxy.dll to iisproxy2.dll (to make sure another instance was used)
and
let the second iis site use iisproxy2.dll, but that didn't worked. (It
doesn't read the iisproxy.ini file located in the same directory as the.dll
file, altough in the manual it says it checks this first.) Now, I thinkit's
possosible to use several iisproxy.dll's as long as you rename it so
each
get it's own instance, the only problem is that each .dll doesn't readthe
correct iisproxy.ini file. (BEA, is this for SP7?)
Regards,
Peter Mergaerts

How can I connect to multiple WLS instances from a single Apache virtual host

Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something like this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway defines the the WL
connection for the entire virtual host, but I need to be able to do it on a location
basis is that possible?
Thanks
Jens Schutt

httpd.conf:
<VirtualHost 172.17.9.24:443>
DocumentRoot "/www/X"
ServerName qawebivesta.qa.livecapital.com
ErrorLog /usr/local/apache/logs/qaweb1.error_log
TransferLog /usr/local/apache/logs/qaweb1.access_log
SSLEngine on
SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /usr/local/apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile /usr/local/apache/conf/ssl.key/server.key
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
SSLOptions +StdEnvVars
</Files>
<Directory "/usr/local/apache/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
SetEnvIf User-Agent ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
Debug ON
DebugConfigInfo ON
<Location /ivesta/>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 7001
</Location>
<Location /TMPPhase2>
SetHandler weblogic-handler
WebLogicHost qawlgc1
WebLogicPort 11001
</Location>
</VirtualHost>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/TMPPhase2 works fine, but when I try to access /ivesta I get a 404 from WebLogic
"https://qawebtmp.qa.livecapital.com/ivesta/index.jsp?__WebLogicBridgeConfig
Weblogic Apache Bridge Configuration parameters:
     WebLogic Cluster List:
          General Server List:
               Host: 'qawlgc1' Port: 11001
          DefaultFileName: ''
          PathTrim: ''
          PathPrepend: ''
          ConnectTimeoutSecs: '10'
          ConnectRetrySecs: '2'
          HungServerRecoverSecs: '300'
          MaxPostSize: '-1'
          DynamicServerList: ON
          StatPath: false
          CookieName: WebLogicSession
          Idempotent: ON
          FileCaching: ON
          DisableCookie2Server: OFF
          QueryFromRequest: OFF
          Build date/time: Jun 25 2001 15:09:34
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This should have been connecting to my 7001 instance not the 11001.
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
What do you mean the wrong port? Post the complete output from
WebLogicBridgeConfig as well as the URL you used.
Also, paste the weblogic relative portions from your httpd.conf
Thanks,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
I also used ?__WebLogicBridgeConfig to verify that it did pick up thewrong port.
Here is my build date for mod_wl.so in SP10
Build date/time: Jun 25 2001 15:09:34
Thanks
Jens
"Eric Gross" <[email protected]> wrote:
Make sure you are using the latest plugin. As well, add parameter:
DebugConfigInfo=ON and make a request with a query paramater of
?__WebLogicBridgeConfig and you should then see the build date/time.
We can
then see if you are indeed using the latest plugin.
It is not a possibility to get the source.
Regards,
Eric
"jens" <[email protected]> wrote in message
news:[email protected]...
And the solution where you put the WebLogic parm under location
the
last
location
over rule the previous.
I have also tried to upgrade my plug-in from SP8 to SP10 but that
didn't
make
any difference either.
Is it possible to get the source code for the plug-in, I'm afraid
that
it
don't
follow put's all it's parm's a the vhost level no matter where in
the
conf
file
they are placed.
HELP
Jens
"Eric Gross" <[email protected]> wrote:
Yu is correct.
Here is another way to do it as well:
MatchExpression /x
WebLogicCluster=server1:port,server2:port|PathTrim=/x
MatchExpression /yWebLogicCluster=server3:port,server4:port|PathTrim=/y
The general syntax for this would be:
MatchExpression exp name=value|name=value
Where exp=Mime type(*.jsp) or exp=/x(path)
The next argument in the list is a pipe(|) delimited list ofname=value
pairs (ie: WebLogicHost, WebLogicPort, WebLogicCluster, PathTrim,
PathPrepend, etc..).
Hope this helps.
Regards,
Eric
"Yu Tian" <[email protected]> wrote in message
news:[email protected]...
Hi Jens,
I think you can proxy by ppath.
<Location /x>
SetHandler weblogic-handler
WebLogicCluster cluster1
</Location>
<Location /y>
SetHandler weblogic-handler
WebLogicCluster cluster2
</Location>
thanks
Yu
"Jens" <[email protected]> wrote in message
news:[email protected]...
Configuration : WebLogic 5.1 SP8 & Apache
I need to be able to have a configuration that looks something
like
this.
www.company.com/x -> WL cluster01
www.company.com/y -> WL cluster02
In all the examples that I have been able to find they alway
defines
the
the WL
connection for the entire virtual host, but I need to be able
to
do it
on
a location
basis is that possible?
Thanks
Jens Schutt

LDAP connections with multiple proxy instances

After configuring LDAP connectivity through the Admin application on a machine with multiple proxy instances I end up with:
number of proxy instances x LDAPConnPool times number of connections to the LDAP server.
Question: Is it possible to prevent some of the proxy instances from opening LDAP connections?

Hi
Increase the IDLE timeout value on the LDAP server. Of course, this just extends the inevitable. Check if there is a way to disable IDLE timeout on LDAP server.
Regards,
Nagendra HK

Understanding of wireless client connection to multiple APs

Hello,
I would like to know how do wireless clients connect to APs
For e.g. if in a single floor square office space - wireless network with multiple APs exists on the same SSID, how do clients decide which AP to connect to. For e.g. the client may get similar strength signals from two APs close to each other (such as Excellent). Which AP does client connect to.
Secondly, how does the load distribution take place. For e.g. if on one AP, 10 clients connect and on the other AP, 20 clients connect, how can equal load distribution be acheived, that is 15 on each AP without the tiring MAC filtering configurations.
Thirdly, is there something like number of user/connection restrictions on APs. I have gone through some AP manuals and did not find any such specifications like max. # of users = 20 etc. Currently we are using D-Link AP and have noticed that once the # of connections go upto 20, performance reduces heavily such as the latency on gateway pings go upto 1000-2000ms.
Fourthly, how can I identify from the client to which AP it is connected.
Thanks.

I would like to know how do wireless clients connect to APs
For e.g. if in a single floor square office space - wireless network with multiple APs exists on the same SSID, how do clients decide which AP to connect to. For e.g. the client may get similar strength signals from two APs close to each other (such as Excellent). Which AP does client connect to.
ANS - Its first come first serve... however.. sometimes if we have multiple SSIDs one with open auth and no encryption and other fuly protected.. then the client wil connect to the open rather the secured on.
Secondly, how does the load distribution take place. For e.g. if on one AP, 10 clients connect and on the other AP, 20 clients connect, how can equal load distribution be acheived, that is 15 on each AP without the tiring MAC filtering configurations.
ANS - MAC is a good option but apart from that.. i have seen somewhere but not able to remember the command which will limit the number of clients per radio..
Thirdly, is there something like number of user/connection restrictions on APs. I have gone through some AP manuals and did not find any such specifications like max. # of users = 20 etc. Currently we are using D-Link AP and have noticed that once the # of connections go upto 20, performance reduces heavily such as the latency on gateway pings go upto 1000-2000ms.
ANS - AP can take upto 2048 MAC addresses.. its recommended not to have more than 24 clients per AP..
Fourthly, hw can I identify from the client to which AP it is connected.
ANS -If the clients are CCX compatible and aironet extentions enabled on the AP. then the command "show dot11 ass" will tell the clients connecting to which AP.. the AP name will get displsayed in the output..
Regards
Surendra

NSAPI - directing to multiple weblogic instances

Hi,
I am trying to redirect 2 different URLs (www.test.com/server1 and www.test.com/server2)
to distinct weblogic instances which run on ports 7001 and 8001. The NSAPI instructions
say to do the following in the obj.conf file -- see below. This works great if
I open a new browser window for each one. However, the problem occurs in a single
browser instance when switching between the 2 URLs. Both URL requests will only
be directed to one of the WebLogic instances -- the other WL instance is ignored
no matter what URL you enter.
Any ideas????
# Here we configure the NSAPI module to pass requests for
# "/weblogic" to a WebLogic Server listening at port 7001 on
# the host myweblogic.server.com.
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy WebLogicHost=myweblogic.server.com\
WebLogicPort=7001 PathTrim="/weblogic"
</Object>
# Here we configure the plug-in so that requests that
# match "/servletimages/" is handled by the
# plug-in/WebLogic.
<Object name="si" ppath="*/servletimages/*">
Service fn=wl_proxy WebLogicHost=192.192.1.4 WebLogicPort=7001
</Object>

I am not sure I understand what you want to do.. From your example, what you
are doing is directing anything that has "weblogic" in the URL to a single
weblogic instance. In your case: myweblogic.server.com.
You are also directing anything with "servletimages" in the URL to :
192.192.1.4.
Both these servers are listening on port 7001. There is no mention of 8001.
Let's say you want to have all requests that have "server1" in the URL go to
one weblogic instance and all that have "server2" in the url goto the other
weblogic instance(port 8001), then you need to configure two object tags.
One that has a ppath="*/server1/*" and that will point to weblogic instance
1(port 7001) and another weblogic object that has a ppath="*/server2/*" and
points to weblogic instance 2(port 8001).
Hope this helps.
Regards,
Eric
"Lauren Jones" <[email protected]> wrote in message
news:3b6f04fb$[email protected]..
>
Hi,
I am trying to redirect 2 different URLs (www.test.com/server1 andwww.test.com/server2)
to distinct weblogic instances which run on ports 7001 and 8001. TheNSAPI instructions
say to do the following in the obj.conf file -- see below. This worksgreat if
I open a new browser window for each one. However, the problem occurs ina single
browser instance when switching between the 2 URLs. Both URL requestswill only
be directed to one of the WebLogic instances -- the other WL instance isignored
no matter what URL you enter.
Any ideas????
# Here we configure the NSAPI module to pass requests for
# "/weblogic" to a WebLogic Server listening at port 7001 on
# the host myweblogic.server.com.
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy WebLogicHost=myweblogic.server.com\
WebLogicPort=7001 PathTrim="/weblogic"
</Object>
# Here we configure the plug-in so that requests that
# match "/servletimages/" is handled by the
# plug-in/WebLogic.
<Object name="si" ppath="*/servletimages/*">
Service fn=wl_proxy WebLogicHost=192.192.1.4 WebLogicPort=7001
</Object>

Invoke BPEL 10g process by Java client code deployed in WebLogic 10.3.3

Hi,
I have a problem with the use of JNDI factory While invoking BPEL 10g process using client code deployed in WebLogic 10.3.3.
Should it be "com.evermind.server.rmi.RMIInitialContextFactory" or "weblogic.jndi.WLInitialContextFactory"?
(Should the JNDI factory follows the container of BPEL server or the container of client code?)

BPEL server from SOA Suite (10.1.3.3.1)
Client code which invokes the BPEL process deployed in WebLogic 10.3.3

How to serve multiple weblogic instances with a single apche server

Can any body let me know how to make use of an apache server to serve 2 weblogic
instances.
Thanks in advance
damodar

Yes, the documentation explains how to do this:
http://e-docs.bea.com/wls/docs61/adminguide/apache.html
Regards,
Eric
"Damodar" <[email protected]> wrote in message
news:3c23ccb9$[email protected]..
>
Can any body let me know how to make use of an apache server to serve 2weblogic
instances.
Thanks in advance
damodar

Connect to multiple local instances without enterig passwords

Oracle 10R2 on Linux Gentoo
I have several local instances which I want to connect in shell script without setting password explicitly. But when I use @connect_string it seems to me that os authentication is ignoring by oracle. Look at this:
oracle@omega1 ~ $ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Nov 24 16:38:40 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
oracle@omega1 ~ $ env | grep ORACLE_SID
ORACLE_SID=orcl
oracle@omega1 ~ $ sqlplus /@orcl as SYSDBA
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Nov 24 16:39:05 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name:
oracle@omega1 ~ $ groups
oinstall dba

I wouldn't like to enter sys password interactively because i use sqlplus from shell script which is ran under cron (unix scheduler).
remote_login_passwordfile is already set to exclusive:
oracle@omega1 ~ $ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Nov 24 17:04:33 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
I've also recreated password file with no result:
oracle@omega1 ~/oracle/product/10.2.0/db/dbs $ orapwd file=/home/oracle/oracle/product/10.2.0/db/dbs/orapworcl entries=20 force=y password=*********
oracle@omega1 ~/oracle/product/10.2.0/db/dbs $ sqlplus /@orcl as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Nov 24 17:13:23 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges

XI 3.0 and external Java client/web service

Hello,
I'm desperately tryin' to get an external system to work together with XI 3.0.
The setup is quite simple:
The external system is nothing but a simple Java program sending SOAP-based requests to a webservice. It is based on AXIS and is running satisfyingly when connecting directly to an appropriate Tomcat/AXIS-based web service, see the following communication.
-- local request
POST /axis/VAPService.jws HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.1
Host: 192.168.1.2:8080
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://localhost/SOAPRequest"
Content-Length: 422
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SOAPRequest soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAPDataIn xsi:type="xsd:string">890000001</SOAPDataIn>
</SOAPRequest>
</soapenv:Body>
</soapenv:Envelope>
-- local response
HTTP/1.1 200 OK
Set-Cookie: JSESSIONID=DFD7A00A244C18A058FCB52A8321A167; Path=/axis
Content-Type: text/xml;charset=utf-8
Date: Mon, 23 Aug 2004 06:52:47 GMT
Server: Apache-Coyote/1.1
Connection: close
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SOAPRequestResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAPRequestReturn xsi:type="xsd:int">1</SOAPRequestReturn>
</SOAPRequestResponse>
</soapenv:Body>
</soapenv:Envelope>
Now I have designed and configured simple business scenarios with XI 3.0 (synchronous as well as asynchronous). The only response I get from XI when the Java client connects ist the following:
-- remote request
POST /sap/xi/engine?type=entry HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.1
Host: <host>:<port>
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://soap.org/soap"
Content-Length: 424
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SOAPRequest soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <SOAPDataIn xsi:type="xsd:string">890000001</SOAPDataIn>
</SOAPRequest>
</soapenv:Body>
</soapenv:Envelope>
-- remote response
HTTP/1.0 500 HTTP standard status code
content-type: text/xml
content-length: 1493
content-id: <[email protected]>
server: SAP Web Application Server (1.0;640)
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP:mustUnderstand="1">
   <SOAP:faultcode>Client</SOAP:faultcode>
   <SOAP:faultstring></SOAP:faultstring>
   <SOAP:faultactor>http://sap.com/xi/XI/Message/30</SOAP:faultactor>
   <SOAP:faultdetail>
      <SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP:mustUnderstand="1">
         <SAP:Category>XIProtocol</SAP:Category>
         <SAP:Code area="PARSER">UNEXSPECTED_VALUE</SAP:Code>
         <SAP:P1>Main/@versionMajor</SAP:P1>
         <SAP:P2>000</SAP:P2>
         <SAP:P3>003</SAP:P3>
         <SAP:P4></SAP:P4>
         <SAP:AdditionalText></SAP:AdditionalText>
         <SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
         <SAP:Stack>XML tag Main/@versionMajor has the incorrect value 000. Value 003 expected
         </SAP:Stack>
      </SAP:Error>
   </SOAP:faultdetail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I made sure the business service in the integration directory is named SOAPRequest and is using SOAP as the communication channel. As the adapter engine I chose the integration server, since it is the only option, although the SOAP adapter framework is installed (according to the SLD) and deactivated any options like header and attachment.
Upon facing the above response I also tried any kind of derivative with inserting the described tag/attribute/element versionMajor, but to no avail.
My questions are:
What do I have to do additionally to get the whole thing running, i.e. configure my external systems in the SLD, providing proxy settings?
Do I have to create web services within the Web AS (which provide some kind of facade to the XI engine using the proxy generation) and connect to these instead of directly addressing the integration engine (I'm using the URL http://<host>:<port>/sap/xi/engine?type=entry, but I also tried http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:SOAPRequest:SOAPIn, this led to a 404 not found error)?
What settings do I have to provide to see the messages the client is sending, when looking into the runtime workbench it seems as if there are no messages at all - at least from my client?
Hopefully somebody might help me out or least provide some information to get me going.
Thanks in advance.
Best regards,
T.Hrastnik

Hello Oliver,
all information I gathered so far derives from the online help for XI 3.0, to be found under http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm. There You'll find - in the last quarter of the navigation bar on the left side - sections describing the adapter engine alonside the SOAP adapter.
Additionally I went through almost all postings in this forum.
This alonside the mandatory trial-and-error approach (I did a lot of it up to date) led me to my current status, i.e. so far I haven't found any kind of (simple) tutorial or demo saying "If You want to establish a web service based connection via SOAP between external applications and XI first do this, then that ...", sadly enough :-(.
Hope that helps, any questions are always welcome, I'll try my best to answer them ;-).
Best regards,
Tomaz

How many client connections will iMQ 2.0 handle?

My main concern is what the number of concurrent client connections (in a single instance) iMQ
can handle? This also depends on Hardware/Software configuration, JVM version (if it pure Java implementation), etc. But it also depends on Vendor implementation. For example FioranoMQ claims that can handling more than 5K concurrent client connections in a single instance of the FioranoMQ server without leading to any substantial performance degradation when a low number
of clients are connected to the server.

With proper tunning iMQ 2.0 can handle thousands of simultaneous connections.
For example on a modest Sun system (Sun Ultra 60/2300 (2x300MHz) 512MB ram)
We have run 4000 active connections without a problem. With more memory the
system could have supported more.
The iMQ FAQ gives some tuning guidelines for configuring the iMQ server
(the broker) to handle large number of connections. I'm attaching the
relevant excerpt (the online FAQ is a bit out of date).
When I try to connect more than 500 clients to the Broker's JMS service, performance gets really poor. Is there a way to configure the
Broker to handle more connections with better performance?
Yes. By default the JMS service's thread pool is limited to 1000 threads. The Broker runs best when it can allocate two threads per
connection. Once the thread pool limit is reached, threads are shared and performance decreases.
The solution is to:
1.Increase the thread pool limit for the JMS service so threads are not shared.
2.Configure the broker's socket read timeout so read threads fully block.
3.Configure the JVM to improve performance in highly threaded applications.
4.And if you are running on Solaris and plan on going over ~1000 connections you will also need to:
Increase the maximum number of open file descriptors per process.
Step 1: Increase thread pool limit for JMS service
Set the jmq.jms.max_threads property to be 2X the maximum number of connections you wish to support. For example if you want to
support 1000 connections you will need to set the property to 2000. You can do this by adding the following line to
$JMQ_VARHOME/stores/<broker instance name>/props/config.properties:
jmq.jms.max_threads=2000
Or by running jmqcmd:
jmqcmd update svc -n jms -o maxThreads=2000
Step 2: Configure the broker's socket read timeout
Set the jmq.protocol.timeout to 0 to cause read threads to fully block in read. Do this by adding the following line to
$JMQ_VARHOME/stores/<broker instance name>/props/config.properties :
jmq.protocol.timeout=0
Step 3: On Solaris pass additional parameters to the JVM
If you are running the broker on Solaris you should pass the following parameters to the JVM:
-Xss128k -Xconcurrentio
The first parameter reduces the per-thread stack size to 128k. The second adjusts several internal JVM parameters that significantly improves performance of highly concurrent applications.
You may pass these to the broker by using the -vmargs option to the broker command or you may choose to alter the $JMQ_HOME/bin/jmqbroker script by adding "-Xss128k -Xconcurrentio" to the line that starts with with "def_jvm_args". For example you would end up with a line that looks like:
def_jvm_args="-Xms8m -Xmx128m -Xss128k -Xconcurrentio"
Note that if your system has sufficient RAM you may also want to increase the JVM max heap size parameter (-Xmx128m).
Step 4: On Solaris Increase the maximum number of open file descriptors per process
This is covered in the iMQ 2.0 documentation. One way to do this is to run 'ulimit -n unlimited' in the shell you are going to run the broker in.

How to make mod_wl_20 handle multiple weblogic sources

Hi community,
I'm configuring an Oracle HTTP Server as a proxy of multiple weblogic instances.
For the case of the AdminServer, I modify httpd.conf as follow:
<IfModule mod_weblogic.c>
WebLogicHost myhost.example.com
WebLogicPort 7001
</IfModule>
<Location /console>
SetHandler weblogic-handler
</Location>
Now that I have configured 2 managed weblogic servers using port 8001 and 8002. How should I do so that both 2 managed weblogic servers are also proxied by the Oracle HTTP Server?
Thanks,
David

Hello
I suppose your managed nodes are located on address and port
10.a.b.d:7001 and 10.a.b.e:7001
and your admin is : 10.a.b.c:8001
you can try this :
<IfModule mod_weblogic.c>
WebLogicCluster 10.a.b.d:7001,10.a.b.e:7001
</IfModule>
<Location /your_app>
SetHandler weblogic-handler
</Location>
<Location /console>
SetHandler weblogic-handler
WebLogicCluster 10.a.b.c:8001
</Location>
It should work for you , it works for me . . . .

Access Manager Client SDK Java Usage with multiple OpenSSO instances

I am having some problems using the SDK / API for connecting to OpenSSO in a Java multi-threaded environment, while connecting to multiple instances of OpenSSO.
Is there a way to setup a new AuthContext that does not include 1) Use of global configuration AMConfig.properties or 2) Stick stuff in SystemProperties?
I see a constructor that takes an OpenSSO url, but the 2nd parameter seems to be ignored. .I.e. com.sun.identity.authentication.AuthContext.AuthContext(String orgName, URL url). I can login if I use the naming service url using "com.iplanet.am.naming.url" with the following code, but for this to work while connecting to multiple OpenSSO servers, I have to synchronized the calls and create the context each time I want to perform an API call.
THIS WORKS:
          String realm = "/";
          String strUrl = url.toExternalForm();
          // from AM server's AMConfig.properties
          Properties amEnv = new Properties();
          amEnv.setProperty("com.iplanet.am.naming.url", strUrl);
          amEnv.setProperty("com.iplanet.am.naming.failover.url", "");
          amEnv.setProperty("com.iplanet.services.debug.level", "message");
          amEnv.setProperty("com.iplanet.services.debug.directory", "/tmp/debug");
          amEnv.setProperty("com.iplanet.security.encryptor",     "com.iplanet.services.util.JSSEncryption");
          amEnv.setProperty("am.encryption.pwd", "BXo8vzOHob8FTpR6da+cSAi0TPLTH2Q/");
          SystemProperties.initializeProperties(amEnv);
          lc = new AuthContext(realm);
THIS DOESN'T:
          amEnv.setProperty("com.iplanet.am.naming.url", "");
          lc = new AuthContext(realm, strUrl);
In my ideal scenario, I'd like to cache a number of different AuthContext instances which connect to a number of different OpenSSO servers. When trying the second scenario, I get the following error message:
"Failed to create new Authentication Context: {0}"
Ideas?

Yep, that was me struggling with 2005Q4 before they released a patch (120954-03 if I am not mistaken).
1. Have you configured your AM installation as a site?
2. Have you added a secondary configuration in the session tab?
A restart will be required after that. Try setting log levels to debug. When AM webserver comes up and brings the application live, you'll see information regarding the secondary configuration, and whether things are actually in place or not.
Hope this helps.
Ankush
http://www.iamcg.net

Java client connecting to multiple weblogic instances

Similar Messages

Maybe you are looking for