BLC 3.0 With JBoss 6.1.0 successfull configuration

Forum for questions and issues related to 3.0 migration.

Those wishing to upgrade should start by looking at the migration documents published on the Broadleaf Commerce documentation site.

Moderator: jocanas

sunily
Newbie
Newbie
Posts: 14
Joined: Wed Nov 28, 2012 6:25 am

BLC 3.0 With JBoss 6.1.0 successfull configuration

Postby sunily » Wed Feb 12, 2014 2:06 am

BLC 3.0 With JBoss 6.1.0 successfull configuration :-

I have configured and successfully deployed Broadleaf3.0 with mysql into jboss-eap-6.1.0.Alpha, sharing all my configuration steps :-

Broadleaf 3.0 Configurations:--
1. Get source code of DemoSite version 3.0 GA release from GitHub.
2. Get full source code version 3.0GA release from path GitHub.
Configure the DemoSite
Prerequisite –
(a) Demosite is configured and running successfully under jetty as per given configuration in the Broadleaf site.
(b) JBoss-eap-6.1.0.Alpha configured and running.
(c) Mysql database is installed and configured a server instance with name “broadleaf” with [user/password =root/root].

Configure Full source Code in eclipse
Create a new project in the eclipse in the same workspace where Demo Site is configured and link source to full source code which you have downloaded from GitHub.
Create a java project in eclipse :-
I have given a name “SourceBroadleafCommerce” and link this project to full source directory “C:\GitHubSource\BroadleafCommerce-3.0”
Open Command prompt and go to the full source code main directory “C:\GitHubSource\BroadleafCommerce-3.0”and execute the maven install command.
C:\GitHubSource\BroadleafCommerce-3.0> mvn install
This step will create many jar files and copied those into Maven local repository.[This process will take time around 5-10 minutes].
Version of jar created by this action you will find in “pom.xml” under /SourceBroadleafCommerce/BroadleafCommerce-3.0/pom.xml. You have to refer to this version of jars in your development environment. In our case it is “3.0.3-SNAPSHOT”
[for my machine all jars put in the path C:\Documents and Settings\user\.m2\repository\org\broadleafcommerce\]


Deploying BroadleafCommerce 3.0 on Jboss-eap-6.1

Prerequisite :- Java6 or Java7 must be installed on your computer.
1. Download JBoss 7.2 version under the “jboss-eap-6.1.0.Alpha.zip” distribution from JBoss site.
2. Unzip the folder in “C:\” and give it a name “C:\jboss-eap-6.1”.
3. We have to configure JBoss server to run in Standalone mode. So we will configure it accordingly.
Go to the directory “C:\jboss-eap-6.1\bin” open the file “standalone.conf” and update the
following:-
JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
to
JAVA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true"

4. Go to the directory “C:\jboss-eap-6.1\bin” open the file “standalone.conf.bat” and update the following line :-
JAVA_OPTS=-Xms1303M -Xmx1303M -XX:MaxPermSize=256M
to
JAVA_OPTS=-Xms512M -Xmx512M -XX:MaxPermSize=512M

5. Set environment variable JBOSS_HOME=“C:\jboss-eap-6.1”

6. Add User and Role in the JBoss server:-

JBoss makes use of security realms to secure access to the management interfaces, these same realms are used to secure inbound access as exposed by JBoss Remoting such as remote JNDI and EJB access, the realms are also used to define an identity for the server - this identity can be used for both inbound connections to the server and outbound connections being established by the server.

ManagementRealm is a simple realm available in Jboss, this simply enables two authentication mechanisms, the local mechanism and username/password authentication which will be using Digest authentication

For username / password authentication the users details will be loaded from the file mgmt-users.properties which is located in {jboss.home}/standalone/configuration



(a) Add Users For the management Console :-
Open the commands prompt and go to the directory “C:\jboss-eap-6.1\bin” and run “add-user.bat” and enter the following details:-

Add management user by selecting “a”
Realm (ApplicationRealm): [leave it blank just hit enter]
Username: jboss6
Password: jboss6@2013
Re-enter Password: jboss6@2013
About to add user 'jboss6' for realm 'ApplicationRealm'
Is this correct yes/no? yes
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB call
yes/no? yes

