NWDI Track Configuration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Synchronize SC Dependencies in

the Track Related to Portal

Applications

Applies to:

NW04, NW04S.

Summary

This document provides important information to track inconsistency state and resolve it by synchronizing dependencies of software components in track with SLD based on the definition of software components.

Author: Koti Reddy Chimalamarri

Company: IBM India Private Limited

Created on: 10 June 2011

Author Bio

Koti Reddy Chimalamarri is SAP Portal Consultant with 5+ years of experience who is currently working with IBM India Private Limited.


© 2010 SAP AG 2

Table of Contents

1. Purpose........................................................................................................................................................... 2

2. Assumptions: .................................................................................................................................................. 3

3. Check Inconsistencies of tracks related to portal applications ...................................................................... 3

4. Synchronize SC Dependencies of tracks related to portal applications ......................................................... 7

Related Content ................................................................................................................................................ 11

Disclaimer and Liability Notice .......................................................................................................................... 12

1. Purpose

This document provides important information to track inconsistency state and resolve it by synchronizing dependencies of software components in track with SLD based on the definition of software components.


© 2010 SAP AG 3

2. Assumptions:

2.1 Portal developers use NWDI environment with NWDS to develop portal applications

2.2 User with NWDI.Administrator Role for doing these changes.

2.3 Screenshots were taken from NWDI 7.0 for these Article .Other versions also contain almost similar navigation.

3. Check Inconsistencies of tracks related to portal applications

3.1 Open NWDI URL as shown below similar to http://<host>:<port>/devinf/main and choose Change Management Service

It will navigate to you page as shown below.


© 2010 SAP AG 4

Choose Landscape Configure to see the details of tracks.


© 2010 SAP AG 5

Observe the Inconsistencies of the Track by checking the software component’s state column as shown below.

Green Color Indicates SC dependencies are synchronized with SLD and the dependency definitions of a software component are the same in both SLD and CMS; no other action is required.

Yellow Color Indicates SC dependencies are different but accepted by synchronization and the dependency definitions of a software component in SLD are not the same as in CMS. During synchronization of the differences, the dependency definition in CMS was accepted.

Red Color Indicates SC dependencies are different between SLD and CMS – synchronize the SC dependencies and accept the valid definition and the dependency definitions of a software component in SLD are not the same as in CMS. Synchronize the dependency definitions with Synchronize SC Dependencies and define which dependency definition is valid for the track.


© 2010 SAP AG 6

Grey Color Indicates SC dependencies are not synchronized and the dependency definitions have not been synchronized with each other. To do this, choose Synchronize SC Dependencies.

Software Component state is generally determined by comparing software component dependencies in the CMS Track as shown below with dependencies defined for software component in SLD for Build Time Context only.


© 2010 SAP AG 7

Compare the above CMS Track software component dependencies as shown above with dependencies in SLD as shown below

If both are same, then only green status will come.

4. Synchronize SC Dependencies of tracks related to portal applications

To resolve inconsistencies of track, change the dependency definitions of software component manually and update the data in CMS. To do this, choose Update CMS as shown below.


© 2010 SAP AG 8

Use the Synchronize SC Dependencies function to display the differences in the dependencies between SLD and CMS, and to decide which dependency definition is valid for the track.


© 2010 SAP AG 9

It shows all the software components to compare SC definitions in CMS and SLD as shown below.

It provides option as below to check software components out of sync with SLD as shown below.

By choosing Show Software components out of sync with SLD, you can restrict the display so that only software components with different dependency definitions are shown.


© 2010 SAP AG 10

Expand the software components that you want to synchronize. For each software component, you can see the dependencies as defined in SLD and CMS.

By Selecting the Software component, decide with below three options which one is needed to resolve inconsistency. Ideal case should be Accept SLD definition.

Accept CMS Definition: Accepts the dependency definition as defined in the CMS track.

Accept SLD Definition: Accepts the dependency definition as defined in the SLD track.

Accept Integration: Accepts the dependency definitions that are selected in the Integrate into CMS Definition column and adds them to the existing CMS definition in the track.

The dependency definitions are applied in the track definitions for all selected software components.

Now save the track which resolve inconsistencies.


© 2010 SAP AG 11

Related Content

Software Components

Resolving Inconsistencies

Consistency Checks for Tracks

http://help.sap.com/saphelp_nw70/helpdata/en/79/69f9e32bbb9f41aa4043c4c4989a41/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/4f/feda41cabae23ee10000000a155106/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/5a/1cc941d7565f24e10000000a1550b0/content.htm


© 2010 SAP AG 12

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

NWDI Track Configuration

Documents

track inconsistency

synchronize

accept sld

sc dependencies

software component

software components

dependency

portal applications