JCo Destination options Disabled

Dear All,
                  I have Created a Webdynpro Appln. When i run it it shows that
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_DEBIT_METATA' in the SLD. No such JCO destination is defined in the SLD.
                   Now when i go to Webdynpro Administrator it shows this JCo Destination Disable.
                   Should i create a JCo destination of this name. Even i am getting only Check SLD Configuration Option enable and other like Create, Maintain JCo Destination etc Disabled. What to do now?
Regards,
Vinayak

Hi Vinayak,
You need to do the following:-
1. Open Visual Admin
2. Navigate to serverservicesSLD data suplier
3. enter the user credentials in http setting and CIM settings.
4. Save and do a client test
assign urself to SAP_SLD_admin group , you will not see the tab disabled , for a good overview of SLD refer to the following guide.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55414
Regards
Pankaj Prasoon

Similar Messages

Create JCO destination option not available

Dear All,
I am trying to make a JCO connection in CE.
However the buttons for
"Create JCo Destination","Maintain JCo Destinations" are disabled.
The status for built-in JCO destinations WD_MODELDATA_DEST
WD_RFC_METADATA_DEST is shown as unknown.
The "Enable" button is also disabled.
Also i am getting the error "Connection to System Landscape Directory (SLD) could not be opened successfully".
Can anyone please help me in this.
Thanks and regards,
Mayuresh.

Hi Mayuresh,
In nwa go to Configuration Management->Infrastructure->SLD Data Supplier Connection->Destinations.
Create a Destination.
Ping the destination to check if it is successful.
After that you can create a JCO Connection.
Regards
pankaj

Maintain JCO destination button is disabled

I am getting the following error when trying to log in to MSS:
"com.sap.tc.webdynpro.services.exceptions.WDRuntimeE xception: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD."
When going to Content Administration->WebDynpro Content->Maintain JCO destinations, the button "Maintain JCO destinations" is disabled. I am logged in as an adminsitrator.
Can someone help?
Tiberiu

I tried from Visual Administrator->SLD Data Supplier to trigger SLD data supply. I get the following error: "Failed to send HTTP data:401. Unauthorized".
I also checked the SLD logs and I found this:
"#14 08/28/2008 08:11:37.910 [SAPEngine_Application_Thread[impl:3]_35] WARNING com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for WBEM client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly. "
Is it possible the SLDSUSER password expired somehow?
Tiberiu

In portal where we will create JCO destinations?

HI Gurus,
In portal where we will get the option or screen for creating JCO destinations....
I guess its somemwhere in System Admin---->
If anybody knows the path please share with me.......
Thanks in Advance,
Dharani

Hi,
Please check the below document for help
configure ESS:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
ESS/MSS Installation to R/3 4.7 Enterprise
http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
MSS - http://help.sap.com/saphelp_erp2004/helpdata/en/0a/8b3b40b1607a56e10000000a1550b0/frameset.htm
help.sap.com - Configuration of Employee Self-Service (ESS)
http://help.sap.com/saphelp_erp2005/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
help.sap.com - Technical Description and Configuration Information
http://help.sap.com/saphelp_erp2005/helpdata/en/76/77594d165144a1a9bff9aae1e26b26/frameset.htm
BP for ESS Document
https://www2.iviewstudio.com/support_content/_17295/BP_ESS_05_P1.pdf
General Settings for Self-Service Applications
Configuring MSS on Portal 6.0
Implementation and Configuration guide for ESS into Portal,Backend R/3 4.7C
Thanks & regards
Santosh
Reward if helpful !!!

Problem in connecting JCO destination in web dynpro

