Configuration Management in an SOA Environment

[article]

the integrations that have been put
in place to support an integrated software development environment.

One of the main aspects this has affected has been the baselines of artifacts that make up a releases because it needs to be done at several different levels but this be explained in much greater detail further articles.

The build system has become more complicated because like the baselines because the services has been in a number of different ways such as:

    • Single service

 

    • Multiple services

 

    • All services if there is a change in libraries

 

  • Services with dependencies

All this has is to be controlled and over the series articles this will be explained how this is carried out and at the same time how this is controlled so the services can be released to the different environments.

One of the particular problems that we are assessing at this early stage of the project is how services will be decommissioned from the production environment. The real challenge has been to make people understand we will be running multiple services of the same name at the same time. The decommissioning of the service is unlike application software because you can't up remove the software, as you normally would use application software. This will be explained in later articles and in detail on the approach that has been taken to resolve the major issue.

Many of the support applications such as Remedy that have been designed over the years and support the company very well over the years. However, with the introduction of SOA this has required a re think on tools like Remedy, this is because the tool needs to be redesigned to support the SOA service. However this has to be done without breaking the
entire setup, this is mainly due to the cost involved in carrying out this work.

One thing I haven't mentioned yet is the choice of Configuration Management we have chosen to support this type of development and the reasons for this choice we be explained later in further articles. Further articles will explain how the Configuration management tool has been setup so we not only baseline software but the documentation as well.

As you can see the introduction of SOA has many challenges, which need to resolve, and the series of articles looks at the practical problems and solutions that I have come up to overcome these problems. Hopefully this will give an insight in how the SOA area needs to be addressed in terms of Configuration Management.

Alan Rogers has been working as a Configuration Manager for the last 13 years and been in the IT industry for 17. He has worked on many projects both designing the Configuration Management infrastructure as well implementing it for many large companies for particular projects. A lot of these processes and standards that he developed for the project have in many cases been adopted as corporate standards. Alan has an MBA from Henley Management College and is also a chartered Manager holding a MCIM.

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Sep 24
Oct 12
Nov 09
Nov 09