Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
waynesmith
Product and Topic Expert
Product and Topic Expert
449
SAP SMP 3.0 Creating a MBO from an SAP Adaptive Server Enterprise.

Purpose

This technical document explains how to create a Mobile Business Object from an SAP Adaptive Server Enterprise. If customer have an evirement that already has an ASE they can take advantage
of the ASE and use it with a SAP mobile solution to provide there uses with a moblie applicaion
solution with minimum investment.
Required Software

  • SUP 3.0 SDK or higher.

  • SAP ASE 15.0

  • Pubs2 database installed.

  • ASE sa rights


Assumption




  • This document assumes you have a working SUP environment.

  • You need to have access to Adaptive Server.

  • You need to have pubs2 database installed.


Step 1 – connecting to Adaptive Server Enterprise


User needs to connect and consume data from Adaptive Server.


Solution


In order to connect to ASE you need to create a connection in SUP Workspace.




  1. Start the SUP Workplace.

  2. Go to the Enterprise Explorer.

  3. Right Click on Database Connection.

  4. Select NEW.



Figure 1.

5. From the Connection Profile Type: select Sybase ASE.
6. Under Name: Add the name you would like to use for the connection object.


Figure 2.

7. Click Next.


Figure 3.

NOTE: The SMP server does not allow blank passwords if the ASE has a blank
it will fail you have to add a password for security.

8. Add your hose name or TCP/IP Address.
9. Add the Port number the ASE is listening on.
10. Add the default database name that you are using.
11. Add your User name.
12. Add your Password NULL password is not supported.
13. Optional place a check in save password
14. Click on the Test Connection Button.


Figure 4.

This concludes the setting up the connection for the Adaptive Server Enterprise.


Step 2 – Creating A MBO:


User needs to create a MBO from Adaptive Server Enterprise.


Solution


In order to do that, you will need to do the following steps.


15. Start or open the SUP Workspace.
16. Go to the Enterprise Explorer.
17. Right click on Database Connections and select from the menu Connect.
18. Go to the folder Mobile Servers tree open and connect to the SUP Server.


Figure 5.

19. Go to the top left menu File and select New -> Mobile Application Project.
20. Add your Project name: SAPASE
21. Go to your Adaptive Server connection.
22. Tree open Databases then pubs2 and Table
23. Highlight the table authors tables
24. Click on authors and drag and drop on to Application Diagram


Figure 6.

25. Go to Attributes and add Primary Key for au_id.
26. Save Project.
27. orkspace Navigator Right click on your project
28. the popup menu select deploy
29. Follow the prompts and click OK.


Figure 7.

This Concludes creating the MBO from the SAP Adaptive Server Enterprise.


Step 3 –Viewing and checking the MBO Deployment from SCC:


Checking the status of the MBO in the SUP Server.

Solution


In order to get an idea of how the deployment works we can check in SCC.


30. First start the Sybase Control Center.
31. Login using supAdmin or an account assigned to you.
32. Go to Domain.
33. Tree open default.
34. Tree open packages.
35. Tree Open sapase:1.0.


Figure 8.

You will see the authors table this means we are now binding the table in SUP to Adaptive server.

This concludes the creation and deploying the Mobile Business Object to the SUP server.


Summary


This document explained in details about the steps needed to create a connection to the SAP Adaptive Server Enterprise. Create the Mobile Business Object and deploy to the SUP Server. Confirming the deployment of the MBO to the SUP server thru Sybase Control Center.
If customer need a soultion for Mobility and are already using an ASE they can simply take advantage and create Mobile application with out the addtional cost of purching new database
platform. It is cost affective using what you already have.