JBoss.orgCommunity Documentation
Copyright © 2010 Red Hat, Inc.
Abstract
Mobicents JAIN SLEE Diameter CCA Resource Adaptor (RA) is the JAIN SLEE 1.1 RA for the Diameter Protocol Credit Control Application, used in Mobicents JAIN SLEE platform.
The RA implements the Resource Adaptor Type defined by Mobicents development teams.
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight key caps and key-combinations. For example:
To see the contents of the file
my_next_bestselling_novel
in your current working directory, enter thecat my_next_bestselling_novel
command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.
Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F1 to switch to the first virtual terminal. Press Ctrl+Alt+F7 to return to your X-Windows session.
The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in Mono-spaced Bold
. For example:
File-related classes include
filesystem
for file systems,file
for files, anddir
for directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
Choose Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
from the main menu bar to launchTo insert a special character into a gedit file, choose from the main menu bar. Next, choose from the Character Map menu bar, type the name of the character in the Search field and click . The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the button. Now switch back to your document and choose from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.
Note the
shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select from the sub-menu in the menu of the main menu bar' approach.
or Mono-spaced Bold Italic
Proportional Bold Italic
Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, type
ssh
at a shell prompt. If the remote machine isusername
@domain.name
example.com
and your username on that machine is john, typessh john@example.com
.The
mount -o remount
command remounts the named file system. For example, to remount thefile-system
/home
file system, the command ismount -o remount /home
.To see the version of a currently installed package, use the
rpm -q
command. It will return a result as follows:package
.
package-version-release
Note the words in bold italics above username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a server-pool. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called Multi-Processing Modules (MPMs). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server.
Two, commonly multi-line, data types are set off visually from the surrounding text.
Output sent to a terminal is set in Mono-spaced Roman
and presented thus:
books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in Mono-spaced Roman
but are presented and highlighted as follows:
package org.jboss.book.jca.ex1;
import javax.naming.InitialContext;
public class ExClient
{
public static void main(String args[])
throws Exception
{
InitialContext iniCtx = new InitialContext();
Object ref = iniCtx.lookup("EchoBean");
EchoHome home = (EchoHome) ref;
Echo echo = home.create();
System.out.println("Created Echo");
System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
}
}
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
A note is a tip or shortcut or alternative approach to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring Important boxes won't cause data loss but may cause irritation and frustration.
A Warning should not be ignored. Ignoring warnings will most likely cause data loss.
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in the the Issue Tracker, against the product Mobicents JAIN SLEE Diameter CCA Resource Adaptor, or contact the authors.
When submitting a bug report, be sure to mention the manual's identifier: JAIN_SLEE_DIAMETER_CCA_RA_User_Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
This resource adaptor provides DIAMETER API for JSLEE applications. CCA is a RFC specification of DIAMETER extension to allow real time credit control of end user services, ie. SIP services, equipment access, network access, ... etc.
Events represent DIAMETER CCA messages received by stack, that is requests and answers with command code equal to 272. Events are fired either on client or server activity.
The activities are custom defined by RA Type to ease use of RA. Activities represent DIAMETER session between two peers. SLEE applications use activities to create,send and receive messages.
Diameter CCA Resource Adaptor Type is defined by Mobicents team as part of effort to standarize RA Types.
Diameter CCA Type 2.4.2-SNAPSHOT defines two types of activities:
This type of activity represents client side of credit control session. It is a source of answers to credit control requests issued with this activity. It is also source of re-authentication requests.
This activity type can be created with call to one of methods of CreditControlProvider. It ends once underlying credit control session ends. State machine for client credit control can be found here and here .
This type of activity represents server side of credit control session. It is source of credit control requests issued from client side and answers to re-auth requests.
This activity type is created explicitly for incoming requests by Resource Adaptor. It ends once underlying credit control session ends. State machine for server credit control can be found here and here
Both activities define methods required to properly function and expose necessary information to JSLEE services. Common part for each is defined as follows:
public CreditControlSessionState getState();
public String getSessionId();
public CreditControlAVPFactory getCCAAvpFactory();
public CreditControlMessageFactory getCCAMessageFactory();
returns current state of credit control session. State directly follows definition from credit control rfc .
returns session Id of underlying diameter session.
returns AVP factory capable of creating specifc AVPs for credit control. It also exposes means of accessing base AVP factory.
returns message factory capable of creating credit control messages. It also exposes means of accessing base factory.
Client type activity interface is defined as follows:
CreditControlRequest createCreditControlRequest();
void sendCreditControlRequest(CreditControlRequest ccr) throws IOException;
void sendInitialCreditControlRequest(CreditControlRequest ccr) throws IOException;
void sendReAuthAnswer(ReAuthAnswer rar) throws IOException;
void sendUpdateCreditControlRequest(CreditControlRequest ccr) throws IOException;
void sendTerminationCreditControlRequest(CreditControlRequest ccr) throws IOException;
Creates credit control request for this activity. Fills AVPs appropriate for this session..
sends credit control request, does not perform any other operations.
sends credit control request. Ensures that its initial request by setting proper AVP .
sends credit control request. Ensures that its update request by setting proper AVP .
sends credit control request. Ensures that its termination request by setting proper AVP .
sends re-authentication answer on this session.
Server type activity interface is defined as follows:
CreditControlAnswer createCreditControlAnswer();
void sendCreditControlAnswer(CreditControlAnswer cca) throws IOException;
void sendReAuthRequest(ReAuthRequest rar) throws IOException;
creates credit control answer for last received request.
sends credit control answer through this session.
sends re-authentication request through this session.
It is safe to type cast activities to interface defined in Base RA Type: net.java.slee.resource.diameter.base.DiameterActivity
Credit Control declares only two additional events, to those defined in Base RA Type, namely CreditControlAnswer and CreditControlRequest. However, it also reuses Base events.
Table 2.1. Events received on Server Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.cca.events. CreditControlRequest | java.net | 0.8 | net.java.slee.resource. diameter.cca.events. CreditControlRequest |
net.java.slee.resource. diameter.base.events. ReAuthRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ReAuthRequest |
Table 2.2. Events received on Client Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java. slee.resource .diameter. cca.events. CreditControlAnswer | java.net | 0.8 | net.java. slee.resource .diameter .cca.events. CreditControlAnswer |
net.java. slee.resource .diameter. base.events. ReAuthAnswer | java.net | 0.8 | net.java. slee.resource .diameter .base.events. ReAuthAnswer |
Table 2.3. Events received on both activities
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. SessionTerminationRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. SessionTerminationRequest |
net.java.slee.resource. diameter.base.events. SessionTerminationAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. SessionTerminationAnswer |
net.java.slee.resource. diameter.base.events. AbortSessionRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AbortSessionRequest |
net.java.slee.resource. diameter.base.events. AbortSessionAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AbortSessionAnswer |
net.java.slee.resource. diameter.base.events. AccountingRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AccountingRequest |
net.java.slee.resource. diameter.base.events. AccountingAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AccountingAnswer |
net.java.slee.resource. diameter.base.events. ErrorAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ErrorAnswer |
net.java.slee.resource. diameter.base.events. ExtensionDiameterMessage | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ExtensionDiameterMessage |
Spaces where introduced in Name
and Class
column values, to correctly render the table. Please remove them when using copy/paste.
Activity context interface factory is defined as follows:
package net.java.slee.resource.diameter.cca;
import javax.slee.ActivityContextInterface;
public interface CreditControlActivityContextInterfaceFactory {
public ActivityContextInterface getActivityContextInterface(CreditControlClientSession cccs);
public ActivityContextInterface getActivityContextInterface(CreditControlServerSession ccss);
}
Resource Adaptor SBB Interface provides SBBs with means of accessing RA objects required for interaction in DIAMETER world. It is defined as follows:
package net.java.slee.resource.diameter.cca;
import net.java.slee.resource.diameter.base.CreateActivityException;
import net.java.slee.resource.diameter.base.events.avp.DiameterIdentity;
public interface CreditControlProvider {
CreditControlClientSession createClientSession() throws CreateActivityException;
CreditControlClientSession createClientSession(DiameterIdentity destinationHost,
DiameterIdentity destinationRealm) throws CreateActivityException;
CreditControlMessageFactory getCreditControlMessageFactory();
CreditControlAVPFactory getCreditControlAVPFactory();
int getPeerCount();
DiameterIdentity[] getConnectedPeers();
}
Creates new client session. Its destination is unknown, its determined on send.
Creates new client session. Its destination is passed upon creation.
Retrieve default message factory.
Retrieve default AVP factory.
Get number of currently connected peers. This may change during runtime, depends on network situation.
Get currently connected peers. This may change during runtime, depends on network situation.
Simple client side requesting credits, with EVENT_TYPE credit control request:
private void doSendEventCCR(int currencyCode,int value) {
try {
//Create session.
CreditControlClientSession session = this.provider.createClientSession();
ActivityContextInterface localACI = this.acif.getActivityContextInterface(session);
localACI.attach(this.getSbbContext().getSbbLocalObject());
CreditControlRequest request = session.createCreditControlRequest();
List<DiameterAvp> avps = new ArrayList<DiameterAvp>();
avps.add(avpFactory.getBaseFactory().createAvp(Avp.ORIGIN_HOST,
("aaa://" + originIP + ":" + originPort).getBytes()));
avps.add(avpFactory.getBaseFactory().createAvp(Avp.ORIGIN_REALM,
originRealm.getBytes()));
//or dedicated:
//request.setDestinationHost(destinationHost);
//request.setDestinationRealm(destinationRealm);
avps.add(avpFactory.getBaseFactory().createAvp(Avp.DESTINATION_HOST,
("aaa://" + destinationIP + ":" + destinationPort).getBytes()));
avps.add(avpFactory.getBaseFactory().createAvp(Avp.DESTINATION_REALM,
destinationRealm.getBytes()));
//Event Type request has request type set to '4'
avps.add(avpFactory.getBaseFactory().createAvp(
CreditControlAVPCodes.CC_Request_Type, 4l));
avps.add(avpFactory.getBaseFactory().createAvp(
CreditControlAVPCodes.CC_Request_Number, 0l));
RequestedServiceUnitAvp rsu = this.avpFactory.createRequestedServiceUnit();
CcMoneyAvp ccMoney = this.avpFactory.createCcMoney();
ccMoney.setCurrencyCode(currencyCode);
UnitValueAvp unitValue = this.avpFactory.createUnitValue();
unitValue.setValueDigits(value);
ccMoney.setUnitValue(unitValue);
rsu.setCreditControlMoneyAvp(ccMoney);
avps.add(rsu);
avps.add(avpFactory.getBaseFactory().createAvp(
CreditControlAVPCodes.Requested_Action, 0));
//use extension avps to fill message or dedicated setters/getters
request.setExtensionAvps(avps.toArray(new DiameterAvp[avps.size()]));
// Now create and send
if (logger.isInfoEnabled())
logger.info("About to send:\n" + request);
session.sendCreditControlRequest(request);
} catch (Exception e) {
logger.error("Failed to create/send Credit-Control-Request.", e);
}
}
....
public void onCreditControlAnswer(CreditControlAnswer answer, ActivityContextInterface aci) {
logger.info("Received CCA with Result-Code[" + answer.getResultCode() + "].");
switch (answer.getCcRequestType().getValue()) {
case 1:
case 2:
case 3:
logger.error("Received 'session' credit control answer. Expecting EVENT_TYPE answer");
break;
case 4:
//result code 2xxx is success
if(answer.getResultCode()/1000 == 2 )
{
//assume msg is correct
GrantedServiceUnitAvp gsu = answer.getGrantedServiceUnit();
CcMoneyAvp money = gsu.getCreditControlMoneyAvp();
doSpendMoney(money);
}else
{
//error, this will pring formated msg dump.
logger.warn("Result of CC operation is a failure:\n"+answer);
}
break;
}
}
Server application to handle simple direct debiting:
public void onCreditControlRequest(CreditControlRequest request,
ActivityContextInterface aci) {
if (logger.isInfoEnabled())
logger.info("Received Credit-Control-Request (Application-Id[" + request.getHeader().getApplicationId() + "].");
// INITIAL_REQUEST(1), UPDATE_REQUEST(2), TERMINATION_REQUEST(3),
// EVENT_REQUEST(4)
CreditControlServerSession session = (CreditControlServerSession) aci.getActivity();
CreditControlAnswer answer = null;
if(request.getRequestedAction() == RequestedActionType.DIRECT_DEBITING)
{
switch (request.getCcRequestType().getValue()) {
case 1:
try {
if (logger.isInfoEnabled())
logger.info("Got INITIAL_REQUEST(1).");
if (getSentInitialAnswer()) {
logger.error("Error. Initial answer already sent! Aborting.");
return;
}
answer = session.createCreditControlAnswer();
if(userHasCredit(request.getUserName(),request.getRequestedServiceUnit()))
{
GrantedServiceUnitAvp gsu = chargeUser(request.getRequestedServiceUnit());
answer.setGrantedServiceUnit(gsu);
answer.setResultCode(2001);
}else
{
//4012 == CREDIT_LIMIT_REACHED
answer.setResultCode(4012);
}
if (logger.isInfoEnabled()) {
logger.info("Processed Credit-Control-Request:\n" + request);
logger.info("Sending Credit-Control-Answer:\n" + answer);
}
session.sendCreditControlAnswer(answer);
this.setSentInitialAnswer(true);
} catch (Exception e) {
logger.error("Failed to create/send Credit-Control-Answer to reply INITIAL_REQUEST(1).", e);
}
break;
case 2:
try {
if (logger.isInfoEnabled())
logger.info("Got UPDATE_REQUEST(2).");
if (getSentUpdateAnswer()) {
logger.error("Error. Update answer already sent! Aborting.");
return;
}
answer = session.createCreditControlAnswer();
if(userHasCredit(request.getUserName(),request.getRequestedServiceUnit()))
{
GrantedServiceUnitAvp gsu = chargeUser(request.getRequestedServiceUnit());
answer.setGrantedServiceUnit(gsu);
answer.setResultCode(2001);
}else
{
//4012 == CREDIT_LIMIT_REACHED
answer.setResultCode(4012);
}
if (logger.isInfoEnabled()) {
logger.info("Processed Credit-Control-Request:\n" + request);
logger.info("Sending Credit-Control-Answer:\n" + answer);
}
session.sendCreditControlAnswer(answer);
setSentUpdateAnswer(true);
} catch (Exception e) {
logger.error("Failed to create/send Credit-Control-Answer to reply UPDATE_REQUEST(2).", e);
}
break;
case 3:
try {
if (logger.isInfoEnabled())
logger.info("Got TERMINATION_REQUEST(3).");
if (getSentTerminationAnswer()) {
logger.error("Error. Termination answer already sent! Aborting.");
return;
}
answer = session.createCreditControlAnswer();
if(userHasCredit(request.getUserName(),request.getRequestedServiceUnit()))
{
GrantedServiceUnitAvp gsu = chargeUser(request.getRequestedServiceUnit());
answer.setGrantedServiceUnit(gsu);
answer.setResultCode(2001);
}else
{
//4012 == CREDIT_LIMIT_REACHED
answer.setResultCode(4012);
}
if (logger.isInfoEnabled()) {
logger.info("Processed Credit-Control-Request:\n" + request);
logger.info("Sending Credit-Control-Answer:\n" + answer);
}
session.sendCreditControlAnswer(answer);
setSentTerminationAnswer(true);
} catch (Exception e) {
logger.error("Failed to create/send Credit-Control-Answer to reply TERMINATION_REQUEST(3).", e);
}
break;
case 4:
try {
if (logger.isInfoEnabled())
logger.info("Got EVENT_REQUEST(4).");
answer = session.createCreditControlAnswer();
if(userHasCredit(request.getUserName(),request.getRequestedServiceUnit()))
{
GrantedServiceUnitAvp gsu = chargeUser(request.getRequestedServiceUnit());
answer.setGrantedServiceUnit(gsu);
answer.setResultCode(2001);
}else
{
//4012 == CREDIT_LIMIT_REACHED
answer.setResultCode(4012);
}
if (logger.isInfoEnabled())
logger.info("Sending Credit-Control-Answer:\n" + answer);
session.sendCreditControlAnswer(answer);
} catch (Exception e) {
logger.error("Failed to create/send Credit-Control-Answer to reply EVENT_REQUEST(4).", e);
}
break;
default:
logger.error("Unexpected CC-Request-Type in message: " + request.getCcRequestType() + ". Aborting...");
}
}else
{
answer = session.createCreditControlAnswer();
//4011 == DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE
answer.setResultCode(4011);
session.sendCreditControlAnswer(answer);
}
}
This RA uses the Mobicents diameter stack to provide service. The stack is the result of the work done by Mobicents JAIN SLEE and Diameter development teams.
The Resource Adaptor supports configuration only at Resource Adaptor Entity creation time, the following table enumerates the configuration properties:
Table 3.1. Resource Adaptor's Configuration Properties
Property Name | Description | Property Type | Default Value |
---|---|---|---|
authApplicationIds | List of supported Authorization Application Ids in form of {vendor}:{application-id}, separated by comma ',' | java.lang.String | 0:4 |
JAIN SLEE 1.1 Specification requires values set for properties without a default value, which means the configuration for those properties are mandatory, otherwise the Resource Adaptor Entity creation will fail!
There is a single Resource Adaptor Entity created when deploying the Resource Adaptor, named DiameterCCA
. The DiameterCCA
entity uses the default Resource Adaptor configuration, specified in Section 3.1, “Configuration”.
The DiameterCCA
entity is also bound to Resource Adaptor Link Name DiameterCCA
, to use it in an Sbb add the following XML to its descriptor:
<resource-adaptor-type-binding>
<resource-adaptor-type-ref>
<resource-adaptor-type-name>DiameterCCA</resource-adaptor-type-name>
<resource-adaptor-type-vendor>java.net</resource-adaptor-type-vendor>
<resource-adaptor-type-version>0.8.1</resource-adaptor-type-version>
</resource-adaptor-type-ref>
<activity-context-interface-factory-name>
slee/resources/CCAResourceAdaptor/java.net/0.8.1/acif
</activity-context-interface-factory-name>
<resource-adaptor-entity-binding>
<resource-adaptor-object-name>
slee/resources/diameter-cca-ra-interface
</resource-adaptor-object-name>
<resource-adaptor-entity-link>DiameterCCA
</resource-adaptor-entity-link>
</resource-adaptor-entity-binding>
</resource-adaptor-type-binding>
Each Resource Adaptor Entity uses a single JAIN SLEE 1.1 Tracer, named DiameterCCAResourceAdaptor
.
The related Log4j Logger category, which can be used to change the Tracer level from Log4j configuration, is javax.slee.RAEntityNotification[entity=DiameterCCAResourceAdaptor]
.
Ensure that the following requirements have been met before continuing with the install.
The Resource Adaptor hardware's main concern is RAM memory and Java Heap size. It is recomended that for higher loads than 400 calls per second JVM has atleast 1GB heap.
Downloading the source code
Subversion is used to manage its source code. Instructions for using Subversion, including install, can be found at http://svnbook.red-bean.com
Use SVN to checkout a specific release source, the base URL is http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-cca, then add the specific release version, lets consider 2.4.2-SNAPSHOT.
[usr]$ svn co http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/resources/diameter-cca/2.4.2-SNAPSHOT diameter-cca-2.4.2-SNAPSHOT
Building the source code
Maven 2.0.9 (or higher) is used to build the release. Instructions for using Maven2, including install, can be found at http://maven.apache.org
Use Maven to build the deployable unit binary.
[usr]$ cd diameter-cca-2.4.2-SNAPSHOT [usr]$ mvn install
Once the process finishes you should have the deployable-unit
jar file in the target
directory, if Mobicents JAIN SLEE is installed and environment variable JBOSS_HOME is pointing to its underlying JBoss Application Server directory, then the deployable unit jar will also be deployed in the container.
Diameter CCA depends on Base RA and MUX, please refer to separate documentation for proper setup.
Similar process as for Section 4.2.1, “Release Source Code Building”, the only change is the SVN source code URL, which is http://mobicents.googlecode.com/svn/trunk/servers/jain-slee/resources/diameter-cca.
To install the Resource Adaptor simply execute provided ant script build.xml
default target:
[usr]$ ant
The script will copy the RA deployable unit jar to the default
Mobicents JAIN SLEE server profile deploy directory, to deploy to another server profile use the argument -Dnode=
.
To uninstall the Resource Adaptor simply execute provided ant script build.xml
undeploy
target:
[usr]$ ant undeploy
The script will delete the RA deployable unit jar from the default
Mobicents JAIN SLEE server profile deploy directory, to undeploy from another server profile use the argument -Dnode=
.
Revision History | |||
---|---|---|---|
Revision 1.0 | Tue Feb 3 2010 | ||
|