Managing Relations

Use

This procedure contains the possible relation-focused tasks you can perform using the Composite Designer perspective. You can easily create proper relations between the development objects, which are either imported or newly created with the Composite Designer palette. While creating a new relation, you do not need to perform manual steps such as creating public parts and defining runtime dependencies between the affected development components in which these development objects are located. All these steps are done automatically by the Composite Designer following SAP's component model rules.

You can also display all relations that a specific development object has and troubleshoot incorrect relations.

Procedure

Creating Possible Relations Between Development Objects

Review the table of the possible relation types.

Referring Object	Referred Object	Relation Semantics
Process	CAF application service exposed as a Web service	Allows a BPM process to call operations provided by a CAF application service exposed as a Web service. The process uses the WSDL exposed by the CAF application service to become aware of the available operations. See Importing Service Interface Definitions .
Process	CAF business object exposed as a Web service	Allows a BPM process to call operations provided by a CAF business object exposed as a Web service. The process uses the WSDL exposed by the CAF business to become aware of the available operations. See Importing Service Interface Definitions .
Process	Web Dynpro	Allows a BPM process to use a Web Dynpro user interface (UI) as the UI is assigned to a specific task. See: Modeling Human Activities Working with Tasks Assigning a User Interface to a Task
Process	Visual Composer	Allows a human activity in a BPM process to have a task with a Visual Composer (VC) user interface (UI) component assigned to it. The VC UI component is assigned to a new task and the task is assigned to the selected human activity. See: Modeling Human Activities Working with Tasks Assigning a User Interface to a Task
Process	Session EJB exposed as a Web service	Allows a BPM process to use a Session EJB exposed as a Web service. See Importing Service Interface Definitions .
Process	Simplified service	Allows a BPM process to use a simplified service. See Importing Service Interface Definitions .
Process	Process	Allows a BPM process to use another BPM process. See Modeling Referenced Sub-Processes .
Task	Web Dynpro	Allows a BPM task to use a Web Dynpro user interface (UI) as the WD UI component is assigned to the task. See Assigning a User Interface to a Task .
Web Dynpro	CAF application service	Allows a Web Dynpro UI component to call operations provided by a CAF application service (BO). The Web Dynpro application imports the session EJB generated by the CAF application service as a Web Dynpro model. See Importing Enterprise JavaBean (EJB) Models .
Web Dynpro	CAF business object	Allows a Web Dynpro UI component to call operations provided by a CAF business object. The Web Dynpro application imports the session EJB generated by the CAF business object as a Web Dynpro model. For more information, see Importing Enterprise JavaBean (EJB) Models .
Web Dynpro	Session EJB	Allows a Web Dynpro UI component to call methods implemented in a session EJB. The Web Dynpro application imports the session EJB as a Web Dynpro model. See Importing Enterprise JavaBean (EJB) Models .
Web Dynpro	Composed service	Allows a Web Dynpro UI component to call methods implemented in a composed service.
Servlet	Session EJB	Allows a servlet to call methods implemented in a session EJB. In fact, this injects the session EJB in the source code of the servlet class. To create such a relation, proceed as follows: Use the Create Relation button of the servlet to join the servlet and the Session EJB. The Create Relation wizard lists the steps that you perform to create a relation. This page of the wizard appears only when you create a relation for the first time. In all other cases you have to choose Back to access this page. Choose Next . Select a business interface and choose Next . Specify a name of the bean injection. Specify on which level the injection is performed (field or method level). Choose Finish .
Servlet	Composed service	Allows a servlet to call methods implemented in a composed service.
JSP	Session EJB	Allows a JSP page to call methods implemented in a session EJB. This adds the Java code needed for looking up the bean's business interface to the body of the JSP page. To create such a relation, proceed as follows: Use the Create Relation button of the JSP to join the JSP and the Session EJB. The Create Relation wizard lists the steps that you perform to create a relation. This page of the wizard appears only when you create a relation for the first time. In all other cases you have to choose Back to access this page. Choose Next . Select a business interface and then choose Finish .
JSP	Composed service	Allows a JSP page to call methods implemented in a composed service.
Session EJB	Session EJB	Allows a session EJB (a referring one) to call methods implemented in the referred session EJB. In fact, this injects the referred session EJB in the source code of the referring one. To create such a relation, proceed as follows: Use the Create Relation button to join the two session beans. The Create Relation wizard lists the steps that you perform to create a relation between the beans. This page of the wizard appears only when you create a relation for the first time. In all other cases you have to choose Back to access this page. The number of the steps listed on this page depends on whether the beans are in the same DC or in different ones. Choose Next . Select a business interface and choose Next . Specify a name for the bean injection. This name refers to the name by which the bean is looked up in the environment. In the source code of the referring session EJB, this name appears as an attribute in the @EJB annotation. With the @EJB annotation you obtain a reference to the business interface of the referred session EJB. Specify on which level the injection is performed (field or method level). Choose Finish .
Session EJB	Composed service	Allows a session EJB to call a composed service.
Composed service	Session EJB	Allows the composed service operations to call methods in a session EJB. See Modeling the Service Flow .
Composed service	Web service	Allows the composed service operations to call operations in other Web services, represented by its WSDL. See Importing Web Services .
Composed service	RFC	Allows the composed service operations to call operations of the WSDL which has been created for the corresponding RFC. See Importing RFC Modules .
Composed service	CAF application service	Allows the composed service operations to call operations of a CAF application service. See Modeling the Service Flow .
Composed service	CAF business object	Allows the composed service operations to call operations of the CAF business objects. See Modeling the Service Flow .
Composed service	Composed service	Allows the composed service operations to call operations of another composed services. See Modeling the Service Flow .
CAF application service	CAF application service	Allows the CAF application service operations to call operations in another CAF application service. See Defining Application Service Dependencies .
CAF application service	CAF business object	Allows the CAF application service operations to call operations of a CAF business object. Modeling Service Operations .
CAF application service	Session EJB	Allows the CAF application service operations to call methods implemented in a session EJB. See Using External Services .
CAF application service	Composed service	Allows the CAF application service operations to call operations of a composed service. See Importing Web Services .
CAF application service	CAF external Web service	Allows the CAF application service operations to call operations of a CAF external Web service represented by a WSDL. See Importing Web Services .
CAF application service	CAF external RFC service	Allows the CAF application service operations to call operations of a CAF external RFC service represented by a WSDL. See Importing RFC Modules .
CAF business object	Session EJB	Allows the CAF business object operations to call methods implemented in a session EJB. See Using External Services .
CAF business object	CAF business object	Allows the CAF business object operations to call operations of another CAF business object. See Modeling Service Operations .
CAF business object	Composed service	Allows the CAF business object operations to call operations of a composed service. See Importing Web Services

