#jboss7

[codepk-blog]

JOSSO Agent 1.8 Installation in JBOSS 7.1

After going through lots of websites & help from forums, was able to install JOSSO agent 1.8 on JBOSS 7.1.

Just to reduce pain for fellow developers, here are the details for the same.

First of all would like to appreciate the efforts put by JOSSO team they are doing a wonderful job & great framework.

Prerequisite

JBOSS 7.1 installed on linux

JBOSS 4.2 installed or any other Application server with josso gateway 1.8.5

1)  Open the file 

/credideal/JBOSS-7.1/standalone/deployments/PORTAL.war/WEB-INF/jboss-web.xml

if not present, copy the file attached

Set the context to the one same as the war name  

<context-root>/PORTAL</context-root>

Note the context path is casesensitive and should be same as that of your partner app

2) Copy the Attached

josso-1.2.wsdl & josso-1.2.xsd in the {JBOSS_HOME}/bin

3) Open josso-1.2.wsdl

Change the 8081 port to that of Gateway server

4) Download JOSSO 1.8.8 from 

http://sourceforge.net/projects/josso/files/JOSSO/JOSSO-1.8.8/josso-1.8.8.zip/download

5) Extract JOSSO to /creadideal - or any place you wish to.

6) Create empty folder in /credideal/josso-1.8.8/dist/agents/bin

Win32

Win64

7) Rename JBoss's  standalone.xml to default.xml

8) JOSSO Installation  - Start the putty and navigate to /credideal/josso-1.8.8/bin

Start josso using the following command

sh josso-gsh

9) Start installation using the following command

agent install --target /credideal/JBOSS-7.1 --platform jb7

--target indicates the path to the JBOSS server.

All the status should be [OK] .. incase of [ERROR] OR [WARN]  please Solve the same and start the whole process again

10) Rename default.xml to standalone.xml & delete the files default.xml.bkp.1 default.xml.bkp.2 if present in the same folder

11) Delete the backup files from this path /credideal/JBOSS-7.1/modules/org/josso/main  namely *.bkp.1

12) Open /credideal/JBOSS-7.1/modules/org/josso/main/module.xml

Search josso-agents-bin-1.8.8-jaxws.jar

Replace the whole tag with this one

 <resource-root path="josso-agents-bin-1.8.8-jaxws.jar"  xmlns="urn:jboss:module:1.1"><filter><include path="META-INF/**" />  </filter> </resource-root> 

Add the following in the resource block

 <resource-root path="spring-core-2.5.5.jar" xmlns="urn:jboss:module:1.1"/> 

<resource-root path="spring-aop-2.5.5.jar" xmlns="urn:jboss:module:1.1"/> 

<resource-root path="xbean-spring-3.4.3.jar" xmlns="urn:jboss:module:1.1"/> 

<resource-root path="spring-beans-2.5.5.jar" xmlns="urn:jboss:module:1.1"/> 

<resource-root path="spring-context-2.5.5.jar" xmlns="urn:jboss:module:1.1"/> 

<resource-root path="spring-context-support-2.5.5.jar" xmlns="urn:jboss:module:1.1"/>

13) Copy all the jars from this path

/credideal/JBOSS-7.1/modules/org/springframework/spring/main 

to

/credideal/JBOSS-7.1/modules/org/josso/main

14) Copy the attached jar

spring-context-support-2.5.5.jar

to

/credideal/JBOSS-7.1/modules/org/josso/main

15) Replace the <dependency> block in /credideal/JBOSS-7.1/modules/org/josso/main/modules.xml

<dependencies> <module name="javax.security.auth.message.api"/> <module name="org.jboss.logging"/> <module name="javax.servlet.api"/> <module name="org.picketbox"/> <module name="org.jboss.as.web"/> <module name="org.apache.cxf"/> <module name="javax.api"/> <module name="javax.jms.api"/> <module name="javax.annotation.api"/> <module name="javax.mail.api"/> <module name="javax.activation.api"/> <module name="org.apache.commons.logging"/> <module name="javax.jws.api"/> <module name="javax.xml.ws.api"/> <module name="javax.xml.ws.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.xml.bind.api"/> <module name="javax.wsdl4j.api"/> </dependencies>

