Exit Session to an other client

Hello there
I've an ITS Application, which is using for the intranet in two different clients. We have different clients (mandt) for a Quality-systems.
Where is define the both URL for this both clients?
The problem is, when I logged out from a client in the intranet, than it goes return to the other URL client.
How can i difference the both clients? I know in the SICF I can define some things about the url (exiturl).
thanks

Hello OeA,
I am unable to understand your requirement. So I have assumed your requirement and answered accordingly.
Please find my understanding below.
1. You have an ITS applicaiton.
2. This application is transported to Quality System.
3. But the application is distributed across SAP clients.
4. So for the same ITS application you have two URLs to access the pages.
5. So let us assume that for logging into client1 you need to use URL1.
6. So let us assume that for logging into client2 you need to use URL2.
I assume that the you want to login to the URL2 during the URL1 logoff!
If this the requirement, then It should be possible to call the URL2 during an logoff user event inside the URL1, you can replace the existing window with the help of URL2 address via javascripts.
You just need to call the URL2 with an additional URL parameter (depending on the ITS application)
~client=<client.no.>
or
sap-client=<client.no.>
The URL2 can be formed dynamically with the help of present URL1 (only difference is the client)
Please expalin your problem clearly so that the readers should be able to understand your requirement and help you with their answers. Thanks!
Regards,
Maheswaran

Similar Messages

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
          clients. I also want this bean to have failover support so we want to
          deploy it in a cluster. The following description is how we have tried
          to solve this problem, but it does not seem to be working. Any
          insight would be greatly appreciated!
          I have set up a cluster of three servers. I deployed a stateful
          session bean with in memory replication across the cluster. A client
          obtains a reference to an instance of one of these beans to handle a
          request. Subsequent requests will have to use the same bean and could
          come from various clients. So after using the bean the first client
          stores the handle to the bean (actually the replica aware stub) to be
          used by other clients to be able to obtain the bean. When another
          client retrieves the handle gets the replica aware stub and makes a
          call to the bean the request seems to unpredictably go to any of the
          three servers rather than the primary server hosting that bean. If the
          call goes to the primary server everything seems to work fine the
          session data is available and it gets backed up on the secondary
          server. If it happens to go to the secondary server a bean that has
          the correct session data services the request but gives the error
          <Failed to update the secondary copy of a stateful session bean from
          home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          to the primary server will not reflect changes made on the secondary
          and vice versa. If the request happens to go to the third server that
          is not hosting an instance of that bean then the client receives an
          error that the bean was not available. From my understanding I thought
          the replica aware stub would know which server is the primary host for
          that bean and send the request there.
          Thanks in advance,
          Justin


          If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
          do you?
          Except of course if you switch ejb containers. Oh well.
          Mike
          "FBenvadi" <[email protected]> wrote:
          >I've got the same problem.
          >I understand from you that concurrent access to a stateful session bean
          >is
          >not allowed but there is a
          >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
          >that
          >does exactly what I need.
          >What you mean 'you'll get a surprise when you go to production' ?
          >I need to understand becouse I can still change the design.
          >Thanks Francesco
          >[email protected]
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Get the fix immediately from BEA and test it. It would be a shame to
          >wait
          >until
          >> December only to get a fix - that doesn't work.
          >>
          >> As for stateful session bean use - just remember that concurrent access
          >to
          >a stateful
          >> session bean is not allowed. Things will work fine until you go to
          >production
          >> and encounter some real load - then you will get a surprise.
          >>
          >> Mike
          >>
          >> [email protected] (Justin Meyer) wrote:
          >> >I just heard back from WebLogic Tech Support and they have confirmed
          >> >that this is a bug. Here is their reply:
          >> >
          >> >There is some problem in failover of stateful session beans when its
          >> >run from a java client.However, it is fixed now.
          >> >
          >> >The fix will be in SP2 which will be out by december.
          >> >
          >> >
          >> >Mike,
          >> >Thanks for your reply. I do infact believe we are correctly using
          >a
          >> >stateful session bean however it may have been misleading from my
          >> >description of the problem. We are not accessing the bean
          >> >concurrently from 2 different clients. The second client will only
          >> >come into play if the first client fails. In this case we want to
          >be
          >> >able to reacquire the handle to our stateful session bean and call
          >it
          >> >from the secondary client.
          >> >
          >> >
          >> >Justin
          >> >
          >> >"Mike Reiche" <[email protected]> wrote in message
          >news:<[email protected]>...
          >> >> You should be using an entity bean, not a stateful session bean
          >for
          >> >this application.
          >> >>
          >> >> A stateful session bean is intended to be keep state (stateful)
          >for
          >> >the duration
          >> >> of a client's session (session).
          >> >>
          >> >> It is not meant to be shared by different clients - in fact, if
          >you
          >> >attempt to
          >> >> access the same stateful session bean concurrently - it will throw
          >> >an exception.
          >> >>
          >> >> We did your little trick (storing/retrieving handle) with a stateful
          >> >session bean
          >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
          >sfsb's
          >> >were not
          >> >> replicated as yours are.
          >> >>
          >> >> Mike
          >> >>
          >> >> [email protected] (Justin Meyer) wrote:
          >> >> >I am trying to access the same stateful session bean from multiple
          >> >> >clients. I also want this bean to have failover support so we want
          >> >to
          >> >> >deploy it in a cluster. The following description is how we have
          >tried
          >> >> >to solve this problem, but it does not seem to be working. Any
          >> >> >insight would be greatly appreciated!
          >> >> >
          >> >> >I have set up a cluster of three servers. I deployed a stateful
          >> >> >session bean with in memory replication across the cluster. A client
          >> >> >obtains a reference to an instance of one of these beans to handle
          >> >a
          >> >> >request. Subsequent requests will have to use the same bean and
          >could
          >> >> >come from various clients. So after using the bean the first client
          >> >> >stores the handle to the bean (actually the replica aware stub)
          >to
          >> >be
          >> >> >used by other clients to be able to obtain the bean. When another
          >> >> >client retrieves the handle gets the replica aware stub and makes
          >> >a
          >> >> >call to the bean the request seems to unpredictably go to any of
          >the
          >> >> >three servers rather than the primary server hosting that bean.
          >If
          >> >the
          >> >> >call goes to the primary server everything seems to work fine the
          >> >> >session data is available and it gets backed up on the secondary
          >> >> >server. If it happens to go to the secondary server a bean that
          >has
          >> >> >the correct session data services the request but gives the error
          >> >> ><Failed to update the secondary copy of a stateful session bean
          >from
          >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
          >> >> >to the primary server will not reflect changes made on the secondary
          >> >> >and vice versa. If the request happens to go to the third server
          >that
          >> >> >is not hosting an instance of that bean then the client receives
          >an
          >> >> >error that the bean was not available. From my understanding I
          >thought
          >> >> >the replica aware stub would know which server is the primary host
          >> >for
          >> >> >that bean and send the request there.
          >> >> >
          >> >> >Thanks in advance,
          >> >> >Justin
          >>
          >
          >