Now restart the server and go to admin console using URL http://localhost:9990/console/App.html

Enter User Name: jboss6
Password: jboss6@2013

You will enter in admin section of Jboss.


Add Database module:-

By default JBoss7.2 under jboss-eap6.1.0 bundled with “h2database”.If we want to use any other database then we have to configure it under its module.


1. Add “MySQL” module

(a). Create a folder “mysql\main” under “C:\jboss-eap-6.1\modules\system\layers\base\com”
(b). Copy jar file “mysql-connector-java-5.1.26-bin.jar” under the above path.
(c). Create a file named “module.xml” under path “C:\jboss-eap-6.1\modules\system\layers\base\com\mysql\main” and add the following content into module.xml :-

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mysql">
<resources>
<resource-root path="mysql-connector-java-5.1.26-bin.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>

(d). Add the following line in “standalone.xml” under the <datasources> section

Note: - Create a database in mysql server with name ”broadleaf” and
[user/password => root/root] which we are referring here.

<datasource jta="true" jndi-name="java:jboss/datasrc/ExaMYSQLDB" pool-
name="TestMYSQL" enabled="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/broadleaf</connection-url>
<driver>mysql</driver>
<security>
<user-name>root</user-name>
<password>root</password>
</security>
</datasource>

(e). Add the following line in “standalone.xml” under the <drivers> section :-

<driver name="mysql" module="com.mysql"/>

Now restarts the JBoss server and go to home page using URL http://localhost:9990/console/App.html
Enter “User Name” and “Password” which we have created in above configuration step in our case it is “jboss6” and “: jboss6@2013”.

and go to Profile>Connector>Datasources
Select the newly created datasource “TestMySQL” from the “JDBC Datasources” list and click the “Test Connection” button.

Note :- You will get successful connection message


Configure DemoSite, MySQL in JBoss server:-
(A).Add JBoss maven plug-in to pom.xml “/site/pom.xml” in the <build><plugins>section.
<!-- JBoss7 Plug-in -->
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.3.Final</version>
</plugin>
(B). Configure 3 DataSource for mysql database in JBoss Server’s standalone.xml file under <datasources> tag.
<datasource jta="true" jndi-name="java:jboss/datasources/BroadleafDS" pool-name="BroadleafDS_Pool" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/broadleaf</connection-url>
<driver>mysql</driver>
<security>
<user-name>root</user-name>
<password>root</password>
</security>
<timeout>
<idle-timeout-minutes>0</idle-timeout-minutes>
<query-timeout>600</query-timeout>
</timeout>
</datasource>
<datasource jta="true" jndi-name="java:jboss/datasources/BroadleafSecureDS" pool-name="BroadleafSecureDS_Pool" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/broadleaf</connection-url>
<driver>mysql</driver>
<security>
<user-name>root</user-name>
<password>root</password>
</security>
<timeout>
<idle-timeout-minutes>0</idle-timeout-minutes>
<query-timeout>600</query-timeout>
</timeout>
</datasource>
<datasource jta="true" jndi-name="java:jboss/datasources/BroadleafCmsDS" pool-name="BroadleafCmsDS_Pool" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/broadleaf</connection-url>
<driver>mysql</driver>
<security>
<user-name>root</user-name>
<password>root</password>
</security>
<timeout>
<idle-timeout-minutes>0</idle-timeout-minutes>
<query-timeout>600</query-timeout>
</timeout>
</datasource>

(C). Update core/src/main/resources/META-INF/persistence.xml as follows to use
DataSources configured in Jboss Server.

<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/ ... ce_2_0.xsd"
version="2.0">

<persistence-unit name="blPU" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafDS</non-jta-data-source>
<exclude-unlisted-classes/>
</persistence-unit>

<persistence-unit name="blSecurePU" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafSecureDS</non-jta-data-source>
<exclude-unlisted-classes/>
</persistence-unit>

