ADF - Session Management ? - what is processScope ?

Hi All,
We have recently started working on ADF using .Can any body please explain
What are the different ways to manage State other than backing bean.
More specifically i want to ask what is processScope? Is it like what we use Session in jsp.
One more thing we are using ADF-BC as Business componant no session beans and top link.
thanks in adv.
RHY

Process Scope is a scope supported by ADF Faces - it allows you to maintain state for longer than a request but shorter than the session (if required). It's mainly used to support Pop-up page dialogs and to pass back information from them to the calling page. List Of Values being a primary use case.
See the following URL:
http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/doc/devguide/communicatingBetweenPages.html
You can also use the session and the request directly with JSF although it's going to be better practice to use a managed bean to manage any state you have rather than coding direct to the Servlet API. Of course one of the advantages of using ADF to manage your bindings is that you don't have to manage the majority of your state, only the bits that ADFm is not managing.

Similar Messages

What's the role of jsessionids in ADF session management?

Hi all,
I'm fairly new to ADF and I've had a client ask me if ADF is using jsessionid consistently for sessionization.
From a quick google search it sounds like all J2EE applications will be using jsessionids as part of their session management, and it doesn't look too difficult to access this information programmatically. Can anyone elaborate for me on what exactly jessionids are and whether they are guaranteed to exist if a session of an ADF application has been instantiated? Basically I think I know the answer to my client's question is yes, but can anyone help me understand the role of jsessionids in ADF apps and other J2EE apps?

Hi.
This is a basic behavior in all Java application servers, as it is mandated by the Java Enterprise Edition specification. The ID is used to match the HTTP request to its session object. Basically, the web container will add jsessionid to the URL when the session id cannot be saved in a cookie. This behavior can also be enforced through settings in weblogic.xml, for example, if you are using WLS.
ADF is built on the top of JEE; consequently, it uses jsessionid in exactly the same way as any other Java application.
Best Regards,
Frédéric.

What is the difference between Session timeout and Short Session timeout Under Excel Service Application -- session management?

Under Excel Service Application --> session management; what is the difference between Session timeout and Short Session timeout?

Any call made from the API will automatically be set to the “Session Timeout” period, no matter
what. Calls made from EWA (Excel Web Access) will get the “Short Session Timeout” period assigned to it initially.
Short Session Timeout and Session Timeout in Excel Services
Short Session Timeout and Session Timeout in Excel Services - Part 2
Sessions and session time-outs in Excel Services
above links are from old version but still applies to all.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

What is new with MAX 2.0 and is it compatible with Session Manager?

We added non-IVI instrument information in, basically the same structure as for IVI instruments,
into the ivi.ini file to keep all instrument information in the same place. Using MAX Version 1.1 caused no problems whatsoever and the system worked fine. With the advent of MAX 2.0 you seem to use ivi.ini as well as config.mxs to store instrument information. What we have found now is that given a working ivi.ini file from MAX 1.1, we end up with 2 or 3 copies of all the devices in the IVI Instruments->Devices section! When the duplicate entries are deleted and the application exited, the
ivi.ini file is updated minus the [Hardware->] sections which contain the resource descriptors that our appl
ications look for. As an added complication, under MAX 2.1 (From an evaluation of the Switch Executive) It behaves the same, except that it almost always crashes with one of the following errors. 'OLEChannelWnd Fatal Error', or 'Error#26 window.cpp line 10028 Labview Version 6.0.2' Once opened and closed MAX 2.1 will not open again! (Note we do not have LabVIEW on the system.) What is the relationship between the config.mxs and ivi.ini now? Also, your Session Manager application (for use with TestStand) extracts information from ivi.ini and may expect entries to be manually entered into ivi.ini (e.g. NISessionManager_Reset = True) i.e. Is the TestStand Session Manager compatible with MAX 2.0?