(Cisco Historical Reporting / HRC ) All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054

Hi All,
I am getting an error message "All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054" when trying to log into HRC (This user has the reporting capabilities) . I checked the log files this is what i found out
The log file stated that there were ongoing connections of HRC with the CCX (I am sure there isn't any active login to HRC)
|| When you tried to login the following error was being displayed because the maximum number of connections were reached for the server . We can see that a total number of 5 connections have been configured . ||
1: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Current number of connections (5) from historical Clients/Scheduler to 'CRA_DATABASE' database exceeded the maximum number of possible connections (5).Check with your administrator about changing this limit on server (wfengine.properties), however this might impact server performance.
|| Below we can see all 5 connections being used up . ||
2: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:[DB Connections From Clients (count=5)]|[(#1) 'username'='uccxhrc','hostname'='3SK5FS1.ucsfmedicalcenter.org']|[(#2) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#3) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#4) 'username'='uccxhrc','hostname'='PFS-HHXDGX1.ucsfmedicalcenter.org']|[(#5) 'username'='uccxhrc','hostname'='47BMMM1.ucsfmedicalcenter.org']
|| Once the maximum number of connection was reached it threw an error . ||
3: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Number of max connection to 'CRA_DATABASE' database was reached! Connection could not be established.
4: 6/20/2014 9:13:49 AM %CHC-LOG_SUBFAC-3-UNK:Database connection to 'CRA_DATABASE' failed due to (All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054.)
Current exact UCCX Version 9.0.2.11001-24
Current CUCM Version 8.6.2.23900-10
Business impact Not Critical
Exact error message All available connections to database server are in use by other client machines. Please try again later and check the log file for error 5054
What is the OS version of the PC you are running and is it physical machine or virtual machine that is running the HRC client ..
OS Version Windows 7 Home Premium 64 bit and it’s a physical machine.
. The Max DB Connections for Report Client Sessions is set to 5 for each servers (There are two servers). The no of HR Sessions is set to 10.
I wanted to know if there is a way to find the HRC sessions active now and terminate the one or more or all of that sessions from the server end ?

We have had this "PRX5" problem with Exchange 2013 since the RTM version. We recently applied CU3, and it did not correct the problem. We have seen this problem on every Exchange 2013 we manage. They are all installations where all roles
are installed on the same Windows server, and in our case, they are all Windows virtual machines using Windows 2012 Hyper-V.
We have tried all the "this fixed it for me" solutions regarding DNS, network cards, host file entries and so forth. None of those "solutions" made any difference whatsoever. The occurrence of the temporary error PRX5 seems totally random.
About 2 out of 20 incoming mail test by Microsoft Connectivity Analyzer fail with this PRX5 error.
Most people don't ever notice the issue because remote mail servers retry the connection later. However, telephone voice mail systems that forward voice message files to email, or other such applications such as your scanner, often don't retry and
simply fail. Our phone system actually disables all further attempts to send voice mail to a particular user if the PRX5 error is returned when the email is sent by the phone system.
Is Microsoft totally oblivious to this problem?
PRX5 is a serious issue that needs an Exchange team resolution, or at least an acknowledgement that the problem actually does exist and has negative consequences for proper mail flow.
JSB

View change in the middle of sessions to Windows 7 clients with OneDrive

Some Windows 7 clients habe reported that the view changes in the middle of sessions to Windows 7 clients with OneDrive.
For example they have been able to see image pictures as normal in the beginning of sessions and then suddenly only image names !

Hi yourDragonXi,
Is it a desktop One drive or a web browser Onedrive content? According to your description, the should be a Sync process when you open the images, besides a screenshot will be helpful to find the explanation.
Thanks and Regards
Wade Liu
TechNet Community Support

How can i lookup a session bean from the client side

how can i lookup a session bean from the client side...........i am using sun appserver..............
this is my code.................[B]
private final static String JNDI_NAME="ejb/LmsBean";
private static String url="ldap://localhost:4848";
Hashtable h=new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
h.put(Context.PROVIDER_URL,url);
System.out.println("Before Loading Context in Delegate");
Context ctx=new InitialContext(h);
System.out.println("Loaded Context in Delegate");
Object obj=ctx.lookup(JNDI_NAME);
System.out.println("Loaded Object in Delegate");
System.out.println("Before Loading Home in Delegate");
LmsHome home = (LmsHome )PortableRemoteObject.narrow(obj,com.parx.lms.controller.LmsHome.class);
System.out.println("Loaded Home in Delegate");
lms = home.create();
System.out.println("Loaded remote in Delegate");
[B]and i got the exception........
Inside Client before calling delegate
Before Loading Context in Delegate
javax.naming.CommunicationException: Request: 1 cancelled
javax.naming.CommunicationException: Request: 1 cancelled
at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:405)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:171)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.ja
va:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.parx.lms.lmsdelegate.LmsDelegate.getController(LmsDelegate.java:3
0)
at com.parx.lms.lmsdelegate.LmsDelegate.addUserDelegate(LmsDelegate.java
:50)
at com.parx.lms.client.consoleClient.Client.main(Unknown Source)
pls go tru the exception and pls help.........

That url string should be having the server name or ip instead of localhost.

Maintain Http Session in a thick client

hi ,
Can anyone tell me how to maintain or recognise the session from a thick client. I am talking to the appserver by making the HttpUrl Connection object everytime, now i am making use of VLH and how do i recognise the httpsession object from the thick client for the second request.
Thanks in advance
Sane

In order to do this you would need to have code to support cookies or URL re-writing as a brower does. This would include interacting with the HTTP headers. This is not a trival task to try on your own. You might want to look at the source for the catcus testing framework (it supports this type of interaction).
http://jakarta.apache.org/cactus/

Deployment Problem "Exit status of DCM servlet client: -1"

I had a "Exit status of DCM servlet client: -1" problem at deployment, which is not yet reported.
Deployment from Jdeveloper 10.1.3.0.4.3673 to Application server 10.1.2.0.2 on Windows 2003 Server works on "home" OC4J but not on newly created OC4J instance. After comparing the two instances, I found the difference in the application.xml file. The Runtime Installer adds a list of library path statements at the end of this file:
<library path="../../../jlib/commons-el.jar"/>
<library path="../../../jlib/oracle-el.jar"/>
When I add these statements to the application.xml file of the newly created OC4J instance, the deployment works.

From the App Server oracle home, and with the same connection information as app is using, can you connect to 8.1.6 db with sqlplus?
You said it works from JDeveloper - which version?
From AS 10.1.2 (which means net/client libraries 10.1.0.3) I get
"ORA-03134: Connections to this server version are no longer supported."
To 8.1.7.4 database connection succeeds. (hint: 8.1.6 is not supported!)
Maybe this could be the culprit?

Differentiating between sessions created by same client

Hello,
Using JAVA Servlets and JSP how can I differentiate between session established by same client but using different browser windows.
Thanks
Niraj Rathi

maheshguruswamy wrote:
You don't have to do anything special. Each new browser window->new session. Just trace the session id passed around in the HTTP request, it will be different when the sessions are different.Partially wrong. That is only true if you use physically different browsers (firefox, IE, opera, etc.). If you open multiple windows of the same browser, they will each share the same session. And that is by design.

Can I download a file in different sessions or should it be in a single session? In other words can I pause the download of a file, shutdown/restart my system and then resume download from where I left off? Or will it start from the very beginning?

Can I download a file in different sessions or should it be in a single session? In other words can I pause the download of a file, shutdown/restart my system and then resume download from where I left off? Or will it start from the very beginning?

If a server supports resuming downloads then the download should continue where it left off.<br />
You can test that by simple starting a large download and wait a minute or so before pausing it.<br />
Then you can close and restart Firefox and see if resuming works.
You can set the pref browser.download.manager.quitBehavior to 2 on the about:config page.<br />
That will make Firefox ask for confirmation if you want to cancel the download if you close Firefox.
See:
* http://kb.mozillazine.org/browser.download.manager.quitBehavior

SAP QUERY does not execute in other client

Hi,
I am working on SAP QUERY on the Quality Assurance and Cust & Dev Client and i am facing a strange thing when i tried to execute the Query from SQ01 ,there i found itis not able to get executed but when i generated the report ,after that it get s executed.
I want to know what are the reasons behind it,please provide me guidelines for solving it.

See, SQ01 can not alone be used.
It is linked with the SQ02 - Funectional Area, where the joins handeled and codes implemented.
Also SQ03 - User Groups.
User Group you can ignore, but Functional Area is must to run a query through SQ01.
When you generate the Functional Area using SQ02, it activates all the objects associated with the Query.
So even if you need same query to some other client sayu in quality or production, you need to import export Functional area first before query or simultaneously.
Regds,
ANil

How to copy Partner Procedure from Downstream Template to all other clients

Hello,
My problem is SAP std Partner procedures (e.g. OTR) is not available in our freshly installed IS Oil Client. I found out SAP note no. "100151 - TD Partner procedures in IS-Oil bulk shipment" which is identical to my problem. However the said note does not contain how to copy Partner Procedure-OTR from Downstream Template to all other clients.
Can any one guide me in this area?
Thanks & Regards,
Aniruddha

Hello Aniruddha,
Partner determination configuration must be transported by creating a
manual transport.
Please refer to note 69385 and also notes listed in the "Related Notes" section for more details.
Best Regards,
Soumya

How to send the transport request from one client to other client?

Hello Friends,
I have generated one transport request in one of the client in Development server.Now as it is customizing request so unless and until i transport it to other client within the same server, Changes will not be visible in other clients.So how to transport this customizing request from one client to other client within the same server.
Thanking you guys in advance.
Regards,
Jitendra

Hi Jitendra,
Release your Transport Request via SE10, then go to STMS & import the request first to your quality server, then to your production server.
Apologies for the incorrect inputs, please use SCC1 as advised by other forum members
Hope the above clarifies your query.
Regards,
Vivek
Edited by: Vivek on Mar 16, 2009 1:05 PM

How to transport Minor changes in BPC 7.0 to other client

Hi,
I am very new to BPC and got an ticket to do a minor change in script logic. We are in BPC 7.0.
I am not sure how I can transport this minor change from Dev to other client.
My question is:
1. Do we need to make system offline while making changes to Script logic in BPC Admin or it is required only at the time of collecting transport request in BI using tcode: UJBPCTR?
It would be kind enough if any one could let me know What are all the activities we need to consider/take care before transporting objects from BPC DEV to BPC QUALITY
Thanks in Advance.
Regards, Trine

You only need to take it offline when executing UJBPCTR and when importing in the target system. The system willl collect all of the appset and transport it, but will do a delta calculation on the target system to determine if any structure changes are required. The script logic data should simply be overwritten.
Cheers,
Rich Heilman

I Have done my Objects in 300 Client.I want to Import it into other client

hi
I Have done my Objects in 300 Client.I want to Import it into other client.
What is the Procedure for that
Please clarify ASAP..
Thanks

Hi Venkata,
Go through these threads:
Copy the Classification Datasource from Client 300 to Client 010
Regards,
Subhasha Ranjan

Making Client able to talk to other Clients

so my sorta IM program have 3 major components: Server, ServerClient, and Client. th Server listens for incoming connection thru ServerSocket, and when a Client connects, a ServerClient thread is started. thus the Server can talk to the Client and vice versa. my question is, how should I make one Client talk to other Clients? the ServerClient threads are not aware of each other.
Thanks!

You can have a Vector for keeping all ServerClient threads. You could write a method that would find if the user is logged in and another that would send a message to him. I think some sort of simple protocol will be needed for transfering what the user wants to do (send a message to the server, find if a user is logged in, send a message to the user, etc.) with proper parameters, but this is irrelevant for now.
Of course this is just a suggestion. Maybe someone will have a better idea.
...:: byElwiZ ::...

Exit Session to an other client

Similar Messages

Maybe you are looking for