HI all,
I was installed sneak preview of Net weaver 6.4,
I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
for the above requirement what I did was
(1)I created SLD setting.
(a)Web as Java (I am not having any problem to
Create this.
(b) Web as ABAP.
When i am trying to create
This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
(a)Host: pava-vis75
(b) Port: 50000
(c) user: administrator
(d) password: abcd1234
RFC Settings, I mentioned as
(a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
(b)Gateway Service/Host: sapgw00
CIM Client Generation settings, as
(a)Host: pava-vis75
(b)Port (http/https):50000
(c) user: administrator
(d) Password : abcd1234
I tested the CIMClient Test by click the the button. I got the successful message.
Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
(a)Alias: vissldtest
(b)Host Name: pava-vis75
(c)Port: 50000
(d) user: administrator
(e) password: abcd1234
Then saved it.
Next I created sapmsUV0 3600/tcp entry at
WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
I restarted the system, as well as server.
Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as create JCO Destination Deployed Contentlocal-local/CompanyCodeGetList-Applications CompanyCodeGetList
I Choosed the JCO Connections tab- there are 2 entries those are
(1) COMPANY_CODE_MODEL
(2) COMPANY_CODE_RFC_METADATA
So I started creating connection for COMPANY_CODE_RFC_METADATA.
First one is
General data Name : COMPANY_CODE_RFC_METADATA
Client : 100
I didnt changed any default JCo pool configuration.
J2EE Cluster
There is a check box called Use Local J2EE engine J2E on pava-vis75 so I choosed that.
Connection Type
Dictionary Meta Data and application Data
I choosed the first one.
Then
Msg. Server Connection
Security
After these, I tried to test the connection by clicking the Test Connection.
It is saying the error as
First time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
second time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Can any body please help me to solve this problem.
From past 1 week on wards I have been trying to resolve this. But in vain.

It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
Regards,
Eduardo.
Message was edited by: Jesus Cil

Using X509 certificates to create a client in a JCo destination / pool

Hi,
Our administrators have set up JCo destinations for us developers to use in connecting to the SAP R/3 back-end. We need to use X509 certificates instead of username/password to create a connection. How is this done? The JCo API doesn't seem to list any class/method combination that is suitable.
JCO.createClient allows me to pass an X509 certificate, but it doesn't allow me to specify what JCO.Pool (i.e., JCo destination) to use.
JCO.addClientPool seems to allow both, but I don't think I want to really "add" a pool-- don't I just want to "use" a pre-existing pool, i.e., one of the JCo destinations our administrator has set up?
Do I need to create a Client using the X509 certificate and somehow add this Client to the JCO.Pool? I thought JCo destinations were meant to be pre-established Client pools waiting for a Client to be plucked out of it and used. Is that wrong? What am I missing?
Thanks in advance for your responses.

Hi,
I'm note sure whether you can use prepared JCo destinations in this case. However, if it's possible to use single JCo clients you instantiate when you need them, you have different options depending on whether you have an Enterprise Portal installed on top of your J2EE Engine or not.
--> Without Portal
Retrieve the user's current certificate from UME using:
[code]com.sap.security.api.IUser currentUser = ...;
java.security.cert.X509Certificate[] certificates = currentUser.getUserAccounts()[0].getCertificates();
byte[] certBytes = certs[0].getEncoded();
String encodedCert = someBase64Method(certBytes);
Properties jcoProperties = new Properties();
// Add your backend properties like hostname and so on...
jcoProperties.setProperty("jco.client.user", "$X509CERT$");
jcoProperties.setProperty("jco.client.passwd", x509Cert);
JCO.Client jcoClient = JCO.createClient(jcoProperties);[/code]
--> With Portal installed
In general: Define your backend system in the Portal's system landscape instead of as JCo destination. Configure it's logonmethod for X.509 certificates. Either use UME's user mapping feature directly via com.sap.security.api.UMFactory.getUserMapping()... to add the certificate properties to the JCO properties, or use some intermediate API, some of which are available in the portal, some of which reside in the J2EE Engine (details if you request them).
Best regards
Heiko

Machines with same Hostnames overwrite WebDynpro JCo Destinations (SLD)

Hello,
we are working with NWDI and virtualized Developer Workplace Machines (on VMWare Images). By this, all Developer Workplace machines have the same hostname. This works fine until teams start developing with Webdynpro JCo Destinations (i.e. for Adaptive RFC).
This is what I think what I figured out what is going on:
- Webdynpro JCo Destinations are managed on the configured SLD (in our case the NWDI SLD)
- SLD identifies the JCo Destination by hostname and destination name
- JCo Destinations are communicated from host to SLD, even though the SLD Data Supplier is configured only for reading SLD content
In our environment with all developer workplaces having the same hostname, we have the effect, that all devlopers workplaces MUST work with the same JCo Destination. Each time a developer updates the destination for his workplace, this update is written to SLD and therefore the destination of all other workplaces is changed as well.
So my question is: Is there any option to stop developer workplaces writing their JCo Destinations to the central SLD without loosing the functionality to read other CIM Data from their (Name Reservation, Tehcnical System Landscape) ?
We are operating Developer Workplaces on following Releases: 6.40 SP15, 6.40 SP17, 7.00 SP12 and 7.10 SP5.
Any help appreciated,
Stefan

Hi Stefan
As of now we are using Content Administrator to manage and maintaing the JCO destinations to the systems which are configured in SLD.
If you eliminate this jco destinations or if you want to decide not to use these JCOs ,You have option with JCO API.
Manually you need to code in your programs to connect any R/3 System.As there is no option to maintain JCO destinations other than Content Admin with SLD configured with land scape.
Regards
Kalyan

User Mapping in JCO Destination

Hi All,
My current configuration is as follows:
EP6 SP17 -> User mapped through Portal to R3 system.
JCO Destinations -> I use a one technical user for all the WAS users ('user/password' option)
I want that the JCO will use the same mapping as the Portal.
Is it possible?
Is there a guide/tutorial for configuring the User Mapping option for a JCO destionation?
p.s
i cannot use SAPLOGONTICKET because the WAS (Portal) user and the R3 user are different.
Thanks,
Omri

Hi Omri,
I don`t think the Portal user mapping could be utilized by JCo destination on WAS in a trivial way.
You can try to read such data using Portal service in your WD application and afterward pass JCo connection to RFC model but may be it is not so good idea.
Another option is to move user mapping logic to R/3 ( don`t ask how it is just guess ).
Also there is no user mapping on the WAS regarding JCo destination (at least I have never heard about it).
Best regards, Maksim Rashchynski.

Lost JCo destination

Hi all,
I am trying to create a JCo destinations in Web Dynpro Content Administrator (EP 7.0) for my Web Dynpro Java application. I was able to create a JCo destination and I saw the message stating that it was created succesfully. However the status icon for that JCo destination is still red and I have only "Create" link available for it (other links are disabled). When I try to create the same destination again, I get this error:
Exception while creating JCo client connection Failed to create new JCO client connection WD_COOKBOOK_MODELDATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Connection WD_COOKBOOK_MODELDATA_DEST already exists in the SLD. Please choose another name. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:505) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:299) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:342) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Please, did anyone of you encounter such a problem? Is there any other place (except for the Web Dynpro Content Administrator) where I can check or manage created JCo destinations?
Best regards,
Tomas Hansut

