How to migrate an existing non-SAP-application

[Former Member]

Hi,

is there anybody who has expirences and could help to answer some basic questions (within a little consulting project, of course)?

What topics would be relevant for such a project? There are so much different possibilities within that platform:

What is the right topic to realize the interface - xApps, CAF, Web Dynpro, Enterprise portal,...?

What could be the right subject for using an existing Database structure and existing (or modified) Web Services - IX, MDM, WAS, ..? (Data Entry over the user interface and data processing with the web services should us the same data from an existing database definition).

Our system (Windows-GUI, Windows platform, OOP, Oracle or SQL-Server) is a special application for a special branch (utilities). More information on demand.

Any hint is appreciated, thanks a lot.

Kind regards

Christian Hartlieb

[Benny · Accepted solution]

Hi Christian,

what you want to do should lead to the right technology. First of all: Do you want to relally port it or do you want to connect your existing application?

The latter is almost always best done with process integration (aka XI). If you want to do a port, you have to decide whether do it with ABAP or in Java. This depends on your knowledge and willingness where to invest.

The user interface I'd recommend either Visual Composer (if you can get it, as it is short before release) or Web Dynpro.

Any direct implementation is done on WebAS.

Regards,

Benny

[Former Member · Accepted solution]

Hi Benny,

thank you for your reply. Followed I'll give you some more information res. answers to your questions:

Concerning "First of all":

On the base of my actual knowledge I would like to do a bit of both. I would like to port the user-interface (Web) and I would like to connect the existing Web Services. Our Web Services would need their own Web Application Server and Data from an existing database structure. The database structure must not be identically - some modifications are possible. In general the content of the database is independent from Standard-SAP (except the Customers/Business-Partners).

The preferred technology should be Java.

Some of the important questions are:

1- Is it possible to define own tables within the platform? (Certainly yes - namespaces? How? What are the requirements?)

2- What requirements are existing for the use of external Web Services in the NetWeaver SOA (Contracts, rights,...)? What changes are probably necessary?

3- Is it possible, that Web Dynpros have direct access to (our) specific database tables? (How is the data access managed?)

4- Which Software and licenses from SAP are necessary to start?

Regards,

Christian

[Benny · Accepted solution]

Hi,

>

> Some of the important questions are:

> 1- Is it possible to define own tables within the

> platform? (Certainly yes - namespaces? How? What are

> the requirements?)

Namespaces are signed with a two letter space in front of your table. You can either reserve space worldwide or use the Z-spcae that is for customer systems.

> 2- What requirements are existing for the use of

> external Web Services in the NetWeaver SOA

> (Contracts, rights,...)? What changes are probably

> necessary?

There is a couple of standards we support on this, but I'm not the specialist on this. Please sse our documentation on services at help.sap.com.

> 3- Is it possible, that Web Dynpros have direct

> access to (our) specific database tables? (How is the

> data access managed?)

Yes it is. But you have to program this. Ther eis no two tier direct-table-access-support from WD. You can write a JavaBean as model or use EJB's and import them as services.

> 4- Which Software and licenses from SAP are necessary

> to start?

You need developer licenses. Please contact your sales rep for the details. For a start as software vendor you could download the preview and later this year buy the special licenses we prepare for ISV's.

Regards,

benny