Re: [jboss-dev-forums] [JBoss AS7 Development] - stopping jboss7
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/brian.stansberry] commented on the document
"stopping jboss7"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-17175#comment-7575
--------------------------------------------------
bin/jboss-admin.sh --connect --controller=<hostname>:9999 --command=:shutdown
where hostname is a resolvable hostname or IP address that matches the server's management interface.
The --controller=xxx part is independent of the --connect and --command=:shutdown bits; it's a general purpose way of telling the CLI the address:port of the process to connect to. E.g. starting an interactive shell and then connecting works:
bin bstansberry$ ./jboss-admin.sh --controller=192.168.0.1:9999
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
Connected to standalone controller at 192.168.200.12:9999
[standalone@192.168.200.12:9999 /]
That example is a bit arbitrary; just meant to show --controller as a param to jboss-admin.sh is independent of the --connect param. A more normal way to connect would be to either pass both on the command line:
./jboss-admin.sh --connect --controller=192.168.0.1:9999
or to launch the interactive CLI unconnected and then pass the host:port as a param to the connect command:
bin bstansberry$ ./jboss-admin.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect 192.168.200.12:9999
Connected to standalone controller at 192.168.200.12:9999
[standalone@192.168.200.12:9999 /]
Note that in all examples above the ":9999" part is not required. If the :<port> bit isn't provided the CLI assumes :9999.
We'll work on getting this better documented in the Admin Guide.
--------------------------------------------------
14 years, 1 month
Re: [jboss-dev-forums] [JBoss AS7 Development] - Detyped Description of the AS 7 Management Model
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/brian.stansberry] commented on the document
"Detyped Description of the AS 7 Management Model"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16317#comment-7574
--------------------------------------------------
You just keep doing add(key, value) calls:
ModelNode address = op.get("address");
address.add("subsystem", "messaging");
address.add("jms-topic", "myexampletopic");
You can discover the legal types (e.g. "jms-topic") for children of the subsystem=messaging resource via the read-resource-description operation described above (the legal keys are the names of the child elements under "children" as described in "Description of Parent/Child Relationships" above). You can also execute the "read-children-types" operation against the subsystem=messaging resource; the response is a list of valid child types.
--------------------------------------------------
14 years, 1 month
[JBoss AS7 Development] - Create datasource using CLI
by Ramesh Reddy
Ramesh Reddy [http://community.jboss.org/people/rareddy] created the discussion
"Create datasource using CLI"
To view the discussion, visit: http://community.jboss.org/message/624510#624510
--------------------------------------------------------------
Can somebody post a sample on how to create a data source using CLI? I checked Admin Guide, did not see any example. The help says, run command "data-source", it was not much help on what parameter it needs, looks like you can ask for "operation-description for the command. Can somebody give small example?
Then I tried something like
/subsystem=datasources/data-source=java\:/TestDS:add(jndi-name=java:/TestORCL, connection-url= jdbc:oracle:thin:@server:1521:orcl, driver-name=oracle, user-name=myuser, password=pass, pool-name=testorcl)
given my driver module "oracle" is deployed already, this succeeds. Now I do not see the data source created in the admin-console right away after refresh, I had to restart the server before I can see it.
I had my user-name set wrong on the data source, so I used admin-console to update the user-name and saved it. But the changes did not take effect either. Is there a refresh or persistence issue with admin-console.
Thanks
Ramesh..
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624510#624510]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
[JBoss Web Services Development] - JBossWS - Running the test suites
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Running the test suites"
To view the document, visit: http://community.jboss.org/docs/DOC-13523
--------------------------------------------------------------
***
#Working_with_the_integration_layers Working with the integration layers
****
#Ant_build Ant build
****
#Maven__Ant_build Maven + Ant build
****
#JBossWSCXF_Spring_testsuite JBossWS-CXF Spring testsuite
***
#Working_with_the_Hudson_QA_environment Working with the Hudson QA environment
****
#Maven__Ant_build_237778 Maven + Ant build
Typically you would build, deploy, test one of the web service stacks against one of the supported target containers. Here we explain first the manual procedure. Further down you find instruction on how to do this using our automated Hudson QA environment.
Please not two different builds are available, Ant and Maven+Ant, as the binary distribution does not use Maven.
h3. Working with the integration layers
To run the general JAX-WS samples against our native WS stack on JBoss-6.0 you would run the sequence below. This is also the required sequence before any SVN commit. If one of the tests fails, please complain loudly.
h4. Ant build
+*Note*+
+Make sure to *modify ant.properties* accordingly before running the tasks below. Running the tests against another target container simply means changing the ant.properties calling "ant deploy-jboss510" for instance. Also please note that the provided Ant targets may change from release to release because of different supported AS containers; calling "ant -projecthelp" is often a good idea to understand which targets are available.+
cd stack/native/trunk/target/jbossws-bin-dist
ant deploy-jboss600
ant tests-main
ant tests-samples
To run the collection of provider sample tests, you would run
ant -Dtest=jaxws/samples/provider test
To run a single specific test, you would run
ant -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test
This can be done in debug mode as well
ant -Ddebug=true -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test
h4. Maven + Ant build
+*Note*+
+Make sure to *copy/modify profiles.xml.example/profiles.xml* accordingly before running the tasks below. Running the tests against another target container both means changing the deploy ant command ("ant deploy-jboss510" for instance) and the specified maven profile when running the tests. This simply means changing the specified profile to "jboss510" for instance. Also please note that the provided target profiles may change from release to release because of different supported AS containers.+
cd stack/native/trunk
ant deploy-jboss600
mvn -Ptestsuite,jboss600 test
To run the collection of provider sample tests, you would run
mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider test
To run a single specific test, you would run
mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase test
This can be done in debug mode as well
mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase -Dmaven.surefire.debug=true test
Finally, depending on the Maven version you're using, you might need to set the jbossXYZ.home property:
mvn -Ptestsuite,jboss600 -Djboss600.home=/home/user/jboss/build/output/jboss-6.0.0.Final test
Please note that starting from JBossWS 4, the integration testsuites have been moved to the 'integration-test' maven phase. So you need to replace 'test' with 'integration-test' in the mvn commands above.
h4. JBossWS-CXF Spring testsuite
Starting from jbossws-cxf 3.4.0 just keep in mind that SpringFramework dependencies are not triggered by default anymore. You can add Spring to the testsuite client classpath as well as enable additional tests relying on Spring using the custom "spring" maven profile:
mvn -Ptestsuite,jboss600,spring test
h3.
h3. Working with the Hudson QA environment
The Hudson QA environment helps you to test any supported stack against any supported target container.
h4. Maven + Ant build
The Hudson setup is still based on Ant. You just need to checkout the jbossws-framework and move to the "hudson" directory.
cd jbossws/framework/trunk/hudson
ant hudson-setup
ant hudson-start
When you hit http://localhost:8180/hudson http://localhost:8180/hudson you should be able to
* log-in
* build a target container
* run a test-suite against the target container
Publicly, Hudson is available at http://jbossws.jboss.org:8180/hudson/ http://jbossws.jboss.org:8180/hudson/ (or http://jbossws.jboss.org:8280/hudson/ http://jbossws.jboss.org:8280/hudson/ during QA release phase)
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-13523]
Create a new document in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 1 month
[JBoss Web Services Development] - JBossWS - Building From Source
by Alessio Soldano
Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Building From Source"
To view the document, visit: http://community.jboss.org/docs/DOC-13547
--------------------------------------------------------------
This page documents the *Maven* based build that we use *since jbossws-3.0.2*. See the http://community.jboss.org/docs/DOC-13514 Mavenization page for details regarding configuring you Maven environment. The Ant based build of previous versions, is documented http://community.jboss.org/docs/DOC-13548 here.
**
#Checkout_and_build_JBossAS Checkout and build JBossAS
***
#Build_JBoss_with_JDK_6 Build JBoss with JDK 6
***
#Run_jboss Run jboss
**
#Checkout_and_build_JBossWSNative Checkout and build JBossWS-Native
***
#Edit_profilesxml Edit profiles.xml
***
#BuildDeploy Build/Deploy
***
#Run_the_smoke_tests Run the smoke tests
**
#Checkout_and_build_JBossWSCXF Checkout and build JBossWS-CXF
***
#_Edit_profilesxml Edit profiles.xml
***
#BuildDeploy_226780 Build/Deploy
***
#Run_the_smoke_tests_719018 Run the smoke tests
h2. Checkout and build JBossAS
svn co http://anonsvn.jboss.org/repos/jbossas/trunk
For more information, see http://wiki.jboss.org/wiki/Wiki.jsp?page=SVNRepository SVNRepository
h3. Build JBoss with JDK 6
cd trunk
build/build.sh
h3. Run jboss
Before you start jboss, you should follow the deploy steps for a supported stack (see below).
cd trunk/build/output/jboss-5.0.1.GA
bin/run.sh
h3.
h2. Checkout and build JBossWS-Native
svn co http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk jbossws-native
For more information, see http://community.jboss.org/docs/DOC-13526 Subversion
h3. Edit profiles.xml
<profile>
<id>jboss-home-profile</id>
<activation>
<property>
<name>user.name</name>
</property>
</activation>
<properties>
<jboss421.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA</jboss421.home>
<jboss422.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_2_GA/build/output/jboss-4.2.2.GA</jboss422.home>
<jboss423.home>/home/tdiesler/svn/jbossas/branches/Branch_4_2/build/output/jboss-4.2.3.GA</jboss423.home>
<jboss500.home>/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_Beta4/build/output/jboss-5.0.0.Beta4</jboss500.home>
<jboss501.home>/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.CR1</jboss501.home>
</properties>
</profile>
Starting from JBossWS 4, the build is supporting Maven 3, which made the use of profiles.xml deprecated.As a consequence of that, you should actually be providing the jbossXYZ.home property on the command line when invoking mvn.
h3. Build/Deploy
To deploy jbossws-native you run:
cd jbossws-native
ant deploy-jboss501
When jboss starts you should see something like
09:32:09,581 INFO [ServerImpl] Starting JBoss (Microcontainer)...
09:32:09,583 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)
...
09:33:24,587 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
09:33:24,588 INFO [NativeServerConfig] 3.0.2-SNAPSHOT
...
09:33:32,318 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:33:32,341 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)] Started in 1m:22s:744ms
h3. Run the smoke tests
cd jbossws-native
mvn -Psmoketest,jboss501 test
You should expect to see no test failures. There might be a number of FIXME messages on the console. These are linked to open JIRA issues.
Starting from JBossWS 4, the integration testsuites have been moved to 'integration-test' maven phase. So you need to use:
mvn -Psmoketest,jboss710 -Djboss710.home=path-to-jboss710 integration-test
h2. Checkout and build JBossWS-CXF
svn co http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk jbossws-cxf
For more information, see http://community.jboss.org/docs/DOC-13526 Subversion
h3. ** Edit profiles.xml
<profile>
<id>jboss-home-profile</id>
<activation>
<property>
<name>user.name</name>
</property>
</activation>
<properties>
<jboss421.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA</jboss421.home>
<jboss422.home>/home/tdiesler/svn/jbossas/tags/JBoss_4_2_2_GA/build/output/jboss-4.2.2.GA</jboss422.home>
<jboss423.home>/home/tdiesler/svn/jbossas/branches/Branch_4_2/build/output/jboss-4.2.3.GA</jboss423.home>
<jboss500.home>/home/tdiesler/svn/jbossas/tags/JBoss_5_0_0_Beta4/build/output/jboss-5.0.0.Beta4</jboss500.home>
<jboss501.home>/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.CR1</jboss501.home>
</properties>
</profile>
Starting from JBossWS 4, the build is supporting Maven 3, which made the use of profiles.xml deprecated.As a consequence of that, you should actually be providing the jbossXYZ.home property on the command line when invoking mvn.h3. Build/Deploy
To deploy jbossws-cxf you run:
cd jbossws-cxf
ant deploy-jboss500
Starting from JBossWS-CXF 3.4.0 SpringFramework libraries are not installed by default. If still want that you need to run:
ant -Dspring=true deploy-jboss500
When jboss starts you should see something like
13:16:25,104 INFO [ServerImpl] Starting JBoss (Microcontainer)...
13:16:25,106 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)
...
13:18:01,278 INFO [CXFServerConfig] JBoss Web Services - Stack CXF Runtime Client
13:18:01,279 INFO [CXFServerConfig] 3.0.2-SNAPSHOT
...
13:18:09,355 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:18:09,389 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200805051004)] Started in 1m:44s:270ms
h3. Run the smoke tests
cd jbossws-cxf
mvn -Psmoketest,jboss501 test
Starting from JBossWS 4, the integration testsuites have been moved to 'integration-test' maven phase. So you need to use:
mvn -Psmoketest,jboss710 -Djboss710.home=path-to-jboss710 integration-test
You should expect to see no test failures. There might be a number of FIXME messages on the console. These are linked to open JIRA issues.
Tests that are known to fail should be excluded in the container specific exclude file. Note, if a test is excluded it is not even compiled and hence will not run in any of the ant test targets.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-13547]
Create a new document in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 1 month