Development Approach

Hello
Greetings!
I have a general question about how to approach the portal development process.
The J2EE technology has improved and now we have a lot of useful standards like EJB 3.0 and Java Server Faces, however if you want to use this kind of technology you have to use Oracle Application Server 10.1.3 but if you want to incorporate this kind of development in Oracle Portal 10.1.4 there are limitations because it uses Oracle Application Server 10.1.2.0.2. I think that JSR-168, WSRP and Oracle JPDK have some limitations if you want to enrich the Portal Interaction.
My question is:
What is the best approach to start a development accesible from Oracle Portal ?
(JSR168, WSRP, Oracle JPDK) or use new technologies like EJB 3.0 and JSF and incorporate them with a mechanism like Iframes ?
Thanks!
Ramiro Ortiz

Did you ever get an answer to this question and make a selection about which technologies to use ?? I'm going down the same path right now (AS 10.1.2, want to use JSF) and I'd like to hear what you've discovered.

Similar Messages

Difference in Inside-out and Outside-In development approaches

Hi,
Can you please tell me difference between Inside-out and Outside-In development approaches. I heard it with respect to adapters and proxies.

Hi Rupesh...
<b>Nice question as a Project Management point of view..</b>
We can go for Interface development in 2 ways..:
1. Create Interface objects in XI and replicate that thing in both sides for further development..
Adv :: You are not dependent on others for XI development....Like in case of Proxies.
Disadvantage : Skill in proxy required..
2. Create RFC/IDoc in end systems and import those in XI for development..
Advantage : People are usually familiar/comfortable with adapter oriented approach rather then adapter less..
Disadvantage : you can't start your work before the end systems have completed their task..Once they have completed then only you can import the RFC/IDoc and proceed..
About deciding the approach : It depends upon teams strength/situation ...Like in one of the project i have worked Project needs to be done by a Consortium of 3 teams from different companies..One for handling legacy one for R3 one for XI..
So we went for Approach 1 as we don't want our work to be dependent on others..
Hope i am clear..
Regards,

Magic Values - A Question of Development Approach

