URGENT: Browser support w/BEA Portal (Platform 7)

Hey,
I just "noticed" that officially, the supported IE browser for BEA Platform 7
is v.5 or above.
My question is, what specifically is not supported with an older IE browser -
v4.0.1 actually. As it is, I would have to deploy to a corporate platform that
is currently using IE 4.0.1. That cannot change in the near future - so if IE
4.0.1 will NOT work with BEA Portal, I have a problem.
Thanks...
Nick Miron
CGI Services to BCE

Similar Messages

Version of browser supported

Where can I find the list of browser supported for the portal server v3sp4hp2

Hi,
You can look at the following URL
http://docs.sun.com/source/816-6140-10/ch1.htm#13538
This gives you the list of the browsers supported in SP4. I dont think there is any change for SP4 HP2
HTH

WSRP Support Kit for WebLogic Platform 8.1 SP2

The WSRP Support Kit for WebLogic Platform SP2 has just been released at
http://dev2dev.bea.com/products/wlportal81/articles/wsrp_support_kit.jsp.
Please note that this is a preview release, and requires WebLogic
Platform 8.1 SP2.
Regards,
Subbu

There is a release planned for mid Summer, but it is too early to confirm.
In case you must add WSRP support to apps in platform domain, you can do
so manually, and here are the steps.
- Create a platform domain before installing WSRP Support Kit.
- Create a portal domain after installing WSRP Support Kit.
- Replace <Security> element in config.xml in the platform domain with
the one from portal domain.
- Add wsrp-common.jar file to the system classpath for the platform domain.
Let me know if this helps.
Subbu
Murtaza Sonaseth said the following on 01/07/2004 02:51 PM:
Is there an planned final release date for WSRP or at least a rough timeframe?
Thanks,
M Sonaseth.

8.1 equivalent of portlet:form event=bea.portal.framework.internal.refresh

I've got a portlet with an edit JSP that allows the user to set some portlet settings. The edit JSP uses a form defined with the tag <portlet:form event="bea.portal.framework.internal.refresh" >. This in essence allowed the edit JSP to submit the form to itself, so it could then process (store) the settings.
This tag is no longer supported in 8.1. I haven't been able to find what the equivalent is. Am I going to be able to do the same thing, or am I going to have to rewrite the Edit piece as a page flow?

I've already tried that and it's not working in my current portal.
The other things I've tried are <render:postBackUrl/> and <render:windowUrl> for the form action, and they weren't working, either. But since then I've discovered that in a new vanilla portal installation, the <render:postBackUrl/> action works fine (I assume the controller would, too, but I didn't try it).
It seems I now have a different problem to work through to figure out why <render:postBackUrl/> works in a new installation, but not in my current one. The same goes for the controller.

How to implement multlingual on bea portal books and pages

Hi
We are are using BEA weblogic portal.
Now we want to use multilingual on bea portal.
Ho we can change the portal book's name and pages according to languages.
Regards
Paramdeep Singh

In your browser, you maintain your list of desired languages. This is an ordered list with the first language/locale in the list being the primary. This list of languages is passed to the server in as header. The portal server uses this header as the default mechanism to determine the language to serve back to the browser, although this behavior can be changed for your implementation if you wish. The server will look for a matching resource bundle based on the order of preference in your list of accepted languages.
So, if you want to receive fr_FR responses, ensure the fr_FR is listed first in your browsers list of languages and that you have created fr resources in your portal.
Brad

Possible/supported to use portal 7.1 with 64 bit java?

Hi!
Our portal machines in productive environment have 16 GB ram and I would like to use them. But 32 bit java does not support this. (Linux platform)
So, the simple question is:
Can I install a 64 bit JDK (e.g. 50 Update 12) and run portal with it?
1) Does it work?
2) Is it supported?
Please note that I have no pressing urge to upgrade at the moment, 3GB heap seem to be sufficient for now but I just want to know. Also if there are future plans to allow this...
Thanks, Chris

Hello Martin,
The E-commerce 5.0 guide for ERP, says that the minimum version supported is 4.6C with the specific patch level version. We had issues initially with the TREX 7.0 installation on 64 bit windows ( lot of modifications have to be done manually here).
But now TREX 7.0 is working fine and i can see the replication happeing from R/3 4.6C. We are configuring the webshops and doing all the XCM settings currently so, would be able to tell in a days time, if it works for us or not.(with 4.6C).
Thanks,
Dipender Singh

SAP Netweaver browser support for Windows 7 OS

