Show TOC

Creating Composite Application Development ComponentsLocate this document in the navigation structure

Use

All packages, services, and objects are grouped into development components (DC). You can create new composite application DCs which represent your application.

Prerequisites

You have opened the Service Composer perspective.

Procedure
  1. Choose Start of the navigation path File Next navigation step New Next navigation step Composite Application Development Component End of the navigation path.
  2. Select the software component in which you want to create the new DC. Choose Next.
  3. Complete the required data as follows:
    Field Description

    Vendor

    Enter the name of the component vendor. Default value: sap.com

    Name

    Enter the name of the DC. Use lowercase only. You may use more than one component name by separating the names with a slash.

    Note

    Enter a component name shorter than 9 characters.

    Caption

    Enter a single line caption.

    Language

    Choose the language. Default value: American English

    Domain

    Choose the domain. Default value: Basis

    Support Comment

    This is used only when the value in the Vendor field is sap.com . Enter a CSN component name.

    Tip

    CAF- SOL

    BC-DWB-JAV-CAF

  4. We recommend that you specify a unique table name prefix for your application. To do that choose the link To avoid table name collisions, set the default prefix here. Choose Next.
  5. Choose Finish.

    The application you have created is added to the Composite Application Explorer.

    Note

    We recommend that you do not rename a CAF DC. Note that if you want to rename the CAF DC anyway, for example using a DC tool, you should follow the procedure below:

    1. Rename all the five DCs of CAF, so that their name pattern remains the same:
      • <new_name>/dictionary
      • <new_name>/ear
      • <new_name>/ejbmodule
      • <new_name>/metadata
      • <new_name>/permissions
        1. In the Navigator  view, choose the ca_model.cafmm  file in the /metadata project (it is in the /src/MMR directory) in the CAF application you want to rename.
        2. Find and replace all occurrences of the original application name with the new  application name.
        3. Build the following string:<reversed_orig_vendor_name>.<orig_appl_name> and replace all of its occurrences with the string < reversed_new_vendor_name>.<new_appl_name>. <reversed_orig_vendor_name> is the same as <reversed_new_vendor_name> in case you have not changed the vendor name of the DCs.
        4. If you have changed the vendor name, you need to do the following in addition:
          • Find and replace all occurrences of the original application name with the new  application name.
          • Search for the string: namespace=http://www.sap.com/caf/<orig_vendor_name> . Find and replace all occurrences of this namespace string with http://www.sap.com/caf/<new_vendor_name> .
          • Search for the string: namespace=http://www.sap.com/caf/<orig_vendor_name> . Find and replace all occurrences of this namespace string with http://www.sap.com/caf/<new_vendor_name> .
            1. Save and generate the application whose name you have changed.
  6. Optional: You can use the business object nodes, application services, and data types of reused projects you have added to define the structure of your application services and business objects. To reuse another application, do the following:
    1. Open theReused Projects tab page of your application.
    2. Choose Add and select the project you want to use in your application.
    3. Choose Finish.
      Caution

      You cannot create an association from a business object node in your application to a business object node in the reused application.

      You cannot create an attribute in your structure that references a structure in the reused application in the following cases:

      • your structure is a main structure of a business object node
      • your structure  is referenced directly or indirectly by a main structure of a business object node
      Note A CAF application can reuse several other CAF applications and they can reuse other applications, as well. Thereby, you can use application services and data types from all directly and indirectly reused applications from the first application. In order to generate the necessary classes and other artifacts for the application, CAF needs the definitions of data types and application services. Therefore the wsdl and xsd documents from directly and indirectly reused applications are copied into the folder structure of the reusing application project. When there are a lot of reusing levels, this folder structure may become quite large. These files are necessary only during generation. You can delete them after this process finishes by choosing the checkbox After generation remove files from reused applications from Composite Application Framework preference page. You can find this page by navigating to Start of the navigation path Window Next navigation step Preference Next navigation step Preferences Next navigation step Composite Application Framework End of the navigation path. Please, note that if your application is developed in team-oriented environment, the folder structure may become so deep that the files cannot be added to Design Time Repository (DTR).
  7. To reuse an existing project that you have created with an older version of the SAP NetWeaver Developer Studio, you need to create projects that use the old connectivity. In these projects, you can reuse old projects. From the menu path, choose Start of the navigation path Window Next navigation step Preferences Next navigation step Composite Application Framework End of the navigation path and mark the Create CAF projects with dynamic connectivity (SAP Note 1000104387)checkbox.

    If you have already enabled this option, the next time you create a project, a warning appears that the new project uses old connectivity.

    Note that you cannot reuse projects that have been created with the new connectivity version in projects that are created with the deprecated connectivity version, and vice versa.

Result