Hello folks,
I have a question for you PL/SQ developers out there. This isn't a specific problem or query I'm raising here, more a question of general approach. I'm probably not using the correct terms here so forgive me. Also, I've already posted this in the ApEx forum, however there's a degree of overlap into pure PL/SQL so I thought you were all bound to have experience of something along the same lines.
Anyhoo...
How to deal with Magic values - i.e. values which hold no intrinsic value in and of themselves, other than for state, process or conditional logic control. I use them quite a lot in my PL/SQL code (as I'm sure most developers do in one context or another).
From a Data architecture perspective, I'll generally have some sort of table for storing the 'facts': names, addresses etc, etc. Any application-specific magic values ('status', 'type') will be held as a foreign key in this table, which will reference a form of lookup table.
Example:
EMOTION
ID   Description
==   ===========
1    HAPPY
2    SAD
3    NEUTRAL
PERSON
NAME ... EMOTIONAL_STATE
====       ===============
BILL       1
JERRY    1
BRIAN      3
DONNA    2So far, so banal...
Now, say I have a process that needs to reference someone's emotional state for some sort of conditional logic:
declare
   n_estate number;
begin
   select emotional_state into n_estate
     from Person
    where name = 'BILL';
   case when v_state = 1 then
      -- do something
   case when v_state = 2 then
      -- do something else
   else
      -- otherwise something else again
end case;
end;straight away your bad code radar should be going crazy: you're coding literals in there! So, the old java programmer in me wants to store these as constants - I'll generally square them away inside a package somewhere, like so:
create or replace package PKG_CONSTANTS as
   ES_HAPPY constant number:= 1;
   ES_SAD constant number := 2;
   ES_NEUTRAL constant number := 3;
end PKG_CONSTANTS;Thus the code becomes
Case when v_state = PKG_CONSTANTS.ES_HAPPY then ...Herein lies the crux of the issue. I'm effectively defining the same value twice: once in the lookup table (for data integrity) and once in the package. If new values are defined (say "Existential Ennui") or existing values are changed, I need to make sure the two are aligned, which hinders maintainability.
I thought about initialising the values as sort of pseudo-constants in the package initialise code but then you end up replacing one literal with another; you end up with code like:
create or replace package PKG_CONSTANTS as
   ES_HAPPY number;
   ES_SAD constant number;
   ES_NEUTRAL constant number;
end PKG_CONSTANTS;
create or replace package body PKG_CONSTANTS as
   rf_curs sys_refcursor;
begin
   for rf_curs in
      select ID
             ,description
        from EMOTIONAL_STATE;
   loop
      case description
      when 'HAPPY' then
         ES_HAPPY := ID;
      when 'SAD' then
         ES_SAD := ID;
      when 'NEUTRAL' then
         ES_NEUTRAL := ID;
      else
         null;
      end case;
   end loop;
end PKG_CONSTANTS;I also thought about using dynamic PL/SQL to re-write and recompile the constants package in the event of a value being changed in the lookup table...seems like quite a lot of work, given that the magic value is pretty much meaningless outside of the scope of the application.
So... how to deal with this? What approach to you take? Does data integrity over-ride application programming style?
Any contributions would be welcome!

Hello,
I had a look through the article (8 year's worth of thread? Sheesh that's dedication!) and yet it doesn't quite express exactly what I'm meaning. The argument there appears to be between dynamic SQL with bind variables versus static SQL. I'm not talking dynamically building queries or the use of bind variablers per se - its more related to how one makes use of magic values within the context of conditional logic and application code.
The example I chose happened to use a case statement, which maybe blurs the line with the syntax of pure SQL query and perhaps why you thought I was going down the dynamic SQL route, but I could just have easily replaced them with a series of 'if elsif else end' type expressions.
From an application developer point of view, the mantra of 'abstraction through constants' is the norm - referencing literals in expressions is generally frowned upon, with the possible exception of special numbers such as 1 or 0 (for incrementing counters, referring to the start of arrays etc, etc). One only has to look at the work of Feuerstein to see this - time and again in his books, the concept of delegating constant values (and subtypes) to well-defined areas (the "Single Source of Truth") rears it's head.
Now in the Oracle world, data architecture generally has primacy, which in this case manifests itself as the use of foreign keys in data tables referencing the equivalent lookups (dimensional modelling, star diagrams and the rest) - thus even special, application-specific values, i.e. with no intrinsic value in the real world, end up in your ERD. There appears to be a bit difference of opinon, depending on the background of the developer.
Hence my question - how do you, as developers, deal with these sorts of situations?

Development Approach for WebCentrer Portal

My task: to develop portal applications with rich functionality.
I see two approaches to this question in the http://docs.oracle.com/cd/E29542_01/webcenter.1111/e35813/pywcp_planning.htm point 1.8
May I use Portal Builder Approach with develop custom components (using JDeveloper) to do what I want, the same as it can be done by means of Portal Framework Approach?
Or it is better to use immediately Portal Framework Approach?
Portal Builder Approach is represented simpler and clear, but I am afraid to face things which can't be realized with Portal Builder Approach..

as per my understanding you should look what you want.If you really want customized features. use custom task flow
read this for making more choice
http://www.techartifact.com/blogs/2013/05/webcenter-portal-vs-webcenter-spaces.html
and in case of lot of customization portal builder is better approach

Table per locale - i18n application development approach

I learn that I shall use table per locale approach for a multi-language application development. And I am in a situation that no all entries will have multi-language versions. I can image some possible issues on data retrieval and update. Can anyone share experience in this regard?
Thanks very much in advance.

I would share my experice here.
For the internationalization of our product, we do not have a table per locale, rather we have a row per locale in the appropriate table. We have localeCode, messageCode and messageDescription columns in that table and the application picks up the right row depending on user locale.
By default we have English data in the database. For inserting french data we run a database script which inserts same rows as English rows appended by some french characters. This is for internal testing purpose only.
In addition, we also run another translation script for creating locale specific resource bundle files and tiles files.
So, labels will come from tiles files and data/messages would come from resource bundle and database. These scripts will not be delivered to the customer. They have their own translators and its their job to provide translations at all necessary places.
After running this script we have experienced that the server takes more time to startup.
Rahul

Best Practises and Guidelines for SharePoint 2013 Development

Currently We are using SharePoint 2010 and doing a lot of enhancement and customization in the portal.
we are planning to migrate SharePoint 2013 after 6-9 months.
I want to know what are the best practices and guidelines for development in SharePoint 2010 keeping one thing in mind that customization should be compatible or can easily migrate to SharePoint 2013 so that re-engineering effort would be as minimum
as possible.
We have every possible piece of customization in SharePoint 2010 portal like web part, event receivers, workflows, master page, page layout, custom search etc.
Please do the needful.

Best practices don't really apply here. They are generally rules of thumb that you can apply without thinking too much and be pretty much right. Development is by it's nature too varied to allow that sort of best practice guidance.
Having said that the main thing you should be concerned with around the choice of development approach in 2013 is the intended future of your client and the application. If they are making a move to the cloud you should be concentrating on the app model
and rapidly phasing out farm solutions. If they are considering it then you can still consider using the more old-school options of farm solutions and sandboxed solutions. If they can't go to the cloud because of data security etc. then you are more or less
free to use what you like.
Also, try to move to client side processing wherever possible. MS are only going to make server side work less pleasant in future.
Beyond that, get to some conferences and start chewing through some of the blogs on the topic.

GeoRaptor 3.2.1 Released for SQL Developer 3.x

Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
     Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
     If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
     Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
     If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
   This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
     1. Metadata entries which have no underlying oracle object (orphan)
     2. Metadata entries for existing underlying objects (existing case)
     3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
     Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
     as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PM

Simon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan

Web services Development

A general question for the group (sorry if this is off-topic, if there's a better
forum for this type of Q let me know).
I'm a web services and web app developer who is new to BEA. In the past I've used
toolkits like Axis for web services and I've always preferred this approach. It
seems to me that using BEA I can develop Web Services in one of two ways. The
'low-level' way where I could use the command line tools (or ant) to create, deploy
and manage the code, or I could use WLW and the nice attribute driven approach.
It strikes me (on first blush) that these techniques are not compatible, so if
I choose one I have to stick with that, and I shouldn't (can't) mix and match
the two.
As a relative newcomer to this community which one should I choose?
Which are people out there using?
Can the approaches me mixed?
What implications does using one or the other have in terms of deployment and
the type of WLS I have installed?
Again sorry if this is off topic, or an RTFM. If either of these is the case pointers
to the FM would be appreciated.
Thanks,
Kevin Jones