Hi,
can anyone provide the SAP Netweaver Portal browser support matrix for Windows 7 OS?
I could see SAP NetWeaver 7.00 Browser Support For End Users and Admin Functionality in case of Windows XP and Vista but not for Windows 7. Where can I find this information? Does SAP provided any info on this?
Regards,
Ravi.

Hi Ravi ,
win7+IE 8 will be compatible with EP 7.0 starting SP21 onwards . For more details pls check PAM - https://websmp108.sap-ag.de/pam .
Regards
Mayank

What determines whether 3D is supported on a given platform?

I'm using the 2.0 beta (build 34) on Windows 7... when I call Platform.isSupported( ConditionalFeature.SCENE3D ), I get a result of 'false'.
What determines whether or not 3D is supported on a given platform?

I just found the resolution to my problem in Jira, at: http://javafx-jira.kenai.com/browse/RT-14415
Specifically, this comment:
The minimum driver version for Intel HD was recently changed to 8.15.10.2302 to workaround bugs in older drivers.
If you run JavaFX as follows, it will show you your driver version number, and also print the minimum version number.
1. Set the environment variable NWT_TRACE_LEVEL=4
2. Run any JavaFX program with: java -Dprism.verbose=true ...

Problem with LDAP in BEA Portal

Problem with LDAP in BEA Portal
I have a list of 50 user which should be cerated in portal staging(devlopment) machine and should be transfered to
production machine using LDAP
Steps which i followed to create Users
1.Create User Profile with 2 parameters branch and Role
2.I have list user in the Xls file with Username,password ,branch and Role
3.Write a java File which will read the Xls File
4.The users are created in the staging machine for the portal
Steps which i followed in LDAP to tranfer the created User form Devlopment to Production
1.Export the created user from Devlopment (which was moved as .DAT in my local directory)
2.import the user from local direcory to production machine
The Users are imported in the production machine with username and password but the role and branch values are empty
We need a solution for importing the user with role and branch corresponding to each user.
Thanks in Adv
Suresh

In Portal 8.1, user name and password in stored in LDAP where as user profile values are stored in database. That is the reason you are not able to see the user profile values.
Check once again whether you can see these values through admin tool. In case,it is not(after confirmation again),you might have to use APIs to do this for you incase you dont want to manage through Admin Tool.
Thanks,
Prashanth Bhat.

No Optimized web browser support on basic phones after 8/30/13?

Over the weekend I received a very disturbing message on my web browser. of my Samsung Gusto 2. It said that there would be no Optimized web browser support on basic phones after 8/30/13 and that if I wanted a good web browsing experience that I would have to upgrade to a smartphone. I am on the $50 unilmited talk,text,and web prepay plan but don'\t want to get stuck paying for a web browser I can't use after that date.A smartphone monthly plan would cost $10-20 more monthly,in addition to spending considerably more to buy a smartphone. I already have a tablet and was told a smartphone was unnecessary. Anybody else get this message?One person in customer service said that it was propaganda and not to believe it. Another person that I called later found the memo but had no further information on it at this time. Aparently Verizon likes to keep their customer service associates in the dark until last minute.No idea if they will alter their price plans in light of this development. I currently have AT&T U-Verse and will move my number to them and switch providers if forced to.They are willing to offer the same plan I currently have with Verizon but will have to buy a new AT&T GoPhone. Have had pretty good customer service with them up to now,but they are not open 24/7 for wireless customer service. Any comments?