did you try with j2ee_admin login?. This can eleminate if there are any authorization issues. Try it

Failed to resolve JCO destination name 'WD_SO_INTERNAL_RFC_METADATA_DEST' i

Hi All,
In the webdynpro content administrator.
All the 'create ,the other links like 'test', 'preview','edit','ping','remove' are all disabled.
when i am trying to access the webdynpro application i am getting the following error. can any body tell me what is the reason behind this.
For your reference, i have uploaded the screen shot of the webydnproContentAdministator , please look in to the wiki in the following path
My Home > Web Dynpro Java > Main > Attachments
comments : Webdynpro content administrator sceen shot
Thanks,
vijay
Failed to resolve JCO destination name 'WD_SO_INTERNAL_RFC_METADATA_DEST' i
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:467)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
    ... 65 more

Vishal,
Yes, tha't's it. The SLD isn't configurated. You have to configurate the SLD before to use JCO Destinations.
Have a look at this forum thread: Configure SLD for Web Dynpro

JCO destination created but NOT showing up in SLD.

We have a portal with a centralized SLD which is tested successfully.
We created a JCO destination on the portal successfully.
However,
1) we cannot test the new jco , all buttons are disabled except the "create" button;
2) if we click above "create" button, we end up with "Jco already exist, cannot create";
3) we go to the centralized SLD, see no jco destination there for this portal.
Very strange. Please help. Thanks!

Which user id are you using to login? Please check the authorization of the user.

JCO Destinations Not Maintainable from Web Dynpro Content Administrator

I have Netweaver Preview 04s installed. Both SLD and app server are running on the same local machine.
1) I have tested connection to SLD from WD Content Admin OK Message.
2) I have created the two destinations using WD Content admin with
    sucess message that it was created in SLD, but the destinations do not
    appear under maintain JCO Destinations of WD Content Admin after creation.
3) The JCO Destinations are not found in SLD when the wd app is deployed.
4) The JCO Destinations are found under the deployed components within WD
    Content admin but listed as Status Not defined. The create link is enabled but
    trying to re-create the items leads to error that they are already defined in SLD.
5) I have added SLD admin privileges to the Administrator user.
6) The Test, Ping etc are disabled greyed-out on the two destinations. Only create
    is enabled but this leads to the error message that it has already been defined
    in SLD.
7) I have clicked on start assigned SLD and checked status is running.
I don't know how the WD Content Admin can detect the destinations have already been created and yet the destinations do not appear under the Maintain JCO destinations column, nor is it possible to test etc.   I should note that Netweaver Admin indicates that SLD is not accessible. As I indicated, I did check that connection worked from WD Content Admin.

