Change plug to interface controller in Netweaver 7.1

hi ,
We are moving to Netweaver 7.1 . Current my webdynpro application is hvng plug firing through interface controller . I hv read tht in 7.1 interface controller is abstract so tht we cnt fire plug from interface controller. I want to know how my my application ging to work in 7.1 Also where i need to make changes in case of firing plug in interface controller. Please also send me links on this topic.Thnx in advance.

HI Kavita,
There is no problem for fire plugs .in you application. As 7.1 supports backward compatibility.
If you want to migrate your application then you need to take care whatever coding you have done in interface controller.
and as plugs are defined in interface view controller. when migrating it will be converted according to new 7.1 structure.
please refer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40af00ad-8080-2a10-88b5-cc4cec99d8ac

Similar Messages

How to create a method in Interface Controller

Hi Guys,
        I am working with webdynpro ABAP sample application "Component usage" . There i got a issue like i am not able to create a method in Interface controller. There i am not able to edit anything. Can anybody please let me know how to do that.
            Thanks In Advance
Regards
Ravikumar

Hi Ravi,
          Check This
If one Web Dynpro component (parent component) needs access to another Web
Dynpro component (child component) the parent component can declare the use
of the child component. A specific component usage instance is then created and
the parent component accesses the functionality of the child component via its
component interface controller.
The only parts of a Web Dynpro component that are visible to the user, are the
interface controller and the interface view(s).
All Web Dynpro components have only one interface controller. Via the
interface controller, data, methods, and event handlers can be exposed to
other components.
Interface views represent the visual interface of a Web Dynpro component.
There is a one-to-one relationship between a Window and an interface view.
Each time a window is defined, a related interface view is automatically
generated, which makes the window accessible from outside the component.
The interface view only exposes those inbound and outbound plugs to the
component user that have the interface property checked. Methods and
context data of the window are not accessible via the related interface view.
If the component has no views, there is no need to have Windows. In this
case, the component will not implement an interface view. Such components
having no visual interface are known as faceless components.
Regards
Sarath

IN Compsition Environment: interface controller in web dynpro

Hi All,
I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
Any clues on this?
Regards
Satish.

Hi All,
I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
Any clues on this?
Regards
Satish.

Compsition Environment: interface controller in web dynpro

Hi All,
(I know this is not right place to raise this question but if anyone know)
I've installed NW CE 7.1 and am trying to trigger an event created in the Interface controller. I observed that the methods and the events declared in the interface controller are not accessible in the view level. Has the WD design time concepts undergone a change?. In short, I'm not able to add the Interface controller as a required controller in any of the views that are present inside the same component.
Any clues on this?
Regards
Satish.

Since one dedicated link is there between
Comopnent and Interface controller.

Regarding Component interface controller

hi all
Can anyone explain me use of Component Interface Controller under Component with example.
Thanks in advance
Imityaz

Hi,
Interface Controller
One Web Dynpro Component may declare the use of another Web Dynpro Component to form a u201CParent-Childu201D usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the childu2019s interface controller.
if an interface controller is part of a component interface, the controller editor is in change mode and the context, the events and the methods can be implemented and edited directly.
Refer this thread,step by step procedure is there.
/docs/DOC-8061#61 [original link is broken]
http://help.sap.com/saphelp_nw70/helpdata/EN/47/45641b80f81962e10000000a114a6b/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/44/0dcafa2d9d1ca2e10000000a11466f/frameset.htm
Regards,
Sunaina Reddy T

Interface controller example

I created simple example of interface controller.
I embedded view of used web dynpro component in the main web dynpro component
I get the error on deploying :
The initial exception that caused the request to fail, was:
   java.lang.UnsupportedClassVersionError: def/wdp/InternalDef (Unsupported major.minor version 49.0)
I also changed my jdk version to be 1.4.2_12   but still it doesnt work
I created in the DCs in local developement.
kindly suggest solution
thanks

Thank you very much for your answers.
1) i had not only changed the jdk version to 1.4.2_14 in windows preferences but also re installed the entire nwds with the new jdk
2) i reaslised that while doing it, i had given wrong path for jdk. c:/programfiles/java.......... instead of c:/j2sdk              so i changed that
3) i recreated both the DCs after having changed the jdk
4) on building the DC i got some errors, so i put some missing plugins in the eclipse
after all this is worked
thanks again for responses,
-r

Fireing outbound plug of interface view from within component

Hi all,
is there a better way of firing an outbound plug of an wd component interface view than from within the interface view controller itself?
The problem is, that you easly get a cyclic reference if you evaluate inbound component plugs in the interface controller (usage from int view ctrl --> int ctrl needed) and then try to fire an outbound plug from this interface controller (usage comp int --> comp int view usage needed).
One workaround is to use some custom controller with usage of the interface view, but this doesn't seem to be a nice solution.
So is it possible to fire outbound comp plugs from, lets say the component controller - without any usage releation to the comp int view - instead, maybe via wdComponentAPI? If yes, could you provide a code snippet?
Thanks you and best regards,
Christian