<persistence-unit name="blCMSStorage" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafCmsDS</non-jta-data-source>
<exclude-unlisted-classes/>
</persistence-unit>
</persistence>


(D). Update site/src/main/webapp/WEB-INF/applicationContext.xml as follows:

<bean id="blMergedDataSources" class="org.springframework.beans.factory.config.MapFactoryBean">
<property name="sourceMap">
<map>
<entry key="java:jboss/datasources/BroadleafDS" value-ref="webDS"/>
<entry key="java:jboss/datasources/BroadleafSecureDS" value-ref="webSecureDS"/>
<entry key="java:jboss/datasources/BroadleafCmsDS" value-ref="webStorageDS"/>
</map>
</property>
</bean>

(E) Update site\src\main\webapp\WEB-INF\applicationContext-datasource.xml and update the jndi related entried as following lines :-

<jee:jndi-lookup id="webDS" jndi-name="java:jboss/datasources/BroadleafDS"/>
<jee:jndi-lookup id="webSecureDS" jndi-name="java:jboss/datasources/BroadleafSecureDS"/>
<jee:jndi-lookup id="webStorageDS" jndi-name="java:jboss/datasources/BroadleafCmsDS"/>

Update site/src/main/webapp/WEB-INF/web.xml with following content :-

<resource-ref>
<res-ref-name>java:jboss/datasources/BroadleafDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>


(F) Now start JBoss application server as standalone.

Open command prompt and start Jboss by executing bat file “standalone.bat”

Open other command prompt in other window and deploy the application into running jboss.

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\site>mvn jboss-as:deploy


You will get the following error:

ERROR Error creating bean with name 'blMergedDataSources' defined in resource loaded from byte array: Cannot resolve reference to bean 'webDS' while setting bean property 'sourceMap' with key [TypedStringValue: value [java:jboss/datasources/BroadleafDS], target type [null]]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webDS': Post-processing of the FactoryBean's object failed; nested exception is java.lang.IllegalArgumentException: warning no match for this type name: org.broadleafcommerce.profile.core.service.CustomerAddressService [Xlint:invalidAbsoluteTypeName]

Note: Below 3 steps G,H and I taken from http://www.shivalabs.in

(G) Create jboss-deployment-structure.xml in site/src/main/webapp/WEB-INF/ folder.

<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
<deployment>
<dependencies>
<module name="org.jboss.ironjacamar.jdbcadapters" />
</dependencies>
<exclusions>
<module name="org.apache.commons.logging"/>
<module name="org.apache.log4j"/>
<module name="org.jboss.logging"/>
<module name="org.jboss.logmanager"/>
<module name="org.jboss.logmanager.log4j"/>
<module name="org.slf4j"/>
</exclusions>
</deployment>
</jboss-deployment-structure>



Note: - Now we have to configure Hibernate3 features under jboss-eap-6.1.0 because by default it comes with Hibernate4 and broadleaf is using Hibernate3 features.


So let us install hibernate3 module in JBoss-eap-6.1.0 and use it.

(H) Install Hibernate 3 module in JBoss AS

Copy the following jars (you can get these from site.war file otherwise directly download from any site) into folder
jboss-eap-6.1/modules/system/layers/base/org/hibernate/3/

antlr-2.7.6.jar
commons-collections-3.2.1.jar
dom4j-1.6.1.jar
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.10.Final.jar
hibernate-entitymanager-3.6.10.Final.jar
javassist-3.16.1-GA.jar

Create module.xml in
jboss-eap-6.1/modules/system/layers/base/org/hibernate/3/

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.hibernate" slot="3">
<resources>
<resource-root path="hibernate-core-3.6.10.Final.jar"/>
<resource-root path="javassist-3.16.1-GA.jar"/>
<resource-root path="antlr-2.7.6.jar"/>
<resource-root path="commons-collections-3.2.1.jar"/>
<resource-root path="dom4j-1.6.1.jar"/>
<!-- Insert other Hibernate 3 jars to be used here -->
<resource-root path="hibernate-commons-annotations-3.2.0.Final.jar"/>
<resource-root path="hibernate-entitymanager-3.6.10.Final.jar"/>
</resources>
<dependencies>
<module name="org.jboss.as.jpa.hibernate" slot="3"/>
<module name="asm.asm"/>
<module name="javax.api"/>
<module name="javax.persistence.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<module name="org.infinispan" optional="true"/>
<module name="org.javassist"/>
<module name="org.slf4j"/>
</dependencies>
</module>