16) Josso Agent Config Changes

Open the josso-agent-config.xml at  /credideal/JBOSS-7.1/modules/org/josso/main/config

Replace

xmlns:protocol="urn:org:josso:protocol:client" 

with

xmlns:protocol="urn:org:josso:protocol:client:jaxws"

Replace 

<protocol:ws-service-locator endpoint="localhost:8080" /> 

with

<protocol:jaxws-service-locator  endpoint="192.168.1.60:8888"   wsdlLocation="file:////credideal/JBOSS-7.1/bin/josso-1.2.wsdl"/> 

Note - The wsdlLocation is the place where you have copied the josso wsdl & endpoint is the JBOSS gateway's ip address.

Change the Login url 

<gatewayLoginUrl>http://localhost:8080/josso/signon/login.do</gatewayLoginUrl>

to <gatewayLoginUrl>http://192.168.1.60:8888/josso/signon/login.do</gatewayLoginUrl>

Note - the url http://192.168.1.60:8888 is the gateway url

Change the Logout url 

<gatewayLogoutUrl>http://localhost:8080/josso/signon/logout.do</gatewayLogoutUrl>

to  <gatewayLogoutUrl>http://192.168.1.60:8888/josso/signon/logout.do</gatewayLogoutUrl>

Replace 

<value>http://localhost:8080/IDBUS</value>

to

<value>http://192.168.1.60:8888/IDBUS</value>

Configure the partner app

<agent:partner-app id="MySimplePartnerApp" context="/simple-partnerapp"/>

to

<agent:partner-app id="sso"  context="/PORTAL"  defaultResource="Index.jsp"/>

Note the context value should be same as the one specified in /credideal/JBOSS-7.1/standalone/deployments/PORTAL.war/WEB-INF/jboss-web.xml  in tag  <context-root>/PORTAL</context-root>

17) Copy the login-redirect.jsp fromt he josso sample war

18) Most important & last step modify web.xml

Edit <url-pattern> in <security-constraint> with the resources you want to protect .

Example

<security-constraint> <!-- Sample Security Constraint --> <web-resource-collection>

<!-- We're going to protect this resource and make it available only to users in "role1". --> <url-pattern>/RedirectPage.jsp</url-pattern> <url-pattern>/Event.jsp</url-pattern> <url-pattern>/Index.jsp</url-pattern> <url-pattern>/Framewrk/*</url-pattern> <url-pattern>/config/*</url-pattern> <url-pattern>/document/*</url-pattern> <url-pattern>/log/*</url-pattern> <url-pattern>/resources/*</url-pattern> <url-pattern>/STD/*</url-pattern> <url-pattern>/Webservice/*</url-pattern> <url-pattern>/Browser.jsp</url-pattern> <url-pattern>/Common.jsp</url-pattern>

<http-method>HEAD</http-method> <http-method>GET</http-method> <http-method>POST</http-method> <http-method>PUT</http-method> <http-method>DELETE</http-method>

</web-resource-collection> <auth-constraint> <role-name>role1</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>NONE</transport-guarantee> </user-data-constraint>

<!-- No roles required, it means that this are public resources ! Usefull to tell JOSSO that resources matching this security constraint should not be subject to SSO protection. --> </security-constraint>

Note - JOSSO agent will check for authenticated access to above url patterns & if not then it will redirect to Login page of the gateway.

Start JBOSS and try accessing the protected url , you should be redirected to the login page of the JOSSO Gateway.

Following are the files shared for your reference and the one you will require for installation

Download installation required files

Please revert in case you need any help in installation.

[ravindranr-blog]

Moving a Spring application from Jboss 7.0.2 to Tomcat 7.0.26

Here are steps to move a spring 2.5.6 application from Jboss 7 to tomcat 7.

The biggest issue is that tomcat doesn't come with its own JTA implementation.