From the Palette , select Create Relation then point to the first object, and drag the expanding connection indicator to the second object of the connection.

Note

You can also use the Create Relation speed button displayed on each development object to launch the wizard for relation creation. For most of the relation types you can review all technical steps that are performed automatically by the Composite Designer perspective when creating a new relation, by choosing the Details button.
Choose OK and follow the instructions of the wizard for the different types of relations.

Displaying and Troubleshooting Relations for a Specific Development Object

Using the Composite Designer you can view and troubleshoot the relations between development objects.

From the context menu of your product (that is the composite application), choose Open Composite Designer .
Once you have the development objects displayed in the layer structure, select the object whose available relations you want to display.
From the context menu of the selected object, choose Relations .

The corresponding relations are displayed in the Relations view.
If you have an error relation and you want to troubleshoot it, select the error relation.
From the context menu, choose Check Results .

The mappings between the selected objects are displayed with details. To review this information you can use the Mappings button or the Message Details button.

Troubleshooting Relations for a Product Globally

The relations check feature is now also available on global product level. To execute it, follow the steps below:

Select the corresponding product in the Composite Explorer view.
Use the secondary mouse button to open the context menu.
Select Check Relations .

The found errors are displayed in the Problems view.

Reviewing the Broken Relations with the Problems View

You can review the errors, no matter found globally or with an individual check as described in the two procedures above, in the Problems view. The displayed errors are shown along with the ones found by the Java EE compiler, and the Web Dynpro or the Business Process Management check functionality.

You are also able to filter and open this type of errors with the new error check framework functionality, displayed as Open the check results dialog , or you can use the option Start of the navigation path Show in Next navigation step Composite Designer End of the navigation path

Reviewing Additional Information About the Relations Types

Additionally in the following SAP Note 0001357187 Information published on SAP site you can also review the following information about the Composite Designer relation types:

relation types that you can (or cannot) create using the Composite Designer.
relation types that you can (or cannot) observe in the Relations view.
relation types that you can (or cannot) delete.
relation types that you can (or cannot) troubleshoot with the Check Results feature.

The relations that cannot be troubleshoot with the Check Results are displayed with a question mark (?).