(I) Tell JBoss to use hibernate 3 module. Update core/src/main/resources/META-INF/persistence.xml

<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/ ... ce_2_0.xsd"
version="2.0">
<persistence-unit name="blPU" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafDS</non-jta-data-source>
<exclude-unlisted-classes/>
<properties>
<property name="jboss.as.jpa.providerModule" value="org.jboss.as.jpa.hibernate:3"/>
<property name="jboss.as.jpa.managed" value="false" />
</properties>
</persistence-unit>

<persistence-unit name="blSecurePU" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafSecureDS</non-jta-data-source>
<exclude-unlisted-classes/>
<properties>
<property name="jboss.as.jpa.providerModule" value="org.jboss.as.jpa.hibernate:3"/>
<property name="jboss.as.jpa.managed" value="false" />
</properties>
</persistence-unit>

<persistence-unit name="blCMSStorage" transaction-type="RESOURCE_LOCAL">
<non-jta-data-source>java:jboss/datasources/BroadleafCmsDS</non-jta-data-source>
<exclude-unlisted-classes/>
<properties>
<property name="jboss.as.jpa.providerModule" value="org.jboss.as.jpa.hibernate:3"/>
<property name="jboss.as.jpa.managed" value="false" />
</properties>
</persistence-unit>
</persistence>

(J) Add jboss-web.xml under site\src\main\webapp\WEB-INF\jboss-web.xml with following content:-

<?xml version="1.0" encoding="UTF-8" ?>
<jboss-web>
<context-root>/</context-root>
</jboss-web>

Add Mysql dependency in C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\pom.xml

<!— MySQL Dependency -->
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.1.26</version>
</dependency>

And “/site/pom.xml”

<!-- MySQL Dependency -->
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
</dependency>


Add Hibernate dialect in following files
[This must be changed whenever you are changing database]:-

1. /DemoSite/build.properties

ant.hibernate.sql.ddl.dialect=org.hibernate.dialect.MySQL5InnoDBDialect

and also update entries for blPU, blSecurePU and blCMSStorage as follows:-

ant.blPU.url=jdbc:mysql://localhost:3306/broadleaf
ant.blPU.userName=root
ant.blPU.password=root
ant.blPU.driverClassName=com.mysql.jdbc.Driver

ant.blSecurePU.url=jdbc:mysql://localhost:3306/broadleaf
ant.blSecurePU.userName=root
ant.blSecurePU.password=root
ant.blSecurePU.driverClassName=com.mysql.jdbc.Driver

ant.blCMSStorage.url=jdbc:mysql://localhost:3306/broadleaf
ant.blCMSStorage.userName=root
ant.blCMSStorage.password=root
ant.blCMSStorage.driverClassName=com.mysql.jdbc.Driver


2. Add hibernate dialect in “/core/src/main/resources/runtime-properties/common-shared.properties” in the following three lines :-

(a)blPU.hibernate.dialect=org.hibernate.dialect.MySQL5InnoDBDialect
(b)blCMSStorage.hibernate.dialect=org.hibernate.dialect.MySQL5InnoDBDialect

(c)blSecurePU.hibernate.dialect=org.hibernate.dialect.MySQL5InnoDBDialect


(K). Clean Project by following command.

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite>mvn clean

(L) Install (package) Project

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite>mvn install

 Set “enable-welcome-root” to “false” in JBoss configuration file “standalone.xml” so that jboss’s default welcome page should not come when hitting the URL:- http://localhost:8080.

This path is configured for front site’s home page because we specified its path as root directory in “jboss-web.xml” under site directory.
<virtual-server name="default-host" enable-welcome-root="false">


(M) Start the Jboss Server

(N) Deploy the “site” module of DemoSite project into Jboss server

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite>site>mvn jboss-as:deploy

