Posts

Websphere Server topologies

Image
Single-server topology: Provides an application server and a Web site. Initially, a single instance is configured to use an internal database. Convert to a cluster or server farm to improve capacity and availability. WebSphere Portal, WAS, and the database are all installed on the same server. Optionally configure a Web server, with IBM WAS's HTTP plug-in to... Serve static resources Provide plug-in point for a corporate  SSO agent  in the event that WebSphere Portal participates in a global SSO domain Standalone server topology The stand-alone scenario is different from the single-server since the database server, LDAP server, and Web server software are installed on different physical servers than the IBM WebSphere Portal. This configuration enables you to distribute the software in the network and therefore distribute the processing load. For a stand-alone configuration, we can use an existing, supported database in the network and an existing, supp...

Start Websphere Application Server automatically with shell scripting

#!/bin/sh  # # script to start and stop WebSphere Application Server 5.x # WAS_HOME="/opt/WebSphere/AppServer" # WAS install dir  SERVERS="server1 MyAppServer" # list of app servers  if [ ! -d "${WAS_HOME}" ]; then    echo "$0: ${WAS_HOME} does not exist, aborting" >&2    exit 1  fi  case "$1" in  ’start’)  # increase resource limits    ulimit -n 1024    ulimit -s 16384     for s in ${SERVERS}; do        ${WAS_HOME}/bin/startServer.sh $s     done  ;;  ’stop’)      for s in ${SERVERS}; do         ${WAS_HOME}/bin/stopServer.sh $s     done     ;;  ’status’) ${WAS_HOME}/bin/serverStatus.sh -all   ;;  *)   echo "Usage: $0 " <start|stop|status>     exit 1     ;; esac

WAS Certification ( Architecture)

Image
Apply design considerations of IBM WebSphere Application Server, V7.0 when installing an enterprise environment (e.g., LDAP, database servers, WebSphere messaging, etc.)   The following topics are important to consider when designing a WebSphere Application Server deployment. They will most likely impact your design significantly: Scalability - Scalability, as used in this book, means the ability of the environment to grow as the infrastructure load grows. Scalability depends on many different factors such as hardware,operating system, middleware, and so on. Caching - WebSphere Application Server provides many different caching features at different locations in the architecture. WebSphere Application Network Deployment provides caching features at each possible layer of the infrastructure: Infrastructure edge:   Caching Proxy provided by the Edge Components WebSphere Proxy Server HTTP server layer:   Edge Side Include (ESI) fragment caching capabilities provi...