Hi Melissa
Right now I am switching back and forth between the Samsung Gusto 2 and the original Gusto. The reason I am doing this is because the Gusto ,even though it is an older phone, is in much better condition than the newer Gusto2. I want to use the beat-up Gusto2 for work, and switch to the other phone when I need a more presentable phone.Also have a Verizon Wireless CDM 7076(somewhere).
Don't know why I am being forced to replace perfectly good phones. And yes,SydneyK, I could use my tablet for data,but it is a little cumbersome to take it out with me,but don't need it for my work . I just took it out for the first time recently to see how well it works on Wi-Fi hotspots(I don't have or want a data plan).Because I am a U-verse customer,I have access to 30,000 AT&T Wi-Fi hotspots AT NO ADDITIONAL CHARGE. I don't want to pay for something (web access)that I can't use on this phone. If Verizon can't give me cost-effective solutions,then I will be forced to transfer my number to AT&T Wireless as of August 30 for a GoPhone. AT&T wants my business and are wiling to do anything to satisfy me. Haven't had any trouble with Verizon either. Yes, their customer service is still available 24/7 even thought you will have to wait a while sonetimes. I just hate the thought of having to go through the hassle of transferring my number to another carrier.
Marc

Out of the box porlets for Content Management with BEA Portal

I am looking at BEA Portal for a simple Intranet site with some basic content management system capabilities. I would like to implement this without the use of a third party tool and wanted to know if there are any open source or out of the box BEA portlets/web-apps with basic CMS capabilities beyond what has been shown in the Portal tutorials around CMS. From doing the tutorials, I have learned how to manage content, and how to build a site from scratch to access the content using the <cm:> tags. However, without additional third party products such as Documentum or Interwoven, is there any free BEA/open source portlets to:
- Configure exposure of this content in a runtime framework? (ie content manager can expose new content from the repository by a configurable admin GUI, place where this content is on the page)
- Allow for a simple approval workflow where content that gets added to the repository by user A has to be approved by user B before automatically exposing?
Interested to know if custom portal type development is the only way to do these kind of simple functions, or third party product.

Hi,
Did you have a chance to look into WebLogic Portal 8.1 SP3? Check out the new Library Services features, which includes versioning and simple approval:
http://e-docs.bea.com/wlp/docs81/adminportal/help/CM_MAN_LifecycleOV.html
We also provide a few ootb portlets that allow users to interact with the CM system. Let us know if you have additional questions.
Best Regards,
--alex

Integrate with BEA Portal and Lotus Domino R5.0.12

Deal all:
I got a problem when I integrate with BEA Portal and Lotus Domino R5.0.12.
my environment is below:
- Domain Server :
Lotus Domino Server R5.0.12
BEA Personal Messaging API 4.3
(test successful on local host)
- Application Server:
BEA Weblogic 8.15
BEA Groupware portlets 2.5
I got connection successful message when I using "Domino Service Connection"
but I got "CZ: VERSION CONFLICT" error message when I add a new account by
Compoze_Groupware-Edit Account user interface.
Have anybody met the error message before... and know how to sovle the problem..
I appreciated any suggest or comment~~~
detail error message is below:
portlets.compoze.groupware.exception.ConnectionException: CZ: VERSION CONFLICT at portlets.compoze.groupware.controls.provider.SessionControlImpl.createSession(SessionControlImpl.jcs:142) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:381) at $Proxy19.createSession(Unknown Source) at portlets.compoze.groupware.controls.provider.GroupwareProviderControlImpl.updateAccount(GroupwareProviderControlImpl.jcs:4825) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406) at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:249) at com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:85) at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224) at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:109) at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:207) at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153) at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54) at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:168) at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:46) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161) at com.bea.wlw.runtime.core.dispatcher.ServiceHandleImpl.invoke(ServiceHandleImpl.java:436) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl._invoke(WlwProxyImpl.java:326) at com.bea.wlw.runtime.core.dispatcher.WlwProxyImpl.invoke(WlwProxyImpl.java:315) at $Proxy11.updateAccount(Unknown Source) at portlets.compoze.content.options.accounts.editAccount.editAccountController.saveChangesAccountAction(editAccountController.jpf:534) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wlw.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:1512) at com.bea.wlw.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:1447) at com.bea.wlw.netui.pageflow.FlowController.internalExecute(FlowController.java:778) at com.bea.wlw.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:211) at com.bea.wlw.netui.pageflow.FlowController.execute(FlowController.java:608) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1504) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:674) at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527) at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1734) at com.bea.wlw.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1754) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:561) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:121) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:150) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:109) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:224) at com.bea.netuix.nf.ControlLifecycle$3.visit(ControlLifecycle.java:171) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:355) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:365) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:126) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:173) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:150) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Hi,
The reason why you are seeing this exception is because there is a mismatch between the version of the WLPM API used by the portlets, with the version of the service that you have installed on you Domino server.
To explain a little, there are two sides to the API that is used to communicate with Lotus Domino:
1) the Java API side (used by the portlets that you have installed in the portal)
2) the Domino Service side (installed as a DSAPI filter in the HTTP task of a Domino Server)
Each Java API jar and Domino Service Executable are branded with a version number, which in your case does not match because the portlets came with one version of the Java API, and you have installed a non-matching version of the service on the Domino Service side (you probably extracted the executable for the service installation from the "BEA Personal Messaging API 4.3" bundle or installer).
The solution for this is to:
1) uninstall the Domino Service that you have plugged into the domino service
2) extract the Domino Service installer which was included with the portlet bundle. This is located in the "Program Files\compoze\groupware_portlets_bea-2.5\8.1\service\domino" directory if you ran the portlet installer, or in the "groupware_portlets_bea81-noinstall-25\groupware_portlets_bea-2.5\8.1\service\domino" directory if you used the "no-install" zip file.
As a tip, to quickly check whether the versions of the service and Java APIâ€™s that you are using are matching, perform the following steps:
1) hit the domino server with the following URL and notice the "service version": http://domino_service_url:http_port/compoze.czdo. This should be something like "Service Version: 3.6.102"
2)in your portal application (or in the portlet install bundle), open the harmony_portlets.jar file with winzip, then find the "compoze_products_information.properties" file. In this file, notice the "product.domino" version (e.g. product.domino = 3.6.102)
3) the two versions you have inspected must match in order for the connection between the portlet and service to succeed.
If you have verified that the "service" version and "java API" version (located in %portal_app_dir%/APP-INF/lib/harmony_portlets.jar, and you are still getting the exception, it is likely that there is a "harmony_portlets.jar" that included an old version of the Java API located somewhere in the portal server classpath. In this case, make sure that the only harmony_portlets.jar in the classpath is the one that was included with the portlet bundle that you have installed.
Regards,
Lev

Why isn't my browser supported?

One of the challenges of delivering desktop-quality software
inside a browser is, well, the browser itself. For more details on
our approach to browser support, its challenges, etc. please see
the posting on the Acrobat.com blog.
http://blogs.adobe.com/acom
Browsers aren't all the same, and there is a fair amount of
work to get things working right, especially with keyboard
shortcuts and the clipboard. We've focused on the most common
browsers first: Firefox (Mac & Windows), Internet Explorer 6
and 7, and Safari 3.
For example: We’d like to follow convention and provide
the typical Cmd-B shortcut to make text bold. However, Firefox on
the Mac uses Cmd-B to open bookmarks in the sidebar; so Buzzword
was forced to use Ctrl-B for making text bold.
For
Firefox under Linux, we're providing limited support. We
have done some testing and we believe it works well, but we're
interested in your feedback. Please be sure to upgrade to the
latest Linux version of Flash Player 9 available at
http://www.adobe.com/go/getflashplayer,
and also be sure to adjust your preferences as described in the
initial page you'll see when visiting the application in Firefox
under Linux.
Other browsers may work (Opera, Camino, etc.) to some extent,
but we can’t make assurances that all functions will work.
We appreciate hearing from users who want to give Buzzword a
spin under non-supported browsers, as it helps us focus our efforts
and testing.

Hi,
After trying Opera AND Firefox to post a reply to "Why isn't my browser supported?" I'm now using IE (7 not 8 - that's not working, too!). Maybe that's the first thing that should work in all browsers - the forum.
The second thing, and that's why I originally wanted to post something here, is that I had problems typing "&" and "/" in Opera. They don't seem to be at the same key as usual. (I have a german keyboard...):
Shift + ^1234567890ß´
Key (normal): °!“§$%&/()=?`
Key (buzzword): ^!@#$%^&*()ß`
Additionally everything seems a little bit slow...
Regards,
Ireen

