websphere-8

问题 I am new to JMS and the Websphere server and I am trying to access a JMS queue configured on Websphere Application Server 8 from my Java code. I am not able to understand exactly what value should be set for Context.INITIAL_CONTEXT_FACTORY. Should it be the fully qualified class name of the class or something specific to the application server? Hashtable environment = new Hashtable(); environment.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");

问题 In our existing application properties file is embedded in a jar file ,we decided to move properties file outside of ear(application) , what is the best place to put properties file in IBM websphere 8.5 ? so that i can retrieve path with WAS Environment variables and file should be available to all nodes in a cluster .. 回答1: You can use the classloader directories for that. I would use the directory classes (you might need to create) under $WEBSPHERE_HOME/AppServer/classes and drop your

问题 I am facing classpath issue related to jars in WAS plugins folder. My application had IBM specific code to get compiled using the com.ibm.ws.runtime jar as mentioned below. Location : C:\Program Files\IBM\Websphere\AppServer\Plugins Source code: Object obj = (( com.ibm.ws.rsadapter.jdbc.WSJdbcUtil.getNativeConnection (( com.ibm.ws.rsadapter.jdbc.WSJdbcConnection )connect))); Both classes are available in com.ibm.ws.runtime Compiled successfully by including IBM runtime.jar in classpath of

问题 I have deployed the RESTful application using Apache Wink packaged in EAR on WebSphere 8.5.5.2 ND. When the application starts it gives me the " Initialization successful " message: [5/14/15 15:56:03:588 CDT] 0000006d RestServlet I org.apache.wink.server.internal.servlet.RestServlet getApplication The system is using the my.domain.mobile.rest.RestfulResourceLoader JAX-RS application class that is named in the javax.ws.rs.Application init-param initialization parameter. [5/14/15 15:56:03:605

问题 The JAXWS implementation within IBM WebSphere 7 and 8 appears to have some problems when it comes to soap handlers and large MTOM attachments. It appears that the entire message, including all attachment binary content, is read into memory when getMessage() is invoked on the SOAPMessageContext object. This can very easily cause the JVM to run out of available memory. @Override public boolean handleMessage(SOAPMessageContext context) { SOAPMessage soapMsg = context.getMessage(); ... } In the

问题 I have an application (.war) deployed in a Websphere Application Server v8. This app consists in a web application which is accessed by browser. Now I have an IP Address that I want to ban but I don't find the option in the Administrative Console. Where I should ban this ip for to avoid the access this specifically application? 回答1: In WebSphere you have 2 options (depends if you directly access app server or through http server): 1 Directly via WebSphere admin console. Go to: Application

问题 I am having troubles with integration WAS [ND/BASE] 8.5 or WAS [ND/BASE] 8.5.5 with Worklight Studio 6.0 in Eclipse or in RAD 9. What I did: Installed RAD 9 Installed WAS TE 8.5.5, created AppSrv profile, secured Installed Worklight 6.0 on the WAS - worklight console application installed fine Installed Worklight Studio 6.0 in RAD 9 Created new Hybrid project in fresh workspace Now, I am trying to have the project run on WAS 8.5.5 (full profile) server, and Worklight Studio 6 does not support

问题 Where do I set the user context Websphere uses when it calls a @Startup EJB? I have a Java EE application with a startup EJB, and I know that it sets a user when calling the EJB, since the call fails due to missing roles. However, I couldn't find where to set the user. 回答1: The EJB spec states that session bean @PostConstruct methods are called in an unspecified security context, and WebSphere does not document a specific security context or allow it to be configured. In practice, singleton

问题 Where do I set the user context Websphere uses when it calls a @Startup EJB? I have a Java EE application with a startup EJB, and I know that it sets a user when calling the EJB, since the call fails due to missing roles. However, I couldn't find where to set the user. 回答1: The EJB spec states that session bean @PostConstruct methods are called in an unspecified security context, and WebSphere does not document a specific security context or allow it to be configured. In practice, singleton

问题 When an ear would contain two ejb modules modulea.jar and moduleb.jar. And modulea.jar contains an @Startup ejbX, that calls another ejbY, which is not an @Startup ejb, from moduleb.jar during the startup of the bean X it is required that moduleb.jar is started first as otherwise the app server is not able to inject X into Y. But how to ensure that moduleb.jar is started first? Currently I have this problem in WebSphere, but I can't seem to find a way to enforce an order. Is there something