diff -r 177e5db417f9 j2eeserver/arch.xml
--- a/j2eeserver/arch.xml	Wed Apr 14 18:11:50 2010 +0400
+++ b/j2eeserver/arch.xml	Mon Apr 19 14:24:52 2010 +0400
@@ -71,9 +71,10 @@
 <answer id="arch-overall">
 
 <p>
-    There are two separate api/spi sets in j2eeserver. The devmodules
+    There are three separate api/spi sets in j2eeserver. The devmodules
     api/spi is for j2ee development modules (web, j2ee app, etc). The
-    plugins api/spi is for server plugins.
+    plugins api/spi is for server plugins. The profiler api/spi is for
+    profiler J2EE integration plugins.
 </p>
 
 <api name="J2EEServer-devmodules" type="export" category="friend" group="java">
@@ -92,6 +93,11 @@
   </ul>
 </api>
     
+<api name="J2EEProfilerAPI" type="export" category="friend" group="java">
+	J2EE Profiler api/spi is an intergation bridge between J2EE servers registered in IDE 
+	and pluggable profiling capability .
+</api>
+
 <api type="export" group="layer" name="PluginRegistration" category="friend" url="@TOP@/org/netbeans/modules/j2ee/deployment/plugins/api/doc-files/plugin-layer-file.html">
     XML layer contract for registration of server plugins and instances that implement 
     optional capabilities of server plugins.  Plugins with
@@ -327,6 +333,77 @@
     </p>
 </usecase>
 
+<usecase id="j2ee-profiler-api" name="J2EE Profiler Plugin">
+	J2EE application profiling capability could be integrated in to IDE.
+	In order to do this plugin needs to implement interface <a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerProvider.html">
+	ProfilerProvider</a> and register it as ProfilerProvider service in default lookup.
+	It is important to note that J2EE profiler plugin doesn't provide profiling functionality.
+	This plugin just manages J2EE server registered in IDE for profiling purpose.
+	It allows to start/stop J2EE server instance and tracks its state.
+	There are should be also functionality which allows to <b>profile</b>. But this is not covered here.
+	This functionality is separate module.
+</usacese>
+
+<usecase id="profiler-distinguish" name="J2EE Profiler Plugin Identifier">
+	IDE could have several Profiler providers registered. In order to distinguish them based on some id there is 
+	<a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/api/ProfilerRegistry.html">ProfilerRegistry</a> class.
+	Method <code>getId()</code> allows to get identifier for profiler provider implementation which could be used
+	for passing futher by client ( into Ant task f.e. ). It allows to request proiling via chosen profiler.
+	Method <code>getProvider()</code> should be used on J2EE server instance side to access chosen J2EE profiler.
+</usacese>
+
+<usecase id="profiler-start" name="Start J2EE server in profiling mode">
+	There are two ways to start J2EE server in profiling mode:
+	<ul>
+		<li>Ant task <code>nbstartprofiledserver</code> </li>
+		<li>"Start in Profile Mode" action for J2EE server instance ( currently this is AWT Action)</li>
+	</ul>
+	The first one uses ant task properties configured based on project. 
+	<a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/api/ProfilerServerSettings.html">ProfilerServerSettings</a> class is instantiated 
+	based on this properties . 
+	Method "getDefaultServerSettings()" is used in case of starting J2EE server in profile mode without original project properties 
+	( case when server is started via AWT Action ).
+	<a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerSession.html">ProfilerSession</a> created by
+	<a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerProvider.html">ProfilerProvider</a>  is used for managing
+	profiling of J2EE server instance.
+
+	Profiler provider could support singleton/several simultaneous sessions . In order to handle this situation there is a method
+	<code>canConfigure()</code>. User will be asked to stop profiling sessions in case of requested session can't be configured 
+	to start till <code>canConfigure</code> return <code>true</code>.
+
+	New session start could require to modify java arguments in 
+	<a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/api/ProfilerServerSettings.html">ProfilerServerSettings</a> 
+	( f.e. network port change , etc. ). This can be done via method <code>configureSession()</code>.
+
+	When session is configured for starting class <a href="@TOP@/org/netbeans/modules/j2ee/deployment/plugins/spi/StartServer">StartServer</a>
+	is used for starting J2EE server in profiling mode. Each J2EE server plugin is responsible for implementing 
+	profiling functionality implementing.
+</usacese>
+
+<usecase id="state-tracking" name="J2EE server state tracking">
+	There is a need to track state of J2EE server instance .
+	In order to do this <a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerSession.html">ProfilerSession</a> has
+	ability to register listeners.
+</usacese>
+
+<usecase id="stop-profiling" name="J2EE server stop">
+	There are two ways to stop profiling J2EE server:
+	<ul>
+		<li>"Stop" action for J2EE server ( currently AWT Action )</li>
+		<li>Stop profling with stop profiled application option ( currently this is Stop Profile Button )</code>
+	</ul>
+
+	The first one is controlled by J2EE server instance class which has a knowledge about profiling session . There is a session method
+	<code>requestStop()</code>. Implementation of this method is responsible for notifying listeners with <code>STATE_STOPPING</code>
+	profiling state change. Also it can provide some additional clean up code for profiling stop.
+
+	Other way to stop : Profiler stop with profiled application option .  In this case ProfilerSession implelentation should notify 
+	its listeners about state change.
+
+	So in both cases ProfilerSession listeners will be notified by <code>STATE_STOPPING</code> state .
+	J2EE server instance class is registered as ProfilerSession listener . So it is able to stop server carefully .
+</usacese>
+
 </answer>
 <!--         
         <question id="arch-time" when="init">
@@ -751,6 +828,8 @@
 <answer id="lookup-lookup">
 Folder lookup is used to read the definition of plugin (the additional optional 
 functionality registered by the plugin).
+<br/>
+Default lookup is used for access to profiler provider classes.
 </answer>
 <!--
         <question id="lookup-register" when="final" >
@@ -1152,7 +1231,12 @@
 -->
  <answer id="compat-deprecation">
   <p>
-   No change to existing APIs.
+	  Class <a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/api/ProfilerSupport.html">ProfilerSupport</a> is deprecated.
+	  It has not been required from very beggining. It is just container for constants which are now are moved into 
+	  <a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerSession.html">ProfilerSession</a>. It's single static 
+	  method is just duplication of method in 
+	  <a href="@TOP@/org/netbeans/modules/j2ee/deployment/profiler/spi/ProfilerSession.html">ProfilerSession</a>.
+	  Mentioned method has ambiguity becuase of current profiler privider concept ( there is no singleton provider and session ).
   </p>
  </answer>