Is JavaMail 1.3.3 supported on z/Linux platform

Hi, I would like to know are following libraries supported on z/Linux platform ?
1) JavaMail 1.3.3 and
2) Java Activation Framework 1.0.2
Or can you please send me the known issues, if any ?
Also would appreciate if could send me any info/link for 64 bit JVM support for these.
Thanks a lot in advance / Rajan Kumar

Java is supposed to be Write Once Run Anywhere. So I would assume that ordinary Java code would run on z/Linux, 64-bit or otherwise, until my tests proved otherwise.

Multiple Browser Support in Webcenter

What are the code changes that are to be made to have Multiple browser support in Webcenter?
what is done in Webcenter to provide to browser independent UI
e,g in jsp , we usually write javascript
if browser is this, do this
else do this
kind of logic

Even When I use JSTL and have modified the code to the following
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:c="http://java.sun.com/jsp/jstl/core"
xmlns:fn="http://java.sun.com/jsp/jstl/functions"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1">
<af:form id="f1">
<c:choose>
<c:when test="${fn:containsIgnoreCase(header('User-Agent'), 'MSIE 6.0')}">
<c:out value="Its IE6"/>
</c:when>
<c:otherwise>
<c:out value="Its others"/>
</c:otherwise>
</c:choose>
</af:form>
</af:document>
</f:view>
</jsp:root>
i get error on compile that says
Error(12,16): The function "header" for prefix "" can not be found in the specified tag library.

URGENT: Browser support w/BEA Portal (Platform 7)

Similar Messages

Maybe you are looking for