WHEN SHOULD I BE USING A COMPONENT INTERFACE?
If you need to insert/update/delete data through PeopleCode, and your PeopleCode will require replicating a lot of existing business logic that already exists in a component then a component interface is the best approach. Once you learn how to use them, they will be the fastest and most robust solution for such cases. If you are performing simple changes, then using a CI becomes overkill as there is an overhead to using a CI on both the system and on development time. Similarly, large amounts of batch processing may be too much for a CI to handle or may be considerably slower using a CI.
| Is This Answer Correct ? | 0 Yes | 0 No |
Do you know is web sphere certified on people tools 8.1x?
Why does my component interface not have a Create method?
Will tuxedo continue to be used in peoplesoft/websphere or peoplesoft/weblogic environment?
Tell me where are workflow work items found?
Architecture of CI? Or what are the main elements in the component Interface?
Tell me what hyperlinks available in peoplebooks? Some options with different hyperlinks not available in peoplebooks, select the correct one?
Explain when a business requirement in fit/gap analysis does not meet by peoplesoft then?
How to catch error messages in CI?
Can you explain how does the people soft enterprise portal work with 8.1x and 8.4 applications?
Tell me both bea weblogic and ibm websphere have the ability to plug into many different web servers. Does peoplesoft support the web servers that they plug into?
When I test my component interface, why do I get a "Not Authorized" error?
Explain why is peoplesoft no longer supporting apache jserv?