Publishing Static application provider architecture

Post Reply
F3lisFera
Posts: 3
Joined: 05 Dec 2010, 23:07

I have a Static_application_provider_architecture with about 40 outgoing interfaces (depends on). When the repository is published this architecture is not able to be rendered in the "application dependencies" unless I manually layout the architecture to compress the layout size. This manual layout is a cumbersome activity. I also understand that if I move to a multi user platform then manual layout is not possible.


Whilst it would be nice to see the architecture layout. It is not essential and I am happy to just have the hyperlinks for "sends data to" "receives data from". Any suggestions for
1/ Ability to render large architecture automatically and publish.
2/ Ability to set up application relationships without an architecture displayed?


Thanks for any advise.

Regards
Jason
You do not have the required permissions to view the files attached to this post.
F3lisFera
Posts: 3
Joined: 05 Dec 2010, 23:07

Just to clarify the prior post. The errror message in tomcat is below.
You do not have the required permissions to view the files attached to this post.
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Jason,

I'll start with the last post first!
I've seen that error message in Tomcat but can you confirm that the architecture image is still available in the Viewer even though Tomcat is reporting this error? I believe that's what I have experienced.

I'm assuming that since you're still seeing the very large image in the View that you are getting the image in spite of the error.

Currently, there is no explicit option to hide these images and just list the URLs. However, given your scenario, you can make a simple modification to the 'core_app_def.xsl' View to prevent the architecture being displayed.

At about line 216 in 'core_app_def.xsl' comment out the full <xsl:if> statement as follows. Save the XSL file and the image will not be rendered.

Code: Select all

<!-- Application Dependencies -->
			<div class="reportComponentFullWidth">
				<p class="mappingYWhite"><img src="images/application_dependencies.gif" alt="Application Dependencies" width="30" height="34"/> Application Dependencies</p>
				<!-- 24.11.2009 JWC - Add the static application architecture image -->
				<xsl:variable name="appStaticArch" select="pro:own_slot_value[pro:slot_reference='ap_static_architecture']/pro:value"></xsl:variable>
			 	
<!-- COMMENT THIS OUT TO PREVENT ARCHITECTURE IMAGE
				<xsl:if test="count($appStaticArch) > 0">
					<xsl:apply-templates select="/node()/pro:simple_instance[pro:name=$appStaticArch]" mode="RenderArchitectureImage"></xsl:apply-templates>
				</xsl:if>
				-->

				<div class="reportDetails">
				<table width="100%">
Perhaps this is something that we should make an option on the View?

Hope this helps

Jonathan
Essential Project Team
F3lisFera
Posts: 3
Joined: 05 Dec 2010, 23:07

Thanks Jonathan.

The image that I was getting was the 'last successfull image" as opposed to the most recently published image. I have since gone to the path \essential_viewer\graph_images and cleared the directory. Followed by publishing the repository from essential. This results in a reference being placed to the image name. The image itself fails to render.

What I have done from there is generate a .png file by using a visio diagram. I called this .png file the same name as the expected architecture diagram and save it in the /graph_images path. This has allowed me to view the formatted visio diagram from within the essential viewer.

Slightly circuitious path but it has the benefit of being able to take advantage of historical architectural artefacts.


Regards
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Thanks for the update.

That's a very interesting approach - the Visio diagram named for the instance. I think there's some potential in that - with improved support from the tools.

Jonathan
Essential Project Team
Post Reply