After successful deployment message on JBoss server hit the following URL to check out the site: -- http://localhost:8080

Browse the application add an item to the cart and go to checkout page, you will get blank page because you moved from http to https page here. To solve this issue add the certificate file into the JBoss configuration file “standalone.xml”

(O) Add the “https” connector under the <connector> section in JBoss’s standalone.xml with certificate-key-file name. You can find certificate key file name under following directory:-

/site/target/mycompany/WEB-INF/blc-example.keystore

Copy this file “blc-example.keystore” from
/site/target/mycompany/WEB-INF/blc-example.keystore

to JBoss server configuration directory

“C:\jboss-eap-6.1\standalone\configuration\”

<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl name="https" password="broadleaf" certificate-key-file="../standalone/configuration/blc-example.keystore"/>
</connector>

Now restart the Jboss server and browse the application, add an item and go to checkout page. This time you will get checkout page and you can proceed with submit of your order.

Steps to deploy Admin module in Jboss EAP 6.1.0:-

(A) Specify JBoss maven plug-in into “pom.xml” under admin module in the <build> section.
File name: - C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\admin\pom.xml
<!-- JBoss7 Plug-in -->
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.3.Final</version>
</plugin>
(B) Step1:- Add “jboss-deployment-structure.xml” file under
C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\admin\src\main\webapp\WEB-INF\

With following contents:--

<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
<deployment>
<dependencies>
<module name="org.jboss.ironjacamar.jdbcadapters" />
</dependencies>
<exclusions>
<module name="org.apache.commons.logging"/>
<module name="org.apache.log4j"/>
<module name="org.jboss.logging"/>
<module name="org.jboss.logmanager"/>
<module name="org.jboss.logmanager.log4j"/>
<module name="org.slf4j"/>
</exclusions>
</deployment>
</jboss-deployment-structure>


(C) Step-2: Add “jboss-web.xml” in path C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\admin\src\main\webapp\WEB-INF\

With following contents:--

<?xml version="1.0" encoding="UTF-8" ?>
<jboss-web>
<context-root>/admin</context-root>
</jboss-web>


(D) Add the datasource entry in “/admin/src/main/webapp/WEB-INF/applicationContext-datasource.xml”

<jee:jndi-lookup id="webDS" jndi-name="java:jboss/datasources/BroadleafDS"/>
<jee:jndi-lookup id="webSecureDS" jndi-name="java:jboss/datasources/BroadleafSecureDS"/>
<jee:jndi-lookup id="webStorageDS" jndi-name="java:jboss/datasources/BroadleafCmsDS"/>

(E) Add datasource entry in “/admin/src/main/webapp/WEB-INF/applicationContext-admin.xml”

<bean id="blMergedDataSources" class="org.springframework.beans.factory.config.MapFactoryBean">
<property name="sourceMap">
<map>
<entry key="java:jboss/datasources/BroadleafDS" value-ref="webDS"/>
<entry key="java:jboss/datasources/BroadleafSecureDS" value-ref="webSecureDS"/>
<entry key="java:jboss/datasources/BroadleafCmsDS" value-ref="webStorageDS"/>
</map>
</property>
</bean>

(F) Step 3: deploy the admin module :
Open command prompt end execute maven command as :-

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\admin>mvn jboss-as:deploy


Since site module is already deployed and running and when we try to deploy admin we get the following error message :-

Caused by: org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [org.hibernate.jmx.StatisticsService@95b081] with key 'org.broadleafcommerce:name=hibernate.statistics-broadleaf'; nested exception is javax.management.InstanceAlreadyExistsException: org.broadleafcommerce:name=hibernate.statistics-broadleaf

(G) To resolve this issue we have to modify the core framework configuration files

1. C:\GitHubSource\BroadleafCommerce-3.0\core\broadleaf-framework\src\main\resources\bl-framework-applicationContext.xml