I think if you are looking for training in "BEA web services" then do
it the WLW way.
However, if you think your web service may be deployed to a non-BEA
app server, then pick up the standards.
This is true for regular web apps using struts vs. WLW's 'netui'
and JSR 162 vs. WLW Portals as well.
Kevin Jones wrote:
Thanks Michael,
anybody else have any comments?
For example if you were looking for training in BEA web services would you expect
it to be WLW or 'command line' based?
Kevin
"Michael Wooten" <[email protected]> wrote:
Hi Kevin,
The two web services development approaches are for two different audiences,
so
it's up to you to select which is more to your liking :-)
Developers who are familiar with the Apache Axis Web Services Platform,
will find
lots of similarities in the Ant-scrpt based approach that the WLS 8.1
Web Services
Platform uses. This would also be the environment for those that really
like to
see that their code uses classes from a standard, like JAX-RPC or SAAJ.
Workshop is really targeted at developers who are less interested in
the mechanics
of Web service construction, and more interested in what they want the
web service
to do. It offers developers with this mindset, almost complete isolation
from
the technologies associated with web service development (i.e. SOAP,
WSDL, XML,
etc.), while still producing a deployable web service that can interoperate
with
web services created by other Web Service stacks.
Again, both of these approaches have healthy developer audiences, so
I see no
real reason to promote one over the other. Personally, I think it makes
sense
to become adept at both.
All in all, I'd have to say that Workshop makes better use of the developer's
time :-)
Regards,
Mike Wooten
"Kevin Jones" <[email protected]> wrote:
A general question for the group (sorry if this is off-topic, if there's
a better
forum for this type of Q let me know).
I'm a web services and web app developer who is new to BEA. In the past
I've used
toolkits like Axis for web services and I've always preferred this approach.
It
seems to me that using BEA I can develop Web Services in one of twoways.
The
'low-level' way where I could use the command line tools (or ant) to
create, deploy
and manage the code, or I could use WLW and the nice attribute driven
approach.
It strikes me (on first blush) that these techniques are not compatible,
so if
I choose one I have to stick with that, and I shouldn't (can't) mixand
match
the two.
As a relative newcomer to this community which one should I choose?
Which are people out there using?
Can the approaches me mixed?
What implications does using one or the other have in terms of deployment
and
the type of WLS I have installed?
Again sorry if this is off topic, or an RTFM. If either of these isthe
case pointers
to the FM would be appreciated.
Thanks,
Kevin Jones