Hi Christian,
this is not possible by using the public API only, i'm afraid. It is of course possible, if you decide to forget about the possible drawbacks of using methods and classes reserved for internal use. But you have to use it at your own risk. I hacked this together some weeks ago, don't know whether it still works
* Fires an outbound plug of an interface view with parameters.
* @param wdComponentAPI Component API "owning" the interface view.
* @param windowName Name of window
* @param plugName Name of outbound plug
* @param callerParameterMap optional Map of plug parameters.
public static final void fireOutboundPlug(
IWDComponent wdComponentAPI,
String windowName,
String plugName,
Map callerParameterMap)
throws WDRuntimeException {
// Find window requested
IWDWindowInfo windowInfo = wdComponentAPI.getComponent().getComponentInfo().findInWindows(windowName);
if (windowInfo == null) {
    throw new WDRuntimeException(
      "Can't find window: " + windowName + " in component: " + wdComponentAPI.getQualifiedName());
// Get info of interface view
IWDInterfaceViewInfo ifViewInfo = windowInfo.getInterfaceView();
if (ifViewInfo == null) {
    throw new WDRuntimeException("Window: " + windowName + ", no interface view info found");
// Find outbound plug
IWDOutboundPlugInfo outboundPlug = ifViewInfo.findInOutboundPlugs(plugName);
if (outboundPlug == null) {
    throw new WDRuntimeException(
      "The interface view: " + ifViewInfo.getName() + " has no outbound plug: " + plugName);
// Parameter passing
Collection plugParameters = outboundPlug.getParameters();
// TODO make check optional, check caller map parameter keys against existing
if (plugParameters == null || plugParameters.isEmpty()) {
    // No caller parameters allowed.
    if (callerParameterMap != null && !callerParameterMap.isEmpty()) {
      throw new WDRuntimeException(
        "The outbound plug: " + plugName + " has no parameters, callerParams must be empty/null.");
// TODO This is a hack, use of internal WD runtime classes and methods (don't use productive).
InterfaceView ifViewController =
    (InterfaceView) ((Component) wdComponentAPI.getComponent()).getController(ifViewInfo.getName());
ifViewController.navigate(outboundPlug.getName(), callerParameterMap);
Please remember, that not everything which is technically possible, makes sense
Regards
Stefan

How to define exit plug for interface view?

hi experts,
I am trying to define exit plug for interface view , but i am not able to make interface view into change mode. it doesnt allow me. what should be done/
Thanks,
saurin shah.

Hi ,
Check the Interface in the Window this will reflected in the Interface Window
Regards
Vikranth

Public functions in the interface controller

Hi all,
My project includes 3 components. Each component has its own Iview and public functions.
The application will run a main component that uses those 3 components.
What is the right way to call the public functions?
Should I announce them in the interface controller?
Or should I use plugging for doing it?
If I announce them in the interface controller, how I am calling them from the main component?
Thanks,
Noy

I can't see the public function. I try to do:
wdThis.wdGet<componentName>ComponentUsage().
And
wdThis.wdGet<componentName>ComponentUsage().getInterfaceController().
To be clearer:
I got 2 components: component A, which uses component B.
Component B has a public function in the component controller called "func1". This function is also announced as a method in the interface controller.
What I want to do is to call func1 from the component controller of component A.

Design question: Interface Controller vs. component controller

Hello,
I have a component A. This component has a component controller (compController) and an interface controller (intController).
Component controller has method compMethod()
Interface controller has method intMethod()
- Am i allowed to call intMethod from component controller? ( i'm pretty sure this isnt bad design because this is also done in the tutorial on eventing)
- Am i allowed to call compMethod from intController or is this bad design?
- Am i allowed to subscribe compController to event in intController or is this bad design?
Kind regards,
Joren

Hi Joren,
like Valery already pointed out, we recommend not to implement any logic in the component interface controller but only implement methods used for delegating logic to the component controller. This is based on the fact, that the component interface controller will be implemented by the component controller in the the next major SAP NetWeaver Release. This means that it will not have its own Java class like in NW04 and NW04s. To simplify migration the interface controller code should be as slim as possible by applying the delegation principle.
You wrote:
<i>- Am i allowed to call intMethod from component controller? ( i'm pretty sure this isnt bad design because this is also done in the tutorial on eventing)</i>
Yes, my (very old) tutorial on serverside eventing exposes a public method <i>fireEvent()</i> which is invoked by the component controller. In early versions of NW04 the wdFireEventInnerEvent() method was not exposed in the IPublic-API of the component interface controller but only in the IPrivate-API. Therefore an additional method fireEvent() must be defined to fire the event from another controller. As a negative side effect, this public fireEvent() method is also exposed by the IExternal-API of the component interface controller so that the event can be fired from outside (by the Embedder component) which is not desired in most cases.
Meanwhile the wdFire<event name>() method is exposed by the IPublic-API of the component interface controller, so that the public method fire<Event name>() is no longer needed.
I will update the tutorial in this respect so that it again propagates best practices.
Regards, Bertram

Difference between interface view and interface controller

Hi,
What is the difference between interface controller and interface view?
When we will use interface controller and when we will use interface view?
How do we create an interface view?
How do we attach this interface view to a view in another component
Regards
MQ

Hi
Interface View Controllers
A) Implement event handlers which are called when ..
-starting (start-up plugs) Web Dypro applications
-a component is reached via navigation (inbound plugs)
B) Allow fireing outbound plugs (navigation)
C) Allow firing exit plug
D) Have no own context, public methods or events
Interface Controller of a Component
The interface controller of a Web Dynpro component contains all context nodes, events and methods of the component controller to which you assigned the Interface addition in the Controller Editor. These parts can be displayed in the interface controller view, although you cannot edit them here.
Interface Controller of a Component Interface
A Web Dynpro component interface can be created independently and defined so that it can be implemented later in any components (see working with Web Dynpro Component Interfaces in the Programming Manual of this documentation). That is why in this case you can define the context nodes, methods and events you require in the interface controller view. The relevant implementation then takes place in the component controller of the implementing component.
Check this links and work on it.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#13 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#12 [original link is broken]
Interface view and interface controller
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945
Difference between custom controller and interface component
Thanks and Regards,
Tulasi Palnati

Software needed for the USB device, "USB Interface Controller TEST2.0"

My mother recently acquired a digital camera. She acquired it from a second-hand store, which did not include an interface cable or software. The manual (and the USB port on the camera) indicates that a male-male USB cable is necessary for photos to be copied to the hard drive.
I was not successful in locating such a cable at any local electronics store (I assume such a cable is now out-of-date). I purchased one from a seller on eBay. The brand is "e circuit electronics".
Upon powering up the camera with the cable connected to it and the computer, the following message appeared:
"Software needed for the USB device "USB Interface Controller TEST2.0" is not available. Would you like to look for the software on the Internet?"
I clicked "Yes". After an approximate two-minute wait, another message appeared stating:
"Software Update is not able to connect to the Internet. Please check your configuration and try again."
I deleted, "Software Update Preferences" in the Preferences folder inside the System Folder, without solving the problem. How do I solve the issue of allowing Software Update to connect to the Internet?

Thank you for your continued assistance, BDAqua. Unfortunately, the driver you linked to does not seem to be compatible with the camera. It is a driver for the V20 model, whereas my model would correspond to be a V2755, as referenced from a list of other Vivicam models when during a search at the Open Drivers web site.
From the system requirement about the card reader you gave me, it will not work, as this system is running 9.1. I am hesistant to upgrade this computer to 9.2, as I have experienced system unstability with that version, with even the 9.2.2 update applied.
In the mean time, I have e-mailed Vivitar regarding this issue, but have as of yet received a reply.
I am not certain as to other specifics to give you, in order to solve the Software Update problem. Please elaborate.
Yes eww, the computer in question is able to fully connect to the Internet for all that I need. I am fully aware of the difference between a computer connecting to the Internet, and a computer connecting to a digital camera. I have 15 years of Macintosh experience.

Windows 7 and DV6500t (ICH8M LPC Interface Controller)

I recently loaded (via dual boot) Windows 7 onto my HP dv6500t. All went fine and all is working OK except for one issue. In Device Manager, I have one unknown device. Looking at its properties, it shows a location of: "ICH8M LPC Interface Controller - 2815" and the driver is unavailable. I tried to use sp36881 (Intel Chipset Installation Utility for ICH8) from HP's site and this did not work. Any help?
Message Edited by MagicPinball on 09-15-2009 09:00 AM
This question was solved.
View Solution.

HP Quick Launch Buttons here
** Say thanks by clicking the "Thumb up" icon which is on the left. **
** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

Changing a Network Interface in DAG Replication Network after going P2V

I have a DAG member suffering severe hardware failure so I have gone P2V with it. It's functioning fine, except that the DAG Network Interfaces have changed - The MAPI Interface was on "Local Area Network" on the physical server, and is now
on Local Area Connection 7 on the VM. However, the DAG settings still point to "Local Area Network" and will not let me change it. Same thing for the replication network.
I have lost redundancy due to this, so I need to get it repaired pretty promptly.
Removing and re-adding the subnet in the DAG network has no effect - it still references the old physical NIC instead of the new virtual NIC, despite the new virtual NIC having the same IP as the old physical NIC.

Try to change the network binding on the server
http://technet.microsoft.com/en-us/library/cc732472(WS.10).aspx
Try to delete the hidden network adapters as well.
Open Device Manager, from the File menu, expand the View and select the Show Hidden Devices option. This will enable and show any old un-used devices in the window
http://www.gfi.com/blog/how-to-remove-hidden-network-adapters-from-virtual-machines/
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Intel(R) 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8

Intel(R) 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
DVD / CD RW not working. 2 different drives installed together . Duel Roms not running media but are seen in My Computer.

Try the suggestions outlined in
this post.
Carey Frisch

Change plug to interface controller in Netweaver 7.1

Similar Messages

Maybe you are looking for