Brian,
The primary difference between MAX 1.1 and 2.x is that there is a new internal architecture. MAX 2.x synchronizes data between the config.mxs and the ivi.ini. The reason you're having trouble is that user-editing of the ivi.ini file is not supported with MAX 2.x.
Some better solutions to accomplish what you want:
1. Do as Mark Ireton suggested in his answer
2. Use the IVI Run-Time Configuration functions. They will allow you to dynamically configure your Logical Names, Virtual Instruments, Instrument Drivers, and Devices. You can then use your own format for storing and retrieving that information, and use the relevant pieces for each execution. You can find information on these functions in the IVI CVI Help file located in Start >> National I
nstruments >> IVI Driver Toolset folder. Go to the chapter on Run-time Initialization Configuration.
I strongly suggest #2, because those functions will continue to be supported in the future, while other mechanisms may not be.
--Bankim
Bankim Tejani
National Instruments

How to implement the Session ManageMent in OracleADF .

Hi I am New to ADF, In my application i have requirement like, I Have a JSPX login page,which contain 4 taskflows as a regions(like AddEmp,DeleteEmp,Create New Dept,Delete Emp), based on the type of user login,i want give different responsibilities(ADF Security, for example a normal employe cant Edit the Other Employe information only HR can do the Edit ), for those who logged in i want to use Session.
Every Time When the user Request the resource it has to check for the session validation.
i know in JEE How to implement Sessions but i don't know in ADF .
Thanks in Advance...

Hi,
have a look here http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/AdfSecurity/AdfSecurity.html
Its a video about ADF Security that explains how you can use custom Resource Permissions for any kind of user authorization, plus the on-board page and task flow permission. Note that the session has nothing to do with authorization. All a session can be is authenticated after which users are associated with enterprise roles, which then are mapped to permissions (through application roles in ADF Security). So session management is not what you are looking for in this case.
In addition you want to read: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/76-insert-update-entity-protection-334421.pdf
Frank

Invalidating the ADF session and redirecting to EBS login screen

Hi ADF team,
I am developing an application which is being accessed from eBusiness Suite (EBS), using ADFX function. It has a global Logout link. When the link is clicked, two things should happen.
1. the ADF session that is running on WLS server should be killed.
2. I should be redirected to eBusiness Suite login page.
This is what I am doing and I am getting error(s).
1. Created a Container jspx page and embedded a task flow in it.
2. Embedded a jsff into task flow.
3. In JSFF created a global link called Logout.
4. Set the action property of Logout link such that it calls a function in the AMImpl. (I confirmed, the function is being called)
5. In the function invalidate the ADF session using following code.
HttpServletResponse response = ((HttpServletResponse)ADFContext.getCurrent().getEnvironment().getResponse());
HttpServletRequest request = ((HttpServletRequest)ADFContext.getCurrent().getEnvironment().getRequest());
HttpSession sessionADF = request.getSession();
sessionADF.invalidate();
return "EBSLogin";
6. Now, EBSLogin control flow leads to a URL View component that has the URL property set as "www.oracle.com".
--Using this approach I get the error: adfc-14000: view port id ****** is invalid
-----Thus need help with this error. Is there a better way to accomplish this ?? What am i doing wrong?
Also, I have a question on how to set the URL property of 'URL View' component. I set it to #{pageFlowScope.MainPageBean.testLogoutURL}. testLogoutURL is a function that returns string. But I do get an error at run time, mentioning that the property cannot be NULL. Thus seems like the way I am doing it is not totally correct. Please advice.
Thanks & Regards,
Anoop

