Escolar Documentos
Profissional Documentos
Cultura Documentos
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
Author Bio
Koti Reddy Chimalamarri is SAP Portal Consultant with 5+ years of experience who is currently working with IBM India Private Limited.
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.
2. Assumptions:
2.1 2.2 Portal developers use NWDI environment with NWDS to develop portal applications 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.
Observe the Inconsistencies of the Track by checking the software components 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.
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.
Compare the above CMS Track software component dependencies as shown above with dependencies in SLD as shown below
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.
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.
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.
Related Content
Software Components Resolving Inconsistencies Consistency Checks for Tracks