GUI update - moving Admin guide wilfly staff to a single branch - part 2

docs/adminguide/sources-asciidoc/src/main/asciidoc/Chapter-Managing.adoc

@@ -22,12 +22,6 @@ include::Section-Managing-Server-Settings.adoc[]
 
 :leveloffset: +1
 
-include::Section-Managing-Server-Settings-wildfly.adoc[]
-
-:leveloffset: -1
-
-:leveloffset: +1
-
 include::Section-Managing-SMPP-Server-Settings.adoc[]
 
 :leveloffset: -1
@@ -70,12 +64,6 @@ include::Section-Managing-DB-Routing-Settings.adoc[]
 
 :leveloffset: +1
 
-include::Section-Managing-DB-Routing-Settings-wildfly.adoc[]
-
-:leveloffset: -1
-
-:leveloffset: +1
-
 include::Section-Managing-mproc-rules.adoc[]
 
 :leveloffset: -1

docs/adminguide/sources-asciidoc/src/main/asciidoc/Section-Managing-DB-Routing-Settings.adoc

@@ -1,6 +1,6 @@
 
 [[_db_routing_rule_settings]]
-= Database Routing Rules (JBOSS 5)
+= Database Routing Rules
 
 {this-platform} {this-application} can now act as a SMPP Server accepting incoming SMPP connections or can also act as a SMPP client initiating a connection to a remote SMSC server.
 Therefore you can now set an intelligent database routing rule to route SMS between SMPP connections or between SMPP, SIP and GSM. 
@@ -17,11 +17,25 @@ The destined number of SMS is checked with address range. {this-platform} {this-
 
 The above methodology can work if the routing rule is based on MSISDN range, however if the range is not fixed (like in case of Number Portability) the above process will break.
 In such cases you can define a Database routing rule.
+
+.Procedure of Database routing rule configuring for JBOSS 5
 You must change the value of the property `smsRoutingRuleClass` in the file [path]_{this-folder}-smscgateway-<version>/jboss-5.1.0.GA/server/default/deploy/{this-folder}-smsc-server/META-INF/jboss-beans.xml_ to look like below and un-comment if its commented out: 
 ----
 
 <property name="smsRoutingRuleClass">org.mobicents.smsc.smpp.DatabaseSmsRoutingRule</property>
 ----
+
+.Procedure of Database routing rule configuring for Wildfly 10
+You must change the definifion of a mbean definition `mbean name="SmscManagement"` by adding of an extra property `smsRoutingRuleClass`
+ in the file [path]_{this-folder}-smscgateway-<version>/wildfly-10.1.0.Final/standalone/configuration/standalone.xml_ to look like below: 
+----
+<mbean name="SmscManagement" type="SmscManagement">
+    <property name="MProcRuleFactories" type="String" value="org.mobicents.smsc.mproc.impl.MProcRuleFactoryDefault"/>
+    <property name="smsRoutingRuleClass" type="String" value="org.mobicents.smsc.domain.DatabaseSmsRoutingRule"/>
+</mbean>
+----
+
+
 SMSC stores the routing rule in the Cassandra Database.
 You can populate this table with address and corresponding cluster name as explained in the sections below. 
 

docs/adminguide/sources-asciidoc/src/main/asciidoc/Section-Managing-Server-Settings.adoc

@@ -1,5 +1,5 @@
 
-= SMSC Gateway Server Settings (JBOSS 5)
+= SMSC Gateway Server Settings
 
 [[_smsc_gateway_server_properties]]
 == SMSC Server Properties
@@ -812,7 +812,7 @@ DESCRIPTION
         this command in CLI will set the SSN value but you must ensure that the SSN number
         is properly configured in the TCAP Stack in the xml descriptor file
         "mobicents-smscgateway-version/jboss-5.1.0.GA/server/default/deploy/
-        mobicents-smsc-server/META-INF/jboss-beans.xml".
+        mobicents-smsc-server/META-INF/jboss-beans.xml" for JBOSS 5 server and "mobicents-smscgateway-version/wildfly-10.1.0.Final/standalone/configuration/standalone.xml" for Wildfly 10 server.
 ----
 
 [[_set_scssn_gui]]
@@ -2334,7 +2334,7 @@ For home routing mode we may need to fill a special table for correlation betwee
 CorrelationId value will be returned as IMSI in SRI response to an upper SMSC GW.
 As an extra field "smsc" field can be specified for each entry of this table.
 If this field is specified and not empty then this value will be returned as a LocationInfo in SRI response to an upper SMSC GW, else SMSC GW address will be returned.
-Correlation table is stored into "jboss-5.1.0.GA/server/<server instanse, for example 'default'>"/data" and has name "SmscManagement_cc_mccmnc.xml". The content of this should follow the following template:
+Correlation table is stored into "jboss-5.1.0.GA/server/<profile>"/data" for JBOSS 5 server and "wildfly-10.1.0.Final/standalone/data" for Wildfly 10 server and has name `SmscManagement_cc_mccmnc.xml`. The content of this should follow the following template:
 
 
 ----