Modify the spring version and the spring test jar version from 3.1.0 to 2.5.6.SEC02 for spring-expression and spring-asm updated to version 2.5.6.RELEASE Downgrading to 2.5.6 allows the JOTM tansaction manager to be used in the persistence.xml Remove all the Redirect attributes usages Change hibernate-jpa.jar file to be compile time in pom.xml Remove <mvc:business-context-bean /> call from the spring-business-context.xml Changed the TilesConfigurer with the patched up version to work with spring2.5.6 and tiles2.1.2

Put the following Java file in your project and configure this in your spring context xml file,

/* * Copyright 2002-2007 the original author or authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * *      http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */

package com.sumequal.web.tiles2;

import java.util.Enumeration; import java.util.Properties;

import javax.servlet.ServletConfig; import javax.servlet.ServletContext;

import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; import org.apache.tiles.TilesApplicationContext; import org.apache.tiles.TilesContainer; import org.apache.tiles.TilesException; import org.apache.tiles.access.TilesAccess; import org.apache.tiles.context.AbstractTilesApplicationContextFactory; import org.apache.tiles.definition.DefinitionsFactory; import org.apache.tiles.definition.digester.DigesterDefinitionsReader; //import org.apache.tiles.evaluator.el.ELAttributeEvaluator; import org.apache.tiles.factory.AbstractTilesContainerFactory; import org.apache.tiles.factory.TilesContainerFactory; import org.apache.tiles.preparer.BasicPreparerFactory; import org.apache.tiles.servlet.context.ServletTilesApplicationContext; //import org.apache.tiles.servlet.context.wildcard.WildcardServletTilesApplicationContextFactory; import org.apache.tiles.web.util.ServletContextAdapter;

import org.springframework.beans.factory.DisposableBean; import org.springframework.beans.factory.InitializingBean; import org.springframework.util.CollectionUtils; import org.springframework.util.StringUtils; import org.springframework.web.context.ServletContextAware; import org.springframework.web.servlet.view.tiles2.SpringLocaleResolver; import org.springframework.web.servlet.view.tiles2.TilesView;