<bean id="blAttributeSource" class="org.broadleafcommerce.common.jmx.AnnotationJmxAttributeSource">
<constructor-arg>
<bean class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName">
<value>java:comp/env/appName</value>
<!-- <value>java:/comp/env/appName</value> --> commented by Sunil
</property>
<property name="defaultObject" value="broadleaf"/>
</bean>
</constructor-arg>
</bean>


Commented the original line “java:/comp/env/appName” and removed extra “/” so that jboss understand the jndi name properly. See correct value in yellow shaded area.


2. C:\GitHubSource\BroadleafCommerce-3.0\core\broadleaf-profile\src\main\resources\bl-profile-applicationContext-persistence.xml

<bean class="org.broadleafcommerce.common.jmx.ExplicitNameFactoryBean">
<constructor-arg value="org.broadleafcommerce:name=hibernate.statistics"/>
<constructor-arg>
<bean class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName">
<value>java:comp/env/appName</value>
<!-- value>java:/comp/env/appName</value --> commented by Sunil
</property>
<property name="defaultObject" value="broadleaf"/>
</bean>
</constructor-arg>
</bean>

(H) Now open command prompt and go to full source code directory C:\GitHubSource\BroadleafCommerce-3.0

Run the maven command to clean the existing jar files.

C:\GitHubSource\BroadleafCommerce-3.0>mvn clean

Run the “maven install” command to package all the jar files again with changed source code.

C:\GitHubSource\BroadleafCommerce-3.0>mvn install

This process will add new jar files in local maven repository

Verify that your DemoSite/pom.xml is referring to the latest version of created jar file

Otherwise you may have to update “<blc.version>3.0.3-SNAPSHOT</blc.version>” in DemoSite/pom.xml

(I) Open command prompt and go to site working directory
C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\site and undeploy the running site application

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\site>mvn jboss-as:undeploy

After successfully undeploy the application.

Stop the Jboss server.

Start the Jboss server.

(J) Now go to the directory C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\
Run the mvn clean command to clean existing jar and war files.

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite>mvn clean

Now run maven install to package the jar and war file again.

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite>mvn install

Deploy site module by following command from site directory:-

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\site>mvn jboss-as:deploy

It will deploy site module in JBoss server, After BUILD SUCCESS message hit the URL and verify http://localhost:8080

Now deploy the admin module by following command from admin directory:-

C:\BLCWorkspace3.0\eclipse-workspace\DemoSite\admin>mvn jboss-as:deploy

It will deploy admin module in JBoss server, After BUILD SUCCESS message hit the URL and verify https://localhost:8443/admin

jefffischer
Team Member
Team Member
Posts: 307
Joined: Tue Sep 29, 2009 12:33 pm

Re: BLC 3.0 With JBoss 6.1.0 successfull configuration

Postby jefffischer » Wed Mar 05, 2014 6:12 pm

Fyi - here's documentation for installing Broadleaf version 3.1.1 on JBoss AS 7

https://github.com/BroadleafCommerce/do ... utorial.md
Jeff Fischer
Broadleaf Commerce
jfischer@broadleafcommerce.org

kunte.vinayak
Newbie
Newbie
Posts: 1
Joined: Wed Apr 23, 2014 12:06 pm

Re: BLC 3.0 With JBoss 6.1.0 successfull configuration

Postby kunte.vinayak » Wed Apr 23, 2014 12:10 pm

getting error in jdbc connection.
i have done all the steps which u have given but while testing connection i am getting an error saying
Failed to create JDBC connection. internal error occurred. so what may be the solution for this??

sunily
Newbie
Newbie
Posts: 14
Joined: Wed Nov 28, 2012 6:25 am

Re: BLC 3.0 With JBoss 6.1.0 successfull configuration

Postby sunily » Wed May 28, 2014 9:21 am

kunte.vinayak wrote:getting error in jdbc connection.
i have done all the steps which u have given but while testing connection i am getting an error saying
Failed to create JDBC connection. internal error occurred. so what may be the solution for this??


Hi Vinayak,
After successfull deployment can you please verify that all your table successfully created in the database with all the data ?
Can you please share your log file ?


Return to “3.0 Upgrade and Migration”

Who is online

Users browsing this forum: No registered users and 1 guest