Mar

4

Create a MOSS LobSystem with SAP Netweaver Web Services

Filed Under Development

Before creating a LobSystem, you will need to first expose your BAPIs as Web Services.

Your MOSS environment will need to be on a domain in order to use Microsoft Single-Signon. If it is not on a domain then you will have to provide a custom SSO Provider implementation.

I used the Flight BAPIs that come with the trial version of SAP Netweaver. The service interfaces for these BAPIs are exposed by default.

Your LobSystemInstance need to have the following Properties set:

Be sure to have WebServiceSsoApplicationId and WebServiceAuthenticationMode since it is Web Services that the BDC will be accessing and not a database. Also, do not use WindowsCredentials as the value of the WebServiceAuthenticationMode. The SAP services are not secured by Windows Credentials.

Now login to your MOSS environment.

  1. On the OS, ensure that the “Microsoft Single Sign-on Service” is running under a domain account that has access to create\modify the a database on a DB server. The server does not have to be your MOSS SQL Server.
  2. Fire up the MOSS Central Administration site and go to Manage Single Sign-On (Operations > Manage Single Sign-On)
  3. Click “Manage server settings”
    1. For the Enterprise Application Definition Administrator Account name, specify the domain group or user, that will manage the Single-Sign on service.
    2. For the Single Sign-on Administrator Account name, specify the domain group or user, that will manage the application definitions and accounts for those definitions. (For testing purposes I kept these two the same)
    3. Specify the name of the SQL Server that the SSO database will reside on. Make sure that the account group or user that you specified above has the appropriate access to the SQL Server.
    4. Keep the name of the database the default, SSO and click Ok.
    5. If everything goes fine then the Single-Signon Service will create the SSO DB on the SQL Server you specified. Any errors that you may receive at this point will be due to the lack of access on the group\user you specified or the Single-Signon Service is not running or not running under the appropriate account.
  4. Click, “Manage settings for enterprise application definitions”
    1. Provide a display name for the Application.
    2. The Application Name needs to be the same value as the property “WebServiceSsoApplicationId” in your LobSystemInstance.
    3. I recommend setting the Account Type to Group. It will allow all users that belong to the group to use this SSO application definition.
    4. DO NOT check Windows authentication. This only works if your LobSystemInstance is set to use Windows Credentials.
    5. Leave the Fields as is.
  5. Click, “Manage account information for enterprise application definitions”
    1. Select the Application definition that you just created.
    2. For the Group account name, specify the domain group that has access to use this SSO application definition.
    3. Click the “Set” button”
    4. Specify the user name and password, that has permissions to invoke the SAP Web Services.
    5. Click “Done”

That is it. You should be able to import your LOB System into the BDC. Make sure that your Business Data Web Parts are accessible to the domain group that you specified SSO application definition. Also, your BDC will need to include the same group in the BDC permissions set and grant them Execute access.

Comments

One Response to “Create a MOSS LobSystem with SAP Netweaver Web Services”

  1. lriwswirl on May 7th, 2008 11:17 pm

    Hi,
    You mentioned trial version of SAP Netweaver, may I know where can i get or download it for testing?

    Thanks.

Leave a Reply