Problem with manage/consume content separation approach

Hi,
In the Portal 10G manual and in several other sources, ORACLE recommends separating content-management from content-publication in different page groups. That's the approach we've adopted, and it seems reasonable. BUT now I find that contents published as portlets are like black boxes not searchable in the page group where they are published! That and not giving search feature at all to the users is almost the same! There must be some solution for this, I find it a major drawback difficult to ignore, since it makes this approach unacceptable.
Please, any help on this will be very appreciated, for it may yield critical decisions in our portal development approach.
Big thanks in advance.

The default portal search is a respository-based search, so will always return the page on which the item is managed. In your use case, it probably makes sense to either (1) not expose the page attribute in your search result (2) use UltraSearch as your end user facing search. Note that UltraSearch creates its index via a crawler, therefore will only return content that is 'public'.
If you have additional, follow-up questions on search options, I recommend a post on the portal search forum: http://forums.oracle.com/forums/forum.jsp?forum=12

CRM ABAP Development aproach

Hi Experts,
Can any body tell me the difference in the approachs of development between CRM ABAP and ABAP.
or only the CRM ABAP development approach.
jaffer vali shaik

Hi,
As far as ABAP is concerned, its same in R/3 and in CRM. But in CRM, its more oriented towards OOABAP. For example, BADI, Model access class of PCUI all are oriented towards OOABAP.
Regards,
Karthik.

Development Strategy Input Request

I have a client who wishes to add Purchase Requests from an existing external Java application into SRM 7.0 on a SAP ECC 5.0 ERP platform. Their request proposes that this could be easily accomplished using the "BAPI_REQUISITION_CREATE" transaction.
We've downloaded the NetWeaver 7.02 ABAP Trial to evaluate possible development strategies. With a desire to follow established Best Practices we could use some advice on the best development approach.
Does the NetWeaver 7.02 ABAP platform offer the best and most appropriate development environment? If so, can we add SRM functionality to test on?
Will the Trial version suffice for the development simple non-UI application for the submission of Purchase Requests? We do not have SAP deployed in our development environment.
Which would be the better approach, ABAP or Java? If Java is the recommended approach, is the Trial development environment suffice?
Any guidance or recommendations would be greatly appreciated. Thanks in advance!

Hi,
In addition to the above....
Webdynpro is preferred when minimum coding is required and applications are to be developed fast with minimal time and effort.
WD is also used when components are to be reused. Also highly skilled programmers are not needed to develop a WD application.
Java script can be used with Portal applications. Refer docs on creating Portal Applications. U'll get to know better.
Regards,
Pooja.

Agile Development in an SAP Landscape

My team is looking to shift from a 'regular', waterfall-type development methodology which delivers 2 large functional releases per year to a more flexible, nimble project based approach based on Agile Development methodologies.
The goal is to be able to treat each project independently from a resource and scheduling perspective - so multiple projects could be underway at any one time but each one potentially running on a different time line. Of course, life-cycle support for the production environment would be on-going at the same time.
The problem we face is defining an SAP system landscape that supports this approach and that allows for the management of the inevitable conflicts that will arise when different projects require changes to the same development object.
I'm interested to hear feedback from anyone who has implemented an Agile Development approach within an SAP environment ( successfully or not ! ) as well as ideas for what a possible Agile SAP landscape could look like.
Thanks
Tim

