Ivica Loncar's List: websphere

• ClassNotFoundExceptions from IBM Software Development Kit (SDK) version 6.0 doing LDAP searches.
• java.lang.ClassNotFoundException: class com.sun.jndi.ldap.obj.Marshalled
   ToObject not found
   java.lang.ClassNotFoundException: class com.sun.jndi.ldap.obj.AttrsToCorba
   not found

• AdminApp interacts with WebSphere to allow scripted and interactive querying of and changes to WebSphere applications. The particular usefulness that I want to record here is how to use AdminApp interactively to help fix up a scripting problem.

    

  Consider the example where an Ant target fails to install an EAR, displaying a message indicating that there was insufficient information for the MapEJBRefToEJB option. The WebSphere documentation doesn't make it easy to figure out what should be provided.

    

  Running wsadmin interactively, the command

  $AdminApp taskInfo /opt/WebSphere/AppServer/installableApps/SomeEAR.ear MapEJBRefToEJB

  gives you the syntax required for the MapEJBRefToEJB option and the relevant values after applying default bindings.

• Consider the example where an Ant target fails to install an EAR, displaying a message indicating that there was insufficient information for the MapEJBRefToEJB option. The WebSphere documentation doesn't make it easy to figure out what should be provided.

    

  Running wsadmin interactively, the command

  $AdminApp taskInfo /opt/WebSphere/AppServer/installableApps/SomeEAR.ear MapEJBRefToEJB

  gives you the syntax required for the MapEJBRefToEJB option and the relevant values after applying default bindings.

• IBM WebSphere scripting with wsadmin: containment paths, configuration IDs and object names
• anybody knew the difference between containment paths, configuration IDs and object names in WebSphere's scripting interface wsadmin

• Installing and configuring WebSphere Portal V6.0 Servers for development with Rational Application Developer V7.0 and Rational Software Architect V7.0

• IBM WebSphere Developer Technical Journal: Configuring single sign-on using Tivoli Access Manager and WebSphere Port

• The timeout.resume.session parameter should be set to "true" in cases where you do not wish for users to see the ErrorSessionTimeout screen and have to re-login to WebSphere Portal once the inactivity timeout for the WebSphere Portal application is exceeded. An example scenario would be if you were using an External Security Manager (ESM) and Trust Association Interceptor (TAI) to handle authentication for WebSphere Portal. You could take advantage of the security invalidation and timeout features of the ESM and TAI to control when the session gets invalidated (and thus when the user gets redirected to ESM's login page to re-login).

• Customizing a server-side Java Authentication and Authorization Service authentication and login configuration

• Developing programmatic logins with the Java Authentication and Authorization Service

• Portal configuration services

• This guide provides a comprehensive step-by-step approach to building an IBM® WebSphere® Portal version 6.1.0.3/6.1.5 cluster within a single cell.
• Included are the steps necessary to build a two-node portal cluster within the same cell. This also includes configuration to an external database, a Lightweight Directory Access Protocol (LDAP) user registry, and a remote Web server.

• PyMQI is a production-ready Python extension for IBM’s messaging & queueing middleware, WebSphere MQ (formerly know as MQSeries). This allows Python programs to make calls directly to MQI to connect queues and get/put messages on them etc.

• An Open Source MQTT Broker
• Mosquitto is a message broker that implements the MQ Telemetry Transport protocol version 3. MQTT  provides a lightweight method of carrying out messaging using a  publish/subscribe model.

• visualvm and websphere 7 to work together on my local windows desktop

• Script libraries can be used to perform a higher level of wsadmin functions than can be done using a single wsadmin command.
• The script libraries are located in  WAS_INSTALL_ROOT/scriptLibraries directory. These libraries are loaded when wsadmin starts and are readily available from the wsadmin command prompt or to be used from the customized scripts.
• The script libraries are located in  WAS_INSTALL_ROOT/scriptLibraries directory. These libraries are loaded when wsadmin starts and are readily available from the wsadmin command prompt or to be used from the customized scripts.
• wsadminlib.py is a large python file containing hundreds of methods to help simplify configuring the WAS using scripting.
• wsadminlib.py  wsadminlib.py is a large python file containing hundreds of methods to help simplify configuring the WAS using scripting.
• wsadminlib.py is a large python file containing hundreds of methods to help simplify configuring the WAS using scripting. A wide variety of methods have been developed. These methods perform tasks such as creating servers, starting servers, creating clusters, installing applications, proxies, core groups, core group bridge, dynacache, shared libraries, classloaders, replication domains, security, BLA, JDBC, etc.
• These methods perform tasks such as creating servers, starting servers, creating clusters, installing applications, proxies, core groups, core group bridge, dynacache, shared libraries, classloaders, replication domains, security, BLA, JDBC, etc.

5 more annotations...

• Sample Scripts for WebSphere Application Server

• HA of an MQLink between SIBus and WMQ

• Another practical piece of advice is to never use "wsadmin -f" to test your scripts. Wsadmin takes eternity to come up, so running it every time you want to run your scripts is simply counterproductive. Instead, load it once and then run your script using Python "execfile" function. Don't forget to call reload function for all modules that are part of your applications, otherwise you won't see the changes until your re-start wsadmin.

• File-based User Authentication Under WebSphere 6
• lution is to use the sample cus