/** * Helper class to configure Tiles2 for the Spring Framework. See * <a href="http://tiles.apache.org">http://tiles.apache.org</a> * for more information about Tiles, which basically is a templating * mechanism for JSP-based web applications. * * <p>The TilesConfigurer simply configures a TilesContainer using a set * of files containing definitions, to be accessed by {@link TilesView} * instances. * * <p>TilesViews can be managed by any {@link org.springframework.web.servlet.ViewResolver}. * For simple convention-based view resolution, consider using * {@link org.springframework.web.servlet.view.UrlBasedViewResolver} with the * "viewClass" property set to "org.springframework.web.servlet.view.tiles2.TilesView". * * <p>A typical TilesConfigurer bean definition looks as follows: * * <pre> * <bean id="tilesConfigurer"> *   <property name="definitions"> *     <list> *       <value>/WEB-INF/defs/general.xml</value> *       <value>/WEB-INF/defs/widgets.xml</value> *       <value>/WEB-INF/defs/administrator.xml</value> *       <value>/WEB-INF/defs/customer.xml</value> *       <value>/WEB-INF/defs/templates.xml</value> *     </list> *   </property> * </bean></pre> * * The values in the list are the actual files containing the definitions. * * @author Juergen Hoeller * @author Richard Jr Barabé * @since 2.5 * @see TilesView * @see org.springframework.web.servlet.view.UrlBasedViewResolver */ public class SpringTilesConfigurer implements ServletContextAware, InitializingBean, DisposableBean {

protected final static Log logger = LogFactory.getLog(SpringTilesConfigurer.class);

private final Properties tilesPropertyMap = new Properties();

private ServletContext servletContext;

private TilesApplicationContext tilesContext;

public SpringTilesConfigurer() { //            this.tilesPropertyMap.put( //                    AbstractTilesApplicationContextFactory.APPLICATION_CONTEXT_FACTORY_INIT_PARAM, //                    WildcardServletTilesApplicationContextFactory.class.getName()); this.tilesPropertyMap.put( TilesContainerFactory.PREPARER_FACTORY_INIT_PARAM, BasicPreparerFactory.class.getName()); this.tilesPropertyMap.put( DefinitionsFactory.LOCALE_RESOLVER_IMPL_PROPERTY, SpringLocaleResolver.class.getName()); //            this.tilesPropertyMap.put(TilesContainerFactory.ATTRIBUTE_EVALUATOR_INIT_PARAM, ELAttributeEvaluator.class.getName()); this.tilesPropertyMap.put(TilesContainerFactory.CONTAINER_FACTORY_MUTABLE_INIT_PARAM, Boolean.toString(false)); }

/** * Set the Tiles definitions, i.e. the list of files containing the definitions. * Default is "/WEB-INF/tiles.xml". */ public void setDefinitions(String[] definitions) { if (definitions != null) { String defs = StringUtils.arrayToCommaDelimitedString(definitions); if (logger.isInfoEnabled()) { logger.info("TilesConfigurer: adding definitions [" + defs + "]"); } this.tilesPropertyMap.put(DefinitionsFactory.DEFINITIONS_CONFIG, defs); } }

/** * Set whether to validate the Tiles XML definitions. Default is "true". */ public void setValidateDefinitions(boolean validateDefinitions) { this.tilesPropertyMap.put(DigesterDefinitionsReader.PARSER_VALIDATE_PARAMETER_NAME, Boolean.toString(validateDefinitions)); }

/** * Set the {@link org.apache.tiles.definition.DefinitionsFactory} implementation to use. * Default is {@link org.apache.tiles.definition.UrlDefinitionsFactory}, * operating on definition resource URLs. * <p>Specify a custom DefinitionsFactory, e.g. a UrlDefinitionsFactory subclass, * to customize the creation of Tiles Definition objects. Note that such a * DefinitionsFactory has to be able to handle {@link java.net.URL} source objects, * unless you configure a different TilesContainerFactory. */ public void setDefinitionsFactoryClass(Class<?> definitionsFactoryClass) { this.tilesPropertyMap.put(TilesContainerFactory.DEFINITIONS_FACTORY_INIT_PARAM, definitionsFactoryClass.getName()); }

/** * Set the {@link org.apache.tiles.preparer.PreparerFactory} implementation to use. * Default is {@link org.apache.tiles.preparer.BasicPreparerFactory}, creating * shared instances for specified preparer classes. * <p>Specify {@link SimpleSpringPreparerFactory} to autowire * {@link org.apache.tiles.preparer.ViewPreparer} instances based on specified * preparer classes, applying Spring's container callbacks as well as applying * configured Spring BeanPostProcessors. If Spring's context-wide annotation-config * has been activated, annotations in ViewPreparer classes will be automatically * detected and applied. * <p>Specify {@link SpringBeanPreparerFactory} to operate on specified preparer * <i>names</i> instead of classes, obtaining the corresponding Spring bean from * the DispatcherServlet's application context. The full bean creation process * will be in the control of the Spring application context in this case, * allowing for the use of scoped beans etc. Note that you need to define one * Spring bean definition per preparer name (as used in your Tiles definitions). * @see SimpleSpringPreparerFactory * @see SpringBeanPreparerFactory */ public void setPreparerFactoryClass(Class<?> preparerFactoryClass) { this.tilesPropertyMap.put(TilesContainerFactory.PREPARER_FACTORY_INIT_PARAM, preparerFactoryClass.getName()); }

/** * Set whether to use a MutableTilesContainer for this application. * Default is "false". */ public void setUseMutableTilesContainer(boolean useMutableTilesContainer) { this.tilesPropertyMap.put(TilesContainerFactory.CONTAINER_FACTORY_MUTABLE_INIT_PARAM, Boolean.toString(useMutableTilesContainer)); }

/** * Set Tiles properties (equivalent to the ServletContext init-params in * the Tiles documentation), overriding the default settings. */ public void setTilesProperties(Properties tilesProperties) { CollectionUtils.mergePropertiesIntoMap(tilesProperties, this.tilesPropertyMap); }

public void setServletContext(ServletContext servletContext) { this.servletContext = servletContext; }

/** * Creates and exposes a TilesContainer for this web application. * @throws TilesException in case of setup failure */ public void afterPropertiesSet() throws TilesException { TilesContainer container = createTilesContainer(); TilesAccess.setContainer(this.tilesContext, container); }

/** * Create a TilesContainer for this web application. * @param context this web application's ServletContext * @return the TilesContainer to expose * @throws TilesException in case of setup failure */ protected TilesContainer createTilesContainer() throws TilesException { ServletContextAdapter adaptedContext = new ServletContextAdapter(new DelegatingServletConfig()); TilesApplicationContext preliminaryContext = new ServletTilesApplicationContext(adaptedContext); AbstractTilesApplicationContextFactory contextFactory = AbstractTilesApplicationContextFactory.createFactory(preliminaryContext); this.tilesContext = contextFactory.createApplicationContext(adaptedContext); AbstractTilesContainerFactory factory = AbstractTilesContainerFactory.getTilesContainerFactory(this.tilesContext); return factory.createContainer(this.tilesContext); }

/** * Removes the TilesContainer from this web application. * @throws TilesException in case of cleanup failure */ public void destroy() throws TilesException { TilesAccess.setContainer(this.tilesContext, null); }

/** * Internal implementation of the ServletConfig interface, to be passed * to the wrapped servlet. Delegates to ServletWrappingController fields * and methods to provide init parameters and other environment info. */ private class DelegatingServletConfig implements ServletConfig {

public String getServletName() { return "TilesConfigurer"; }

public ServletContext getServletContext() { return servletContext; }

public String getInitParameter(String paramName) { return tilesPropertyMap.getProperty(paramName); }

public Enumeration<?> getInitParameterNames() { return tilesPropertyMap.keys(); } }

}

/WEB-INF/tiles-definitions.xml

downgraded from tiles 2.2.1 to 2.1.2

removed the following line from spring-business-context.xml

<bean id="validator" />

Changed version in persistence.xml from 2.0 to 1.0

After all this change, I've got the following issue,

21:14:56,369 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sumequal]] (MSC service thread 1-3) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in ServletContext resource [/WEB-INF/spring-business-context.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError

Then I've changed using two application context file, one for web and another for server configurations into one and configured that in ServletDispatcher init param. Everything worked fine.

[atm09td]

JBoss Application Server 7はJBoss AS 6をベースにせず、ノウハウだけを流用しコードはスクラッチから書きなおした新しいJBoss ASのリリースです。書きなおしているので良いところは残しつつ、今までのJBoss ASとは大幅に異なるリリースとなっています。 バージョン7ということでJBoss AS 7を選ぶ上位7つの理由を挙げてみます。 超高速 - 10倍以上の起動速度、世界最速のJava EE 6アプリケーションサーバ Java EE 6 - CDIによるカスタマイズ容易なプログラミングモデル 超軽量 - 16Mのメモリ指定でも起動 モジュール化 - アプリケーション空間の独立とクラスローダ地獄からの開放 管理容易性 - 新しい管理API、管理コマンドラインインタフェースとグラフィカルインタフェース ドメイン管理 - 複数のサーバをまとめて管理 テスト容易性 - 超高速コンテナとArquillianの組み合わせでコンテナテストも超高速 Lightningというコードネームの通り、本当にクソ速いです。僕が使っている普通のノートPC上ではチューニング無しで1.4秒で起動しますし、特に古いマシンやネットブックとかじゃなければ2秒以内で起動するでしょう。最速は第二世代Core i7クアッドコア i7-2600Kで0.706秒という記録が出ています。全ての記録やチューニング方法はAS7StartupTimeShowdownのページで見ることができますし、Wikiなので自由に追加して構いません。 AS7トップページからダウンロードできるのはJava EE 6 Webプロファイル版ですが、もしFullプロファイルが欲しいという人はダウンロードページへ。Java EE 6のサンプルが含まれている"Quick Starts"のダウンロードもここにあります。 合わせてSeam Forgeのデモビデオが公開されています。本当のJava EE 6は今日からスタートです！

JBoss AS 7.0.0.Final コードネーム "Lightning" リリース - nekopの日記