Our team has been adopting some agile practices and have seen some great benefits. We have not embraced one methodology entirely (XP, Scrum, etc.). We're taking bits and pieces that make sense in our environment and adopting them incrementally.
Here's an example of some of the things that we're doing:
1. Chunking out development tasks. Basically working with the requirements or functionality that we know and not waiting until every possible scenario is clearly (or not so clearly) defined. We try to get stakeholders (business users and BPx's) looking at our programs and prototypes often to ensure that we're on the right track. This chunking out of tasks has been a benefit in that it is easier to manage (from a manager and developer perspective) and it gives us clearly definable goals for what we're shooting for in a fixed time frame (1 week). We talk individually every day (short spinarounds) to ensure that we're on track and identify any potential risks.
2. Modeling of requirements. This proves extremely valuable to our developers, functional folks, and business users. This usually involves grabbing a couple of folks and whiteboarding ideas to ensure that everybody has a clear understanding of what is going on. I will admit that this we certainly don't do it as much as we should, but it's something that we're working on doing as much as we can.
3. Frequent builds/migration. We currently transport released changes to test every 30 minutes in the ABAP stack. This allows us as developers to move on to the next task and allows our testers a quicker turnaround of bug fixes and new functionality. We move production code twice a week. For the JAVA side, we do a "JIT" build/deployment. As fixes need to be migrated, we check in/build and deploy. Since the NWDI is still new to us, we haven't done much investigation on automating this process, but I imagine that we will do so in the future.
One of the challenges that we ran into was thinking that the code was the only thing that matters (which you might get from some agile camps). Just because you're modeling and documenting (just enough documentation), does not mean that you're not "agile". You don't throw out design and analysis just so you can sit down and write code to have something to show somebody. The collaboration and clarity that agile practices provide is one of the keys to making it successful.
We started implementing some of these practices in the development group about 8 months ago and since then we've seen some interest/adoption in our project management group and functional teams. I would imagine that we'll continue to pick and choose practices that work for us...try some out, see what happens, adapt, evolve, etc. So far so good in my opinion. From a managment perspective, it really has made it easy to know what people are working on and how productive we can be as a group. From a developer's perspective, it makes development easier and more fun when you have a clear target in front of you and you can throw out ideas in a modeling session. From the end user perspective, they seem to like that we can roll out production ready functionality in an incremental way so they don't have to wait 6 months to get something that they can see and use. From my limited experience, it seems to be a much better way to develop applications.

Developing a code for KM

Hi All,
I am a newbee in Portal programming. The client has given me a java program under KM to develop using PDK.
I have installed the Eclipse and its plugin and also installed the PDK. Able to run some small sample java reports. However I am not able to figure out how to access the KM database so that I can start with an actual requirment.
Waiting for some suggestions.
Regards,
Rajan.K

Hi Rajan,
which kind of KM component do you want to develop? We have different development approaches in general: 1. Using the existing KM functionality within portal applications or 2. extending the KM with custom functionality.
Best regards,
Thilo

Adobe Rich Web Experts Speaking at India's Biggest Independent Technology Event

Great Indian Developer Summit is India's Biggest Polyglot Conference for IT Professionals
Bangalore, March 25, 2010: At the 2010 edition of Great Indian Developer Summit learn how browser and rich web technologies such as AJAX, DHTML, Mashups, Web 2.0, Enterprise 2.0 technologies, and Rich UI technologies are making money and gaining market-share for some of the leading businesses in the world. On 21st and 23rd April 1010, Rich Web experts from Adobe will speak about the changing face of web applications, enriching cloud applications with Adobe Flash, agile interaction design, developing multi-screen applications on Flash, building enterprise RIAs with Flex and Java, building data centric applications and killer RIAs with PHP and Flex. The summit will be held at the Indian Institute of Science in Bangalore.
Ramesh Srinivasaraghavan, who leads the Adobe Flash Platform Evangelism initiatives of Adobe India, will keynote on the state of art in web application development and identify trends that could transform the way we create and use web applications. He will also conduct a separate session exploring the role that RIA technologies play in the new paradigm of developing applications for the cloud.
The ubiquity of Adobe's Flash Player and AIR spans the spectrum of Web, Desktop, Mobile and devices such as set top boxes. Flash Engineer Hemanth Sharma will lead attendees through the development workflow for building multi-screen applications. In a separate session, Sujit Reddy explains model-driven and code-driven development approaches to build data-centric applications with Adobe Flex and Java. Also discover how you can migrate your existing J2EE applications to Adobe Flex based RIA's easily. Computer Scientist Harish Sivaramakrishnan, popularly known as flexgeek, will lead attendees on a whirlwind tour of Adobe Flash Catalyst - a sparkling new tool which he says is the best thing that happened to the designer-developer collaboration after sliced bread.
On 23rd April while Prashant Singh conducts a 180-minute workshop on Data Centric Development features of Flash Builder and how to use them to create a Rich Internet Application powered by Java, Shyamaprasad will teach how to build PHP powered rich Internet applications using Flex. Starting off by setting up the Zend framework he will demonstrate how to build a complete Flex application that connects to a PHP server, using version 4 of Flash Builder.
On 21st and 23rd April 2010, at GIDS.WEB Conference & Workshops learn how browser and rich web technologies such as AJAX, DHTML, mashups, Web 2.0, Enterprise 2.0 technologies, and Rich UI technologies are making money and gaining market-share for some of the leading businesses in the world.
About Great Indian Developer Summit
Great Indian Developer Summit is the gold standard for India's software developer ecosystem for gaining exposure to and evaluating new projects, tools, services, platforms, languages, software and standards. Packed with premium knowledge, action plans and advise from been-there-done-it veterans, creators, and visionaries, the 2010 edition of Great Indian Developer Summit features focused sessions, case studies, workshops and power panels that will transform you into a force to reckon with. Featuring 3 co-located conferences: GIDS.NET, GIDS.Web, GIDS.Java and an exclusive day of in-depth tutorials - GIDS.Workshops, from 20 April to 24 April at the IISc campus in Bangalore.
At GIDS you'll participate in hundreds of sessions encompassing the full range of Microsoft computing, Java, Agile, RIA, Rich Web, open source/standards, languages, frameworks and platforms, practical tutorials that deep dive into technical skill and best practices, inspirational keynote presentations, an Expo Hall featuring dozens of the latest projects and products activities, engaging networking events, and the interact with the best and brightest of speakers from around the world.
For further information on GIDS 2010, please visit the summit on the web http://www.developersummit.com/
A Saltmarch Media Press Release
E: [email protected]
Ph: +91 80 4005 1000

Im not sure if this is the right place to post this, but anyway thanks for the info :)

