WDA Component configuration - 'Component-Defined' is not enable?

Hi,
I create a web dynpro abap component and then a component configuration, but is not possible to modify
tab 'Component-Defined'.
Could you please tell me why 'Component-Defined' is not enable?
Thank you.
Best regards.
Al
Edited by: Alberto Baracco on Feb 15, 2011 11:30 AM

Hi,
my WDA implements a POWL application and uses the component POWL_UI_COMP.
I have copied in the context of the custom controller the node CONF_DATA of the custom controller POWL_CONFIG.
Now tab 'Component-Defined' of my component configuration is enabled and it contains the parameters of node CONF_DATA.
Thank you.
Best regards.
Al

Similar Messages

  • WDA application configuration parameter Stylesheet URI not working

    Hi Experts,
      I created an application configuration for a webdynpro ABAP application and populated theme path for parameter Stylesheet URI on application configuration. However when I execute the application using this application configuration, the application does not pick up the theme.
      If I pass the same path using URL parameter SAP-EP-THEMEROOT, it works. Also it works if I maintain it as URL parameter in SPRO
      However for my requirement I need it to work specifically from application / application configuration parameter. Has anyone faced this problem and found a solution?
    Thanks in Advance
    Tanmay

    I believe you need a redirect if you want to change between SSL and non-SSL.
    How about something in the line of (example with code 404):
    <If $code=404 && $security>
      Error fn="redirect" url="http://oursite/error.html"
    </If>.. where +$security+ means SSL.
    About the Error and URI, it seems uri="/error.html" would work, but it will not switch you from SSL to non-SSL.
    I'm curious why you would want to redirect a user to the non-SSL instance in this scenario..

  • JSP : Tiles Error �tag.getAsString� : component context is not defined

    JSP : Tiles Error �tag.getAsString� : component context is not defined
    I�m working with Struts 1.1 and Tiles, under Tomcat 5.0.16
    My application works fine using Struts 1.1 alone, however, when attempting to run the application in a �Tiles� environment, I get an error:
    �
    javax.servlet.jsp.JspException: Error - tag.getAsString : component context is not defined. Check tag syntax
    �
    I have �defined� this in my �tiles-defs.xml� file, and as far as I can tell, everything else is configured properly (I have looked over the included Struts document examples, and others on the web, and I seem to have everything configured identically).
    What am I missing???
    I have created a series of �mostly� empty JSP files, for simplicity sake.
    JSP FILES:
    -     header.jsp
    -     footer.jsp
    -     menu.jsp
    -     rootLayout.jsp
    -     user.jsp
    -     show_user.jsp
    -     error.jsp
    -     defaultContentPage.jsp
    All JSP files contain:
    <%@ taglib uri="/WEB-INF/lib/struts-tiles.tld" prefix="tiles" %>
    and
    �
    <title>
    <tiles:getAsString name="title"/>
    </title>
    �
    My �tiles-defs.xml�: =================================================
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE tiles-definitions PUBLIC
    "-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
    "http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
    <tiles-definitions>
    <!-- ================ RootLayout ======================= -->
    <definition name=".root.layout" path="/jsp/rootLayout.jsp" >
    <put name="title" value="Default title"/>
    <put name="header" value="/jsp/header.jsp"/>
    <put name="menu" value="/jsp/menu.jsp"/>
    <put name="content" value="/jsp/defaultContentPage.jsp"/>
    <put name="footer" value="/jsp/footer.jsp"/>
    </definition>
    <!-- ================ Extentions ======================= -->
    <!-- User -->
    <definition name=".view.user" extends=".root.layout">
    <put name="title" value="Welcome to the User Form."/>
    <put name="content" value="/jsp/user.jsp"/>
    </definition >
    <!-- Save -->
    <definition name=".view.save" extends=".root.layout">
    <put name="title" value="Welcome to the Show User Form."/>
    <put name="content" value="/jsp/show_user.jsp"/>
    </definition >
    <!-- Error -->
    <definition name=".view.error" extends=".root.layout">
    <put name="title" value="Error Message."/>
    <put name="content" value="/jsp/error.jsp"/>
    </definition >
    </tiles-definitions>
    My �struts-config.xml�: ==============================================
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE struts-config PUBLIC
    "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
    "http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
    <struts-config>
    <!-- ========== FormBeans =================================== -->
    <form-beans>
    <form-bean name="userForm" type="biz.seamrog.strutstest.model.state.UserForm"/>
    </form-beans>
    <!-- ========== Action Mapping Definitions=================== -->
    <action-mappings>
    <!-- Action using normal forward syntax...
    <action path="/user"
    forward="/jsp/user.jsp">
    </action>
    -->
    <!-- Action using a "Tiles" forward syntax...
    The "forward" path mappings are defined in a file named
    "../WEB-INF/tiles-defs.xml
    -->
    <action path="/user"
    forward=".view.user">
    </action>
    <!-- Action using normal forward syntax...
    <action path="/save"
    type="biz.seamrog.strutstest.model.logic.SaveAction"
    name="userForm" scope="request"
    input="/jsp/user.jsp">
    <forward name="success" path="/jsp/show_user.jsp"/>
    <forward name="failure" path="/jsp/error.jsp"/>
    </action>
    -->
    <!-- Tiles syntax -->
    <action path="/save"
    type="biz.seamrog.strutstest.model.logic.SaveAction"
    name="userForm" scope="request"
    input="/jsp/user.jsp">
    <forward name="success" path=".view.show_user"/>
    <forward name="failure" path=".view.error"/>
    </action>
    </action-mappings>
    <!-- ============== Global Forwards ======================== -->
    <global-forwards>
    <!-- NOTE: paths with "." syntax are Tiles defined paths,
    all other paths follow conventional "/path/to/file.jsp syntax
    -->
    <forward name="user" path=".view.user"/>
    <forward name="show_user" path=".view.show_user"/>
    <forward name="error" path=".view.error"/>
    <forward name="cssBase" path="/stylesheets/common.css"/>
    </global-forwards>
    <!-- ============= Plug-ins =============== -->
    <!-- Tiles Plug-in -->
    <plug-in className="org.apache.struts.tiles.TilesPlugin" >
    <set-property property="definitions-config" value="/WEB-INF/tiles-defs.xml"/>
    <set-property property="definitions-parser-validate" value="true" />
    <set-property property="moduleAware" value="true" />
    </plug-in>
    </struts-config>
    My �web.xml�: =====================================================
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'>
    <web-app>
    <servlet>
    <!--
    MyController extends org.apache.struts.action.ActionServlet
    NOTE: The servlet could also be specified specifying the
    default Struts ActonServlet...
    <servlet-name>controller</servlet-name>
    <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
    ...I have chosen to extend here just for practice sake.
    -->
    <!--
    <servlet-name>MyController</servlet-name>
    <servlet-class>biz.seamrog.strutstest.controller.MyController</servlet-class>
    -->
    <servlet-name>MyController</servlet-name>
    <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
    <!--
    Point to Struts configuration file(s)
    -->
    <init-param>
    <param-name>config</param-name>
    <param-value>/WEB-INF/struts-config.xml</param-value>
    </init-param>
    <!-- Tiles config -->
    <init-param>
    <param-name>definitions-config</param-name>
    <param-value>/WEB-INF/tiles-defs.xml</param-value>
    </init-param>
    <!-- This is the added Application parameter: -->
    <init-param>
    <param-name>application</param-name>
    <param-value>ApplicationResource</param-value>
    </init-param>
    <!-- end -->
    <load-on-startup>5</load-on-startup>
    </servlet>
    <!--
    All incoming requests that end in .do, send to MyController.
    -->
    <servlet-mapping>
    <servlet-name>MyController</servlet-name>
    <url-pattern>*.do</url-pattern>
    </servlet-mapping>
    <!--
    Send initial requests to the login page for this application
    -->
    <welcome-file-list>
    <welcome-file>/jsp/user.jsp</welcome-file>
    </welcome-file-list>
    <!--
    Make all of the necessary related Struts JSP custom tag libraries
    available and define where to find them.
    -->
    <taglib>
    <taglib-uri>/WEB-INF/lib/struts-bean.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/lib/struts-html.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/struts-html.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/lib/struts-logic.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>/WEB-INF/lib/struts-tiles.tld</taglib-uri>
    <taglib-location>/WEB-INF/lib/struts-tiles.tld</taglib-location>
    </taglib>
    </web-app>
    My �rootLayout.jsp�: ================================================
    <%@page contentType="text/html"%>
    <%@ taglib uri="/WEB-INF/lib/struts-tiles.tld" prefix="tiles" %>
    <html>
    <header>
    <title>
    <tiles:getAsString name="title" />
    </title>
    <body>
    <tiles:get name="header"/>
    <tiles:get name="menu"/> <tiles:get name="content"/>
    <tiles:get name="footer"/>
    </body>
    </html>

    I found an entry in the Mail Archive for Struts. I got it working. My working code is below. You need to in the base JSP import the header and put the 'title' out to it.
    tiles:def file:
    <!DOCTYPE tiles-definitions PUBLIC
    "-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
    "http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
    <tiles-definitions>
    <definition name=".petstore.Base" path="/common/petstorecommon.jsp">
    <put name="title" value ="${title}"/>
    <put name="header" value="/common/header.jsp"/>
    <put name="message" value="/common/message.jsp"/>
    <put name="content" value="${content}"/>
    <put name="navbar" value="/common/navbar.jsp"/>
    </definition>
    <definition name="petstore.Login" extends=".petstore.Base" >
    <put name="title" value="Login Page" />
    <put name="content" value="/Logon.jsp"/>
    <put name="test1" value="test1value"/>
    </definition>
    base tile def:
    <%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles"%>
    <%@ page contentType="text/html;charset=windows-1252"%>
    <html:html>
    <head>
    <html:base/>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
    <title>pet store common (jsp)</title>
    </head>
    <body>
    <tiles:insert attribute="header">
    <%-- both of these attributes are accessible from header.jsp It works!!! --%>
    <tiles:put name="title" beanName="title" beanScope="tile" />
    <tiles:put name="test1" beanName="test1" beanScope="tile" />
    </tiles:insert>
    <%-- <tiles:get name="header" /> --%>
    <tiles:get name="message" />
    <tiles:get name="content" />
    <tiles:get name="navbar" />
    </body>
    </html:html>
    Getting access to the title value in the header.jsp file:
    <%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean"%>
    <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html"%>
    <%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic"%>
    <%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles"%>
    <html>
    <head>
    <tiles:getAsString name="title" />
    <tiles:getAsString name="test1" />
    </head>
    <body>
    </body>
    </html>

  • Opened SE80 & tried creating WDA Component. Layout page not displaying

    Dear All
    I am new to WDA. I would like to create a WDA Component. I opened up SE80, the layout tab doesn't seems to be loading. It shows page cannot be displayed. Kindly let me know what else I need to do.
    I read in help portal, they mentioned to active ICM/ICF I am not sure where to do this. Kindly advice.
    Thanks in advance
    Kind Regards
    Ramamoorthy D

    Kindly go through below link:
    [Web Dynpro ABAP Configuration|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/e86de5008b4d9ae10000000a155369/frameset.htm]
    Also check following things (which are generaly not required in normal enviornment):
    1) Check host file entry with server addres and server name
    goto start-> run-> type 'drivers' ->etc-> open host file in note pad -> make server entry
    2) check proxy settings of browser
    tools->internet options->connections->lan settings-> advanced->exceptions
    Regards,
    Saket

  • WDA Personalization bug when running multiple instances of the same WDA component

    I have found an issue relative to WDA personalization that it seems to be a bug for me.
    Scenario:
    In my scenario, I have a Web Dynpro component A which has two usages of the same Web Dynpro Component B (USAGE1 and USAGE2).There is a WDA application APPL_A defined to fire WDA component A. I have defined a component configuration COMP_CONF1 for WDA component B and an application configuration APP_CONF1 for WDA application APPL_A. This application configuration applies the same component configuration COMP_CONF1 to both usages USAGE1 and USAGE2.
    Runtime behaviour:
    At runtime, I execute application APPL_A using the application configuration APP_CONF1. When I personalize something in the USAGE1 of WDA component B, the effects does not appear in USAGE2 until a page refresh is done. Obviously, as both usages uses the same component configuration at rutime the effects of personalization should be applied to both, but WDA configuration framework fails to apply the changes instantaneously to USAGE2.
    Have you expermiented this behaviour? Is there any workaround for this?

    I have found an issue relative to WDA personalization that it seems to be a bug for me.
    Scenario:
    In my scenario, I have a Web Dynpro component A which has two usages of the same Web Dynpro Component B (USAGE1 and USAGE2).There is a WDA application APPL_A defined to fire WDA component A. I have defined a component configuration COMP_CONF1 for WDA component B and an application configuration APP_CONF1 for WDA application APPL_A. This application configuration applies the same component configuration COMP_CONF1 to both usages USAGE1 and USAGE2.
    Runtime behaviour:
    At runtime, I execute application APPL_A using the application configuration APP_CONF1. When I personalize something in the USAGE1 of WDA component B, the effects does not appear in USAGE2 until a page refresh is done. Obviously, as both usages uses the same component configuration at rutime the effects of personalization should be applied to both, but WDA configuration framework fails to apply the changes instantaneously to USAGE2.
    Have you expermiented this behaviour? Is there any workaround for this?

  • Component-Defined Tab Inactive

    Hi,
    I am new to Floor Plan Manager and creating my first Floor Plan Manager Application. We are on EHP4.
    On Component Configuration Page there are three tabs i.e. Attributes, Component-Defined and WebDynpro Builtin. Problem is that Component-Defined Tab is inactive and I dont know the reason why it is inactive.
    Any idea or am I missing any service activation?
    Thanks,

    I am also facing same problem, could please provide solution, Same solution not working for me.

  • Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

    Hi,
    I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
    compile works fine, but the server deployment throw the following error
    message:
    [java] port component "Hello" is not found in wsdl.
    It's simple JAX-RPC based webservice where a SessionBean method is used as
    the service implementation. The same configuration (webservice.xml,
    mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
    WLS 9.1. Maybe it's a simple configuration error and someone can help.
    Regards
    Guido
    Appendix
    webservice.xml
    <webservices xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
    version="1.1">
    <webservice-description>
    <webservice-description-name>HelloService</webservice-description-name>
    <wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
    <jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
    <port-component>
    <port-component-name>Hello</port-component-name>
    <wsdl-port>HelloPort</wsdl-port>
    <service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
    t-interface>
    <service-impl-bean>
    <ejb-link>HelloBean</ejb-link>
    </service-impl-bean>
    </port-component>
    </webservice-description>
    </webservices>
    mapping.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>com.jcoffee.components.ws</package-type>
    <namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>com.jcoffee.components.ws</package-type>
    <namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
    </package-mapping>
    <service-interface-mapping>
    <service-interface>com.jcoffee.components.ws.HelloService</service-interface
    >
    <wsdl-service-name
    xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
    wsdl-service-name>
    <port-mapping>
    <port-name>HelloPort</port-name>
    <java-port-name>HelloPort</java-port-name>
    </port-mapping>
    </service-interface-mapping>
    <service-endpoint-interface-mapping>
    <service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
    t-interface>
    <wsdl-port-type
    xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
    port-type>
    <wsdl-binding
    xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
    wsdl-binding>
    <service-endpoint-method-mapping>
    <java-method-name>hello</java-method-name>
    <wsdl-operation>hello</wsdl-operation>
    <method-param-parts-mapping>
    <param-position>0</param-position>
    <param-type>java.lang.String</param-type>
    <wsdl-message-mapping>
    <wsdl-message
    xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
    sdl-message>
    <wsdl-message-part-name>String_1</wsdl-message-part-name>
    <parameter-mode>IN</parameter-mode>
    </wsdl-message-mapping>
    </method-param-parts-mapping>
    <wsdl-return-value-mapping>
    <method-return-value>java.lang.String</method-return-value>
    <wsdl-message
    xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
    ponse</wsdl-message>
    <wsdl-message-part-name>result</wsdl-message-part-name>
    </wsdl-return-value-mapping>
    </service-endpoint-method-mapping>
    </service-endpoint-interface-mapping>
    </java-wsdl-mapping>
    HelloService.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="HelloService"
    targetNamespace="http://ws.components.jcoffee.com/"
    xmlns:tns="http://ws.components.jcoffee.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types/>
    <message name="Hello_hello">
    <part name="String_1" type="xsd:string"/>
    </message>
    <message name="Hello_helloResponse">
    <part name="result" type="xsd:string"/>
    </message>
    <portType name="Hello">
    <operation name="hello" parameterOrder="String_1">
    <input message="tns:Hello_hello"/>
    <output message="tns:Hello_helloResponse"/>
    </operation>
    </portType>
    <binding name="HelloBinding" type="tns:Hello">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <operation name="hello">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
    </input>
    <output>
    <soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
    </output>
    </operation>
    </binding>
    <service name="HelloService">
    <port name="HelloPort" binding="tns:HelloBinding">
    <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
    </port>
    </service>
    </definitions>
    and last but not least the ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
    <display-name>JCoffee web service sample</display-name>
    <enterprise-beans>
    <session>
    <ejb-name>HelloBean</ejb-name>
    <service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
    <ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <method-permission>
    <unchecked/>
    <method>
    <ejb-name>HelloBean</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    <container-transaction>
    <method>
    <ejb-name>HelloBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>

    Hi again,
    I got it - i've forgot the namespace prefix for the wsdl-port.
    Now it works.
    Thanks!
    "Ben" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]...
    Hi,
    I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
    compile works fine, but the server deployment throw the following error
    message:
    [java] port component "Hello" is not found in wsdl.
    It's simple JAX-RPC based webservice where a SessionBean method is used as
    the service implementation. The same configuration (webservice.xml,
    mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
    WLS 9.1. Maybe it's a simple configuration error and someone can help.
    Regards
    Guido
    Appendix
    webservice.xml
    <webservices xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
    version="1.1">
    <webservice-description>
    <webservice-description-name>HelloService</webservice-description-name>
    <wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
    <jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
    <port-component>
    <port-component-name>Hello</port-component-name>
    <wsdl-port>HelloPort</wsdl-port>
    <service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
    t-interface>
    <service-impl-bean>
    <ejb-link>HelloBean</ejb-link>
    </service-impl-bean>
    </port-component>
    </webservice-description>
    </webservices>
    mapping.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>com.jcoffee.components.ws</package-type>
    <namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>com.jcoffee.components.ws</package-type>
    <namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
    </package-mapping>
    <service-interface-mapping>
    <service-interface>com.jcoffee.components.ws.HelloService</service-interface
    >>
    <wsdl-service-name
    xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
    wsdl-service-name>
    <port-mapping>
    <port-name>HelloPort</port-name>
    <java-port-name>HelloPort</java-port-name>
    </port-mapping>
    </service-interface-mapping>
    <service-endpoint-interface-mapping>
    <service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
    t-interface>
    <wsdl-port-type
    xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
    port-type>
    <wsdl-binding
    xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
    wsdl-binding>
    <service-endpoint-method-mapping>
    <java-method-name>hello</java-method-name>
    <wsdl-operation>hello</wsdl-operation>
    <method-param-parts-mapping>
    <param-position>0</param-position>
    <param-type>java.lang.String</param-type>
    <wsdl-message-mapping>
    <wsdl-message
    xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
    sdl-message>
    <wsdl-message-part-name>String_1</wsdl-message-part-name>
    <parameter-mode>IN</parameter-mode>
    </wsdl-message-mapping>
    </method-param-parts-mapping>
    <wsdl-return-value-mapping>
    <method-return-value>java.lang.String</method-return-value>
    <wsdl-message
    xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
    ponse</wsdl-message>
    <wsdl-message-part-name>result</wsdl-message-part-name>
    </wsdl-return-value-mapping>
    </service-endpoint-method-mapping>
    </service-endpoint-interface-mapping>
    </java-wsdl-mapping>
    HelloService.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="HelloService"
    targetNamespace="http://ws.components.jcoffee.com/"
    xmlns:tns="http://ws.components.jcoffee.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types/>
    <message name="Hello_hello">
    <part name="String_1" type="xsd:string"/>
    </message>
    <message name="Hello_helloResponse">
    <part name="result" type="xsd:string"/>
    </message>
    <portType name="Hello">
    <operation name="hello" parameterOrder="String_1">
    <input message="tns:Hello_hello"/>
    <output message="tns:Hello_helloResponse"/>
    </operation>
    </portType>
    <binding name="HelloBinding" type="tns:Hello">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="rpc"/>
    >
    >
    <operation name="hello">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
    </input>
    <output>
    <soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
    </output>
    </operation>
    </binding>
    <service name="HelloService">
    <port name="HelloPort" binding="tns:HelloBinding">
    <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
    </port>
    </service>
    </definitions>
    and last but not least the ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
    <display-name>JCoffee web service sample</display-name>
    <enterprise-beans>
    <session>
    <ejb-name>HelloBean</ejb-name>
    <service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
    <ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <method-permission>
    <unchecked/>
    <method>
    <ejb-name>HelloBean</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    <container-transaction>
    <method>
    <ejb-name>HelloBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>

  • While Creating PM order If component stock is not available shld thr error

    Dear All,
    At the time of PM order creation, If assign component stock is not available system should through error and order shold not save
    Regards
    Honyal

    Hi Mr Honyal,
    This is not possible in Standard.
    You need to configure it throught user exit.
    You can use user exit - CNEX0009.
    The exit is called from PS, PM, PP, so while coding please use a specific transaction code like IW31, IW32 etc.
    The exit is called material by material. So if you have entered 5 material in components screen,
    the exit will be called 5 times.
    At run time you need to check the availabel stock of that material and give error if the stock doesnt exist.
    Take help from your ABAPer & MM consultant for coding and finding tables of stock.
    Thanks & Regards,
    Mihir

  • Component is missing, not registered, not upgradeable

    Hi,
    I got the error:
    "Error: 0xC0048021 at Data Flow Task, OLE DB Source [1]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "OLE DB Source;Microsoft Corporation; Microsoft SqlServer
    v10; (C) Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;7"."
    This apears in any destination or source connection

    Hi Douglas,
    Based on the current information, the issue occurs because there are only 32-bit relevant OLEDB drivers installed on the current computer, so you need to configure the SSIS project to run in 32-bit runtime mode. Regarding the issue that you don’t need
    to change this property on the other servers, there can be two reasons:
    The existing SSIS project on another server is already configured to run in 32-bit mode.
    There are 64-bit relevant OLEDB Drivers installed on other servers, hence, the package can run in 64-bit runtime mode properly.
    Regards,
    Mike Yin
    TechNet Community Support

  • The Service Component Container is not running" eventhough they are running

    Hi,
    We are on 12.0.4 with hardware load balancer(cisco), and pcp has been configured between two Application nodes. The database is in the seperate node with OS Cluster.
    I wanted to configure Workflow notification mailer. For that i have logedin through OAM workflow-->It is showing as
    Nitification mailer -unavailable
    Agent listener --     Down
    Service component --     Down
    Background Engine --     Down
    Purge --           UP
    Control queue cleanup -     Down
    I have Navigate to Service component screen,
    There all the Automatic component are showing status as stopped with error, I clicked the "workflow agent listener service" of container all the services are up and "state" is showing as "activated" Node it is showing as "Primary node of PCP"
    But when you click on any "stopped with error" service to start, It is throughing " The Service Component Container is not running" when i click on "view log" it is not showing any message seems like hanging.
    Before starting the Notification mailer configuration i wanted to rectify the above issue.
    Can you pl help us out in rectify the same.
    Thanks and Regards
    Vasu

    Check the log file from the server itself; it should be under ($APPLCSF/$APPLLOG/FNDCPGSC*.txt).

  • The Service Component Container is not running

    Hi All
    When I tried to start any of the services in the services components in the
    OAM , I got the error 'The Service Component Container is not running'
    I already did the required configuration steps required to integrate the
    workflow mailer with Email
    I am on WF.G
    The error in the view_log is : FND_WEBFILE.GET_URL (CPID=0)
    Any idea?
    Thanks in advance

    Have you verified that the concurrent manager Workflow Mailer Service is running. You can check this from the System Administrator -> Concurrent -> Manager -> Administer. You will have to make sure the Workflow Agent Listener Service is also running.
    Then start the mailer and agent listener components.
    If you still have trouble starting them up, following are the things to check out.
    1. check out if the Concurrent Manager env set up is correct. $APPL_TOP/admin/adovars.env is the file that contains env variables such as AF_CLASSPATH. This needs to point to right Java libraries that contains aqapi, jmscommon etc.
    2. The concurrent manager log files are written to $APPLCSF/$APPLLOG directory on the concurrent tier. The Service Component Container log files are named as FNDCPGSC9999.txt where the numeric part if the PID.
    3. Please refer to metalink note 242941.1 for more information on setting up and troubleshooting the mailer.
    Hope this helps.
    Vijay

  • ERROR: The Service Component Container is not running: Standalone Workflow

    We're trying to get the java notification mailer established through the OEM 10g Application Server Control. But the mail agent listener servlet container (WFALSNRSVC), and the mailer service servlet container (WFMLRSVC) are not running. Because of that, I cannot get any other parts of the mail configuration running. Note, I can successfully complete getting through the 8 steps of the "Workflow Notification Mailer" configuration (e.g. IMAP and SMTP mail accounts work fine and are accessible from the Workflow application server). What's the trick to getting the servlet containers running?? All I find in Oracle documentation is that these must be running before you can do anything, but I don't find anything on troubleshooting when they are not running.
    Thanks.

    Hi,
    I'm having the same problem as you did.
    I've tried pushing the button Go in the Oracle Workflow Manager - Service Components.
    And it showed
    An error has occurred!
    The Service Component Container is not running.
    Should I uninstall my Oracle Workflow?
    And install a new installation of Oracle Workflow?
    What does it mean by the "wfinstall"?
    Is it the Oracle Workflow Configuration Assistant? which I can access using the wfinstall.bat.
    Or should I replay the Oracle Workflow Configuration Assistant (wfinstall.bat) and choose Upgrade option?
    Or should I uninstall all of my Oracle installation and start installing from the beginning?
    BTW, what if I don't use (or have) OID?
    Is it required?
    Any clue would be grateful.
    Thanks.
    Buntoro

  • Problem in ECM involving HRECM00_PLANNING_OVERVIEW(standard WDA component)

    Hi Guys,
    I am currently working in HR module(ESS/MSS).Here we will have to use the standard WDA component HRECM00_PLANNING_OVERVIEW to implement the budget approver application.
    If you launch it in portal and select a budget owner that gets populated in the first screen and click on "Review Details" button it basically calls a java web dynpro application which shows all the employess under that particular budget approver.
    If you open  HRECM00_PLANNING_OVERVIEW in se80,and goto the method "onactionopen_planning"(method which gets fired when "Review Details"  button is clicked) you will see the last stament as-
    ELSE.
              wd_this->launch_planning_ui( ).
            ENDIF.
    Double click and go inside  aunch_planning_ui().
    method LAUNCH_PLANNING_UI .
      DATA fpm                  TYPE REF TO if_fpm.
      DATA navigation           TYPE REF TO if_fpm_navigation.
      DATA key                  TYPE fpm_s_navigation_key.
      DATA target_key           TYPE string.
      fpm = cl_fpm_factory=>get_instance( ).
      " Store table of pernrs in memory so that comp planning UI can read it
      wd_assist->write_memory_for_planning(
        EXPORTING
          crevi               = wd_this->selected_crevi
          planning_pernr_tab  = wd_this->planning_objec_tab ).
      " Navigate to Compensation Planning iView
      key-key1 = 'HRECM'.
      key-key2 = 'HRECM_LAUNCH_PLANNING'.
      navigation = fpm->get_navigation( is_key = key ).
      target_key = navigation->get_key_from_alias( iv_alias = 'ECM_WDJ_LAUNCH' ).
      navigation->navigate( iv_target_key = target_key ).
    endmethod.
    This is the standard code for the method.
    navigation = fpm->get_navigation( is_key = key ). In this line its callin get_navigation and getting all the navigation parameters for the java wd application i beleive. If you go inside method get_navigation you will find in the last line its assigning
      APPEND ro_navigation TO mt_navigation.
    in mt_navigation if you go deep inside the class attributes at debug mode and see the attibute mt_target you will get an attribute application_params inside which the portal path(in bold) is getting fetched.
    application_params
    LINK_TEXT |Review Details                                                 |
    OBLIGATORY|X                                                                  |
    APPLICATIO<POP                                                               |
    APPLICATIO<ECM_WDJ_LAUNCH                                                 |
    PATH_TO_PA<ROLES://portal_content/com.sap.pct/line_manager/com.sap.pct.erp<
    Parameter_<                                                               |
    disabled  |                                                               |
    invisible | 
    I want to know from where it is getting the portal path(path_to_pa)?Because i have to change the portal path for my use.
    Please help experts.
    Thank,
    Saikat.

    Oops....forgot to close the thread.
    solved this a long time back.It can be configured by the transaction lpd_cust.
    thnx,
    saikat.

  • WDA Component Theme Change

    Dear All,
    I want to Change theme of WDA Component. Using parameter WDTHEMEROOT i m passing new theme but its not working.
    So i have tried to pass the theme programmatically using SAP-CSSURL. It is taking the theme but the theme layout is not displayed, like backgroud color or any color its not appearing on page.
    Your reply will be appriciated.
    Regards,
    KK

    Hi All,
    I am going through similar issue, We have a URL LInk in WebDynPro ABAP application. we wanted the Link color to be Pink similar to portal theme color for links in portal.
    I got this to work by setting WDFORCEEXTERNALSTYLESHEET = 'X' & disabling LightSpeed with WDLIGHTSPEED = ' ' / blank.
    So, we got the Pink color link in WD app now. but The RoadMap UI element we had in WebDynPro component is not getting generated.
    We tried to get URL color in WD abap from portal with just WDFORCEEXTERNALSTYLESHEET = 'X. then UI elements like RoadMap & Tables are all not getting populated properly. By disabling LightSpeed, everything is coming fine except RoadMap...
    Any ideas here ?
    Thanks,
    Phani

  • Component on page not moving as vertical scroll bar is moved

    All -
    I have a mxml page that is a mx:Application.  This page basically consists of a VBox
    and a number of components included within that VBox.  All but 1 of the components
    within this VBox are built-in flex components.  The one component that is not a built-in
    flex component is the one that is causing me issues.  The issue is happening when I run
    the application, once running the vertical scroll bar appears on the right-hand side of the
    page (as expected because I have quite a few items in my VBox).  The problem is that as
    I drag the vertical scroll bar from the top of the page to the bottom of the page, the custom
    component within my VBox that I built is staying put (it's not moving with respect of the
    movement of the vertical scroll bar).  All of the built-in flex components that are within my
    VBox are moving with respect of the movemnet of the vertical scroll bar as expected.
    I appreciate any information that you can provide that will lead me in the right direction,
    Thank you,
    Wes

    // THIS IS THE CUSTOM COMPONENT

Maybe you are looking for