on top of my head
        FacesContext fc = FacesContext.getCurrentInstance();
        ExternalContext ectx = FacesContext.getCurrentInstance().getExternalContext();
        HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
        HttpSession session = (HttpSession)ectx.getSession(false);
        String redirectURL = (String)session.getAttribute("ebizRedirectUrl");
        if(redirectURL!=null){
          int oa_html = redirectURL.indexOf("OA_HTML");
          finalRedirectURL = redirectURL.substring(0, oa_html);
          finalRedirectURL = finalRedirectURL + "oa_servlets/AppsLogin";
        if (session != null)
        session.invalidate();
        try {
            response.sendRedirect(finalRedirectURL);
            fc.responseComplete();
        } catch (IOException e) {
            e.printStackTrace();
        }

Session management in Info View with two different logins using single sign

There is a form with 2 user logins UserA and User B to redirect to infoview with sso in my application. I am able to go to each of the Infoview pages successfully but have the following problem.
User A logs in and infoview opens in a new IE window and sees his/her folders based on permissions and is able to do his/her work for the first time.
User B logs in andand infoview opens in a new IE window sees his/her folders based on permissions and is able to do his/her work for the first time.
After a while when User A tries to access the InfoView in the previously opened IE Window, he/she gets an error message. An error has occurred: The object with ID 2519 does not exist in the CMS or you don't have the right to access it.
User B is able to continue his/her work. Who ever logs in the last, he/she is able to continue his/her work but the other one gets an error.
Please let me know on how to address this issue . I added logonToken and tried everything at my hand but no success. Is this session controlled by business objects or by the jsp page. What more changes are required for my jsp page to fix the error. Attached below are the form and the applogon.jsp snippets.
 applogon.jsp
 IEnterpriseSession enterpriseSession = null;
 Exception failure = null;
 boolean loggedIn = true;
 String redirectURL = null;
 // If no session already exists, logon using the specified parameters.
 if (enterpriseSession == null){
 try{
 // Attempt logon. Create an Enterprise session manager object.
 ISessionMgr sm = CrystalEnterprise.getSessionMgr();
 // Log on to BusinessObjects Enterprise
 enterpriseSession = sm.logon(username, password, "cms", "secEnterprise");
 }catch (Exception error){
 loggedIn = false;
 failure = error;
 if (!loggedIn){
 // If the login failed, redirect the user to the start page.
 return;
 }else{
 // Store the IEnterpriseSession object in the session.
 session.setAttribute("EnterpriseSession", enterpriseSession);
 // Create the IInfoStore object.
 IInfoStore iStore = (IInfoStore) enterpriseSession.getService("InfoStore");
 // Store the IInfoStore object in the session using the helper functions.
 session.setAttribute("InfoStore", iStore);
 // Store the CMS name for later use.
 session.setAttribute("CMS", "CMS");
 // Create the IReportSourceFactory object.
 IReportAppFactory reportAppFactory =(IReportAppFactory)enterpriseSession.getService("RASReportService");
 // Store the IReportSourceFactory object in the session using the helper functions.
 session.setAttribute("ReportAppFactory", reportAppFactory);
 // Retrieve the logon token manager.
 ILogonTokenMgr logonTokenMgr = enterpriseSession.getLogonTokenMgr();
 String logonToken = logonTokenMgr.createLogonToken("", 60, 100);
 String infoViewURL = null;
 String tokenParam = null;
 infoViewURL = "/businessobjects/enterprise115/desktoplaunch/InfoView/logon/logon.do";
 tokenParam = "token=" + logonToken;
 redirectURL = infoViewURL + "?" + tokenParam;
 // Retrieve a logon token and store it in the user's cookie
 // file for use later.
 Cookie cookie = new Cookie("LogonToken", logonTokenMgr.createLogonToken("", 60, 100));
 response.addCookie(cookie);
 // Store the logon token for later use.
 session.setAttribute("token", enterpriseSession.getLogonTokenMgr().getDefaultToken());
 // Redirect the user to the relevant tutorial page.
 out.println("You have been logged on to Enterprise.");
 response.sendRedirect (redirectURL);
Thank You for your help

// Retrieve the parameters that the user entered into the logon fields.
 user name and password come from here from the above html form into the jsp here. Ted Is this what you are asking for where does the username and password come from
 String username = request.getParameter("user");
 String password = request.getParameter("pass");

 IEnterpriseSession enterpriseSession = null;
 Exception failure = null;
 boolean loggedIn = true;
 String redirectURL = null;
 ISessionMgr sessionMgr = null;
 // If no session already exists, logon using the specified parameters.
 if (enterpriseSession == null){
 try{
 // Attempt logon. Create an Enterprise session manager object.
 sessionMgr = CrystalEnterprise.getSessionMgr();
 // Log on to BusinessObjects Enterprise
 enterpriseSession = sessionMgr.logon(username, password, "appserver.abc.com", "secEnterprise");
 System.out.println("line61");
 }catch (Exception error){
 loggedIn = false;
 failure = error;
 if (!loggedIn){
 // If the login failed, redirect the user to the start page.
 return;
 }else{ this code is in my first post

Issue in session management

Hi All,
I have a problem regarding java session management.
i have created one web application in which i want if user login from one browser instance and opens another instance of same browser and logs in from that then user should be logged out from previous instance. I am using Mozzila 5.0.
Here is what i am doing while creating session in LoginServlet.java
session = request.getSession(false); //return session if already exists
System.out.println("Session object: "+session);
if(session != null)
System.out.println("Session ID Old: "+session.getId());
session.invalidate(); //invalidate the session if already exists
session = request.getSession(true); //Create new session
System.out.println("Session ID New: "+session.getId());
Second and third System.out.println() statements giving the same session id.
This way only the information stored in session when user was logged in from first instance of browser is replaced with the new information stored when the user logged in from second instance of browser, but the user is not logged out from the first browser instance.
Please help me out how i can log the user out from first instance if he logs in from second instance.
Thanks in advance...

Since user in logging again from the same machine so i think invalidating the previous session won't work.
Suppose user opens first instance of the mozilla browser and login as say 'ashok' whose role is normal user now he opens another instance of mozilla by clicking on executable and login as 'mitch' whose role is admin then after successful login of 'mitch' on first window mitch's menus items are getting displayed instead of ashok's.
What i am doing is,
While creating new session on login i first check is any existing session available in above case its true
session = request.getSession(false); //return session if already exists
System.out.println("Session object: "+session);
if(session != null)
System.out.println("Session ID Old: "+session.getId());
session.invalidate(); //invalidate the session if already exists
session = request.getSession(true); //Create new session
System.out.println("Session ID New: "+session.getId());
so control will go inside the if block, here i first invalidate the existing session (this is not destroying the session but only unbinding the information that was stored in the session) and create new session (this is returning the same session which was already exists) and save mitch's information. Since the previous instance was using the same session that will now get the mitch's information so now both instances will show the mitch's information.
I am not getting any way to destroy the existing session so next time new session id will get generated.

Bug in session manager. If you work for Sun, please take a look.

While evaluating what it would take to transition from Iplanet 6 to Sun Webserver 6.1, I found a problem with the Sun Webserver's s1ws60 session managers. If the page is not explicitly flushed before ending, the session cookie JSESSIONID is never sent. So as long as the user continues to visit small pages, they keep getting new sessions (because they are never sent a session id, so the session manager creates a new one every time they visit). The session cookie is sent if larger pages are visited (the buffer is automatically flushes). The session cookie is also sent if out.flushBuffer() is explicitly called within the JSP. This problem was not present in IWS6.0.
The problem has been tracked down to a combination of the code in com.iplanet.server.http.session.IWSSessionManager (found in the "plugins" directory) and the JSP's Java code generated by a component of the webserver (Catalina?). Under Iplanet, the code generated in the finally{} section of the JSP first flushed the buffer, then called releasePageContext. Under Sun Webserver, the code generated just calls releasePageContext without explicitly flushing the buffer before the call. When flushing the buffer for a non-committed response, the headers are first generated and sent, along with any cookies, including the session cookie. The server only sends the session cookie if, among other things, the session satisfies "_session.isNew()". The order of events in releasePageContext ensures that this is never true when used in combination with IWSSessionManager. I don't have the source code to verify this, but from experimentation I think this is the reason: Before the buffer is flushed, the session is saved by IWSSessionManager.update(session), which at line 498 calls "sn.unsetNew()". So the session is never isNew() when it gets around to sending the session cookie. This can be resolved by either adding an explicit buffer flush to the finally{} section of the JSP, or removing the unsetNew() call from IWSSessionManager. Since I don't know where the code that generates the JSP is (or if I can even change it), I ended up removing the sn.unsetNew() call from the update() function.
Here's the code generated in the finally{} section using IWS6 and Sun Webserver:
Iplanet 6
        } finally {
            if (out != null && (out instanceof org.apache.jasper.runtime.JspWriterImpl)) {
                ((org.apache.jasper.runtime.JspWriterImpl) out).flushBuffer();
            if (_jspxFactory != null) _jspxFactory.releasePageContext(pageContext);
        }Sun Webserver
        } finally {
            _jspx_releaseTags(_jspx_curTag, null);
            if (_jspxFactory != null) _jspxFactory.releasePageContext(pageContext);
        }

I posted a bug report on this.

JMF error - Format of Stream not supported in RTP Session Manager

java.io.IOException: Format of Stream not supported in RTP Session Manager
at com.sun.media.datasink.rtp.Handler.open(Handler.java:139)
why this erro occors?
I already created the DataSink.
When I try to do this...
dsk.open(); //here the error got
dsk.start(); Code of server of media
I want to sent audio (wav) like a radio, but from file. Without stop to send streaming. PullBufered
*Class Server that you offers Streaming of midia
public class Servidor {
private MediaLocator ml;
private Processor pro;
private javax.media.protocol.DataSource ds;
private DataSink dsk;
private boolean codificado = false;
//start the server service, passing the adress of media
// ex: d:\music\music.wav
// pass the ip and port, to make a server works
public void iniciarServicoServidor(String end,String ip, int porta)
try {
//capture media
capturarMidia(end);
//creates processor
criarProcessor();
// configure the processor
configurarProcessor();
//setContent RAW
descreverConteudoEnviado();
//format the media in right RTP format
formatRTP();
//creat the streaming
criarStreaming();
//configure the server
configurarServidor(ip, porta);
//in this method raise the excepition
iniciarServidor();
//when I try to open the DataSink.open() raises the exception
//java.io.IOException: Format of Stream not supported in RTP Session //Manager
// at com.sun.media.datasink.rtp.Handler.open(Handler.java:139)
} catch (RuntimeException e) {
System.out.println("Houve um erro em iniciarServicoServidor");
e.printStackTrace();
public void capturarMidia(String endereco)
try {
System.out.println("**************************************************************");
System.out.println("Iniciando processo de servidor de multimidia em " + Calendar.getInstance().getTime().toString());
ml = new MediaLocator("file:///" + endereco);
System.out.println("Midia realizada com sucesso.");
System.out.println ("[" + "file:///" + endereco +"]");
} catch (RuntimeException e) {
System.out.println("Houve um erro em capturarMidia");
e.printStackTrace ();
public void criarProcessor()
try {
System.out.println("**************************************************************");
pro = Manager.createProcessor(ml);
System.out.println("Processor criado com sucesso.");
System.out.println("Midia com durcao:" + pro.getDuration().getSeconds());
} catch (NoProcessorException e) {
System.out.println("Houve um erro em criarProcessor");
e.printStackTrace();
} catch (IOException e) {
System.out.println ("Houve um erro em criarProcessor");
e.printStackTrace();
public void configurarProcessor()
try {
System.out.println("**************************************************************");
System.out.println("Processor em estado de configura��o.");
pro.configure();
System.out.println("Processor configurado.");
} catch (RuntimeException e) {
System.out.println("Houve um erro em configurarProcessor");
e.printStackTrace();
public void descreverConteudoEnviado()
try {
System.out.println("**************************************************************");
pro.setContentDescriptor(new ContentDescriptor(ContentDescriptor.RAW));
System.out.println("Descritor de conteudo:" + pro.getContentDescriptor().toString());
} catch (NotConfiguredError e) {
System.out.println("Houve um erro em descreverConteudoEnviado");
e.printStackTrace();
private Format checkForVideoSizes(Format original, Format supported) {
int width, height;
Dimension size = ((VideoFormat)original).getSize();
Format jpegFmt = new Format(VideoFormat.JPEG_RTP);
Format h263Fmt = new Format(VideoFormat.H263_RTP);
if (supported.matches(jpegFmt)) {
// For JPEG, make sure width and height are divisible by 8.
width = (size.width % 8 == 0 ? size.width :
(int)(size.width / 8) * 8);
height = (size.height % 8 == 0 ? size.height :
(int)(size.height / 8) * 8);
} else if (supported.matches(h263Fmt)) {
// For H.263, we only support some specific sizes.
if (size.width < 128) {
width = 128;
height = 96;
} else if ( size.width < 176) {
width = 176;
height = 144;
} else {
width = 352;
height = 288;
} else {
// We don't know this particular format. We'll just
// leave it alone then.
return supported;
return (new VideoFormat(null,
new Dimension(width, height),
Format.NOT_SPECIFIED ,
null,
Format.NOT_SPECIFIED)).intersects(supported);
public void formatRTP()
try {
// Program the tracks.
TrackControl tracks[] = pro.getTrackControls();
Format supported[];
Format chosen;
for (int i = 0; i < tracks.length; i++) {
Format format = tracks.getFormat();
if (tracks[i].isEnabled()) {
supported = tracks[i].getSupportedFormats();
// We've set the output content to the RAW_RTP.
// So all the supported formats should work with RTP.
// We'll just pick the first one.
if (supported.length > 0) {
if (supported[0] instanceof VideoFormat) {
// For video formats, we should double check the
// sizes since not all formats work in all sizes.
chosen = checkForVideoSizes(tracks[i].getFormat(),
supported[0]);
} else
chosen = supported[0];
tracks[i].setFormat(chosen);
System.err.println("Track " + i + " is set to transmit as:");
System.err.println(" " + chosen);
codificado = true;
} else
tracks[i].setEnabled(false);
} else
tracks[i].setEnabled(false);
} catch (RuntimeException e) {
// TODO Auto-generated catch block
e.printStackTrace();
public void tocar()
pro.start();
public void criarStreaming()
try {
System.out.println("**************************************************************");
if (codificado)
System.out.println("Midia codificada...");
System.out.println("Processor entra em estado de realize.");
pro.realize();
System.out.println("Processor realized.");
System.out.println("Adquirindo o streaming a ser enviado.");
ds = pro.getDataOutput();
System.out.println("Streaming adquirido pronto a ser enviado.");
} catch (NotRealizedError e) {
System.out.println("Houve um erro em criarStreaming");
System.out.println(e.getMessage());
e.printStackTrace();
catch (Exception e) {
System.out.println(e.getMessage());
public void configurarServidor(String ip, int porta)
System.out.println("**************************************************************");
String url = "rtp://" + ip + ":" + porta + "/audio/1";
System.out.println("Servidor ira atender em " + url);
MediaLocator mml = new MediaLocator(url);
System.out.println("Localizador de midia ja criado");
try {
System.out.println("Criando um DataSink a ser enviado.");
dsk = Manager.createDataSink(ds, mml);
System.out.println("DataSink criado.");
} catch (NoDataSinkException e) {
e.printStackTrace();
public void iniciarServidor()
try {
System.out.println("**************************************************************");
dsk.open();
System.out.println("Servidor ligado.");
dsk.start();
System.out.println("Servidor iniciado.");
} catch (SecurityException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
Gives that output console.
All methods are executed but the last doesnt works.
The method that open the DataSink.
What can I do?
Iniciando processo de servidor de multimidia em Sun May 13 22:37:02 BRT 2007
Midia realizada com sucesso.
[file:///c:\radio.wav ]
Processor criado com sucesso.
Midia com durcao:9.223372036854776E9
Processor em estado de configura��o.
Processor configurado.
Descritor de conteudo:RAW
Midia codificada...
Processor entra em estado de realize.
Processor realized.
Adquirindo o streaming a ser enviado.
Streaming adquirido pronto a ser enviado.
Servidor ira atender em rtp://127.0.0.1:22000/audio/1
Localizador de midia ja criado
Criando um DataSink a ser enviado.
streams is [Lcom.sun.media.multiplexer.RawBufferMux$RawBufferSourceStream;@a0dcd9 : 1
sink: setOutputLocator rtp://127.0.0.1:22000/audio/1
DataSink criado.
Track 0 is set to transmit as:
unknown, 44100.0 Hz, 16-bit, Stereo, LittleEndian, Signed, 176400.0 frame rate, FrameSize=32 bits
java.io.IOException: Format of Stream not supported in RTP Session Manager
at com.sun.media.datasink.rtp.Handler.open(Handler.java:139)
at br.org.multimidiasi.motor.Servidor.iniciarServidor(Servidor.java:291)
at br.org.multimidiasi.motor.Servidor.iniciarServicoServidor(Servidor.java:43)
at br.org.multimidiasi.motor.ConsoleServidor.main(ConsoleServidor.java:30)
Since already thanks so much.
Exactally in this method raises erros.
Ive tried another formats (avi, mp3) but all with the same error, what I can do?
[code] public void iniciarServidor()
try {
System.out.println("**************************************************************");
dsk.open();
System.out.println("Servidor ligado.");
dsk.start();
System.out.println("Servidor iniciado.");
} catch (SecurityException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
Track 0 is set to transmit as:
unknown, 44100.0 Hz, 16-bit, Stereo, LittleEndian, Signed, 176400.0 frame rate, FrameSize=32 bits
java.io.IOException: Format of Stream not supported in RTP Session Manager
at com.sun.media.datasink.rtp.Handler.open(Handler.java:139)
at br.org.multimidiasi.motor.Servidor.iniciarServidor(Servidor.java:291)
at br.org.multimidiasi.motor.Servidor.iniciarServicoServidor(Servidor.java:43)
at br.org.multimidiasi.motor.ConsoleServidor.main(ConsoleServidor.java:30)

unknown, 44100.0 Hz, 16-bit, Stereo,
LittleEndian, Signed, 176400.0 frame rate,
FrameSize=32 bits
java.io.IOException: Format of Stream not supported
in RTP Session Manager
The fact that it doesn't know what the format is
might have to do with the problem. I've had similar
problems, and I've traced it back to missing jars and
codecs. Have you tried running the same code locally
without the transmission to see if you player will
even play the file?Already and it works, I used Player to play it and play normally, I try to make it with the diferents codecs of audio and video, but no sucess.

How to permanently turn off the Session Management alert

Hello,
I have a certain iView that is working through https.
Whenever I go to this iView I receive this pop up:
Session Management will not work!
You can turn off this alert inside 'Support Desk' -> 'SAP Application'
I am turning this alert off and I don't see it anymore but after we are doing a server restart it is turned on again and again I need to turn it off.
How can I turn this alert off permanently, even after a server restart?

yes its all a bit strange isnt it ...... the AlertSessionManagementMismatch appears to be runtime in nature - in that if you disable the session management alerting using the support desk approach - this value becomes false. Yet a restart doesnt keep it at false.
What I discovered is - IGNORE what you see when you edit the service - change it physically to FALSE (even if it says false) and save it. This will persist it at the next restart.
Haydn

Plugin based Web Service with session management

I am trying to make a web service in java with jax-ws that should support extensions to the service without rebuilding the project. I thought it might be possible to make a standard web service and the let each plugin create their own service, making the client side plugin point to both the standard service and the plugin specific one. This way I could have user management and such in the standard service and the more plugin specific one in an other service. The problem is though, how do I make a common session for all the services? All services are running at the same server and on the same domain name.
I checked the HTTP headers and found out that the JSESSIONID was changing when I created a new port on the client side. I was trying to implement a SOAPHandler to edit the cookie in the HTTP header, hoping that this will lead to the same session across the services. But found it hard. It was no problem reading the "Set-cookie" header, setting the cookie on the new requests was harder, as the CookieJar object seems to be internal [1]. And the MessageContext.HTTP_REQUEST_HEADERS wasn't created at the time my handlers run. Is there an easy solution to this?
I am not sure if my idea is a good solution to the main problem, and all other ideas are more than welcome. I hope it is possible to extend the features of my server without rebuilding the project. If anything is unclear, feel free to ask :)
[1] com.sun.xml.internal.ws.client.http.CookieJar

Adhir_Mehta wrote:
Could you explain plug in scenario with one example?Ok. We have not chosen exactly how to do this, but the idea is that someone may be able to extend the functionality of our server without rebuilding the project. We thought of something like a jar file with a implementation of some abstract classes. It should at least only be necessary to redeploy the project into the web container. The problem is; how do we let the plugins extend our web interface? One solution we thought of was to let each plugin have it's own service and dynamicly link to the plugin services from the main service that we provide as standard in our server. This way we may have some kind of plugin support on the clients as well, making the client side plugins know what kind of service it needs on the server side and thus extending the functionality all together.
Hope that explains our scenario. Feel free to comment and add new ideas :)
Regarding session management, its not advisable to manage the session in web services since that way it will become non interoperable.The documentation we found regarding sessions and jax-ws was all doing sessions with HTTPSessions, and to let the web container handle that.
On the server side
    @Resource
    private WebServiceContext wsContext;
    private HttpSession getSession() {
        MessageContext mc = wsContext.getMessageContext();
        return ((javax.servlet.http.HttpServletRequest)mc.get(MessageContext.SERVLET_REQUEST)).getSession();
    HttpSession session = getSession();
    session.setAttribute("User", user);On the client side
((BindingProvider)port).getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY,true);Do you have other standard options for us on how to do session management? All ideas are more than welcome

Web service authentication/session management using Axis2

I'm creating a web service using Axis2 where the client will need to login to the service and maintain a session. I'm trying to figure out a good way to do this. I've read the article on the following link:
http://www.developer.com/services/article.php/3620661/Axis2-Session-Management.htm
and it describes 4 main ways of doing this: Request Session Scope, Soap session scope, Transport session scope, and Application scope. However, it doesn't give much detail in actually implementing this. It says to add a parameter to services.xml like this:
<service name="foo" scope=" transportsession">
</service>
but what about the actual code that goes in the server and client to actually handle the login process and verify the username/password in an SQL database on the server? I'm having a lot of trouble finding a good tuturial on this. Can anyone point me in the right direction? I'm also open to other ideas that don't necessarily directly involve Axis2.

Session management for a web service and already answered. Locking.

Database session management in APEX

How is the database session managed in APEX? I found that sometimes a database session can last from page to pages in an APEX application, but sometimes every page starts a new database session.
Is there a way to control the database session in APEX?
Thanks,
-Fengting

Since HTTP is a stateless and connectionless protocol, you are not guaranteed to get the same database session between pages. APEX maintains the session state implicitly. Each session is assigned a unique identifier with APEX. The APEX engine uses the session ID to store and retrieve the applications working set of data or session state before and after each page view.
The session information persists in the database until purged. Therefore, as long as the client's session cookie has not expired, a user can continue running the application long after having first launched it. This is also what allows a user to run multiple instances of an application simultaneously in different browser sessions.
That being said, I think the answer to your question is that it is not necessarily going to be the same database session (but could be), nor can you control it. You should use session state.

Is it possible to use run-time configuration in conjunction with Session Manager?

I'm trying to avoid using MAX, basically because it's a pain for users to configure MAX when the application already knows what the configuration is. I actually get the configuration from a database, but that's another story. I've experimented with run-time configuration (see page 4-31 of the 'IVI Driver Toolset' manual) and it works fine. However, when I try to use this in conjunction with Session Manager, session manager complains that my logical name is not a driver session name. I suspect that Session Manager is looking up logical names from a different source, therefore run-time configuration won't work. Any suggestions? I've attached the files I'm working with.
Attachments:
SessionMgrTrial.zip ‏41 KB

Hello Mark:
The Session Manager GetLogicalNames method does not distiguish between logical names and virtual instrument names. A user of the method cannot ask for just logical names or just virtual instrument names. Right now you always get both. The new function is called InstrSessionMgr.GetNames. Notice that the online help file says Boolean for the flags parameter when it is an enum.
Hope this helps. If you have any further queries, please let us know.
-NI support
National Instruments - Software IS the instrument!
Attachments:
help.gif ‏22 KB

ADF - Session Management ? - what is processScope ?

Similar Messages

Maybe you are looking for