Flash player does not work with Ie or Firefox with win 8.1?

Flash player does not work with Ie or Firefox with win 8.1 64, If i try and play a video I get the message to install Flashplayer.
If I try and install it it says it is already installed. Your onsite installer says it is not applicable to my machine.
I have followed all the normal steps re enabling addons and active filters etc.
all to no avail Pc is Dell 6 months old, Flashplayer has never worked on this machine. Last MS update mid Dec 2014.
Version of flashplayer is 15....03.......

Flash Player is a built-in component of Internet Explorer. There's nothing separate to download or install.
Firefox requires a different version of Flash Player (the NPAPI plug-in), which will be served to you if you go here: http://get.adobe.com/flashplayer using Firefox; however, there are some unique stability issues related to Firefox on Win8.1, and you're probably better off using Google Chrome if you want a more optimal experience with Flash Player.
For problems where IE isn't being detected by sites that require Flash:
First, confirm that ActiveX Filtering is configured to allow Flash content:
https://forums.adobe.com/thread/867968
Internet Explorer 11 introduces a number of changes both to how the browser identifies itself to remote web servers, and to how it processes JavaScript intended to target behaviors specific to Internet Explorer. Unfortunately, this means that content on some sites will be broken until the content provider changes their site to conform to the new development approach required by modern versions of IE.
You can try to work around these issues by using Compatibility View:
http://windows.microsoft.com/en-us/internet-explorer/use-compatibility-view#ie=ie-11

Development Approach

Similar Messages

Maybe you are looking for