A real architect building real buildings will spend most of his time researching the building code, liasing with planning auhorities and discussing costs with the investors.
So a solution architect will spend most of his or her time ensuring that the solution complies with the various security and development standards at the site, complies with the enterprise roadmaps etc, and discussing budgets etc. and liasing with other teams defining interfaces and synchroning plans.
A real architect seldom gets the chance to be Richard Rodgers and build a substantial building on a new site for a client with deep pockets, instead they design "cookie cutter" houses for speculative developers, add extensions to exisiting buidlings or remodel old buildings for new uses.
In the same way the IT architect will spend most of his or her profesional life enhancing or replacing parts of an existing system within a limited budget, a limited timeframe and be severly constrained by the existing technoligy.
So my advice is to get a grip on the various standards and procedures where you work and try to get a handle on the architectural process as it works and the jargon as it is used in your organisation. If you were any good as a programmer you already know all the technical stuff you need.
