Skip to Content

 
I love track based development in the NWDI.

            I hate track based development in the NWDI.

                     Unfortunately both the statements are true.

I plan to write few blogs on practical difficulties in Track based development in the Java Stack. My objective is not to criticize but to inform SDN colleagues about possible problem areas which can be better managed in their projects. 

In this first blog I will discuss Development Component Type – Dictionary.

You can create Simple Data Types, Structures and Database Tables using Dictionary DC. These are reusable and can be used in any other DC project. The first problem is related to Database tables. 

In track based development the process for creating and deploying  dictionary DC’s are listed below.

  1. From development configurations perspective, Create DC of type dictionary.
  2. All resources created will be assigned to an activity
  3. Create Database Table in this DC.
  4. Checkin the Activity and Activate
  5. TheTable will now be created in the Development Server configured in the track.
  6. Release the activity and import the activity in consolidation server configured in the track
  7. Assemble and approve for moving the  table to production  landscape 

Till now things go pretty smooth. I’ve not seen such a smooth transport of development anywhere else (Apart from ABAP).

The problem comes when you want to change the table definition which you have created.  CMS/SDM (in Release 6.30/6.40) doesnt supports changing (Drop columns/Change Column Width…)  Tables in a Dictionary DC and transporting the change through the landscape. Its planned for future releases. This is really a bottleneck for the Java Development Infrastructure. The problem is further complicated by the fact that there is not sufficient documentation about this restriction.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Former Member
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 

Leave a Reply