John,
If you have more than one user Id's to login in to the Portal,then try to login with Super Admin role and then check the JCo connections there.
Search for the JCo connections you have created and test them.
Also have you given J2EE host name and SAP logon information correctly or not, do check them once.
regards
Anil Dichpally

Destination DLL disabled. []: [CrystalEnterprise.Smtp]

Hi,
When I am trying to schedule a report in infoview, the status shows failed and displays this error :
destination DLL disabled. []: [CrystalEnterprise.Smtp]
i have changed the destination settings and added to and from in it and the metrics option says
true for SMTP Email destination default setting valid is true..
could you please help me out...
Thanks in advance
DV

Hi Toor,
Please go through by below link..
How to do Scheduling Crystal Reports?
Antony
Follow these steps.
There are two ways to configure EMail destination settings:
    1.1 Default settings can be configured on destination tab of specific job server.
    1.2 Report specific settings can be configured to change default settings while scheduling the report.
To enable the Email settings in the job server, navigate to:
    Home >> Servers >> ReportSpeficJobServer
and Enable the "Email (SMTP)" option in the Destination Name list.
Then click on "Email (SMTP)" link to set the following options:
    3.1 Domain name (Mandatory).
    3.2 Server Name (Mandatory).
    3.3 SMTP Port (Mandatory).
    3.4 Authentication details if required (Optional).
    3.5 Email settings for From / To / Cc (This can be configured while scheduling the report as well).
    3.6 Subject / Message / Placeholders are optional.
    3.7 Checkbox "Attach report instance to the email message" can be uncheck if it is required to send only the confirmation of Successful instances.
    3.8 If checked, File Name settings can be configured (Optional).
Click on update to save the settings.
Make sure SMTP port is opened .SMTP Default port is 25.
Thanks,
Amit

R/3 Accessibility via JCo Destination

Hello
We have a WebDynpro application running in an SAP EP 7.0 SP15.
We have metadata and modeldata JCo destinations defined for an R/3 backend system.
The WebDynpro application is using the modeldata JCo destination to reach a BAPI in the R/3 backend system.
As far as SSO access is configured for the modeldata JCo destination, it is required that the Portal user of the WebDynpro applications has an user defined in the R/3 system.
We would need to find some solution so that the WebDynpro application can access the BAPI in spite the runtime Portal user does not exist in R/3 backend system (e.g. accessing R/3 system with another user, that could be hardcoded or mapped to the Portal user or whatever).
Is that possible? If yes, how?
Thanks a lot!
Regards,
Jon

I think that perhaps you posted this question in the wrong Web Dynpro forum. This question appears to be Web Dynpro Java related and not Web Dynpro ABAP. Please confirm otherwise I will be moving this thread to the WDJ forum where it seems to belong.

Is there an issue with Safari in Iphones and Ipads where it does not recognize option disabled="disabled" tag properly?

Greetings everybody,
I have run into a peculiar problem with the Safari browser on mobile platforms (IPad, IPod, IPhone) which I hope I can find a solution for in this community.
I just launched a new website where I sell products with certain variations, for example please view this link: http://www.finerribbon.com/aegean-single-face-satin-ribbon.html
On this particular product, the product variants are supposed to work in such a way where:
If you select the value "1/8" from the "Choose Ribbon Width" field
THEN
The only options active and available to choose from in the "Choose Roll Size" field should be: 500 Yds, 20 Yds & Sample Swatch
Now, if we browse to the above link in Safari using a desktop or a laptop, there are no problems at all, but if we browse to the above link using an IPhone or an Ipad, then we have a problem where all the options are available regardless of the values chosen, basically the above functonality does not work.
I was told that there an issue with Safari in Iphones and Ipads where it does not recognize option disabled="disabled" tag properly, is this true? Can anyone advise me if there is a solution to this problem? I would sincerely apperciate it.
Thank you very much for your time and help!

Hi...
I have run into a peculiar problem with the Safari browser on mobile platforms (IPad, IPod, IPhone) which I hope I can find a solution for in this community.
Now, if we browse to the above link in Safari using a desktop or a laptop, there are no problems at all, but if we browse to the above link using an IPhone or an Ipad, then we have a problem
At the top of this window you'll see the following:
Apple Support Communities > Mac OS & System Software > Safari > Discussions
This the Safari forum for the Mac OS X.
Better that you post your topic here > Developer Forums: Apple Support Communities
I do see on my iPad what you are rreferring to. But you shoudl get the feedback you need in the developer forum.

JCo Destination options Disabled

Similar Messages

Maybe you are looking for