Increase Heap Memory in Websphere(97/285 technotes fpr 2015)

Method 1: Using the administrative console

Open the administrative console.

Navigate to Servers > Server Types > WebSphere application servers > <servername>

Navigate to Server Infrastructure > Java and Process Management > Process Definition

Navigate to Additional Properties > Java Virtual Machine > General Properties

Define the values (in MB) for ‘Maximum heap size’ and/or ‘Initial heap size’.

Restart the server.

Note: If the heap size is already low, the administrative console might not open. In such cases, use some other method to configure the heap size.

Method 2: By editing the configuration files

This method should be used with caution.

Search for a file named server.xml in your WebSphere installation.

Generally, the location of this file is as follows:

<profilehome>/config/cells/<cellname>/nodes/<nodename>/servers/<servername>/server.xml

Select the server.xml specific to your server and edit it to add/modify/delete the attributes @initialHeapSize and @maximumHeapSize of the element <jvmEntries> The value of these attributes is the heap size in MB.

For example:

<jvmEntries ... initialHeapSize="2048" maximumHeapSize="3072" ...>
 ...
 </jvmEntries>

Restart the server after saving the changes to server.xml.

References:

https://blakboard.wordpress.com/2013/05/15/how-to-configure-heap-size-for-websphere-application-server/

How to log outgoing/incoming SOAP Requests in Websphere? (61 of 285 technotes for 2015)

Trace for SOAP WS messages can be enabled by following these steps on Websphere 7 administration console:

• Go to administration console
• Go to: Servers -> WebSphere application servers -> server > Change Log Detail Levels
• In the package tree find the package com.ibm.ws.websvcs.trace, click on package name and choose ‘All Mesasges and Traces’, as result you should have log details set as below:

*=info: com.ibm.ws.websvcs.trace.*=all

• Click on 'OK’ and then Save the changes.

SOAP request/responses can now be found in trace.log on your appl. server.

References: http://bit.ly/1J4dSy5

Managed node fails to synchronize (27 of 285 technotes for 2015)

Access is denied for the getRepositoryEpoch operation on ConfigRepository MBean because of insufficient or empty credentials.

In Administrative console:

1. SSL certificate and key management -> Key set groups ->Select Key set group name -> uncheck the box for “Automatically generate keys”
   
   Clear the Automatically generate keys option.
   
2. From the Key set groups -> check key set Group name and hit Generated Keys tab.
   
3. Click OK and Save to save the changes to the master configuration.
   
4. Stop the dmgr
   
5. On dmgr side delete the contents under wstemp, temp and config/temp folder from <profile_root>
   
6. Start the dmgr
   
7. Stop the Node/Server using stopNode/stopServer commands from the <profile_root>/bin of AppServer
   
8. Manually synchronize the node by running syncNode.sh from <profile_root>/bin, since security is enabled then please run following command
   
   syncNode.sh <DMgr_hostName> <SOAP_PORT_of_DMGR> -username <username> -password <password>
   
9. Start the node and server.
   
10. Logon to Dmgr Administrative console and check the Node/Server availability.

Reference: http://www-01.ibm.com/support/docview.wss?uid=swg21405907

Creating Windows Service to start / stop Websphere Application Server(23 of 285 technotes for 2015)

To Remove Windows Service

Go to d:ibmwebsphereappserverbin
d:...>wasservice.exe -remove “name of service” (from services)

To Add new Windows Service

Go to d:ibmwebsphereappserverbin

d:.…>WASService.exe -add “<service_name>” -serverName “<server_name>” -profilePath “<profile_path>” -logRoot “<log_server_path>” -logFile “<log_file_path_name>” -encodeParams -stopArgs “-username <user_name> -password <password>” -startType automatic -restart false

eg:

WASService.exe -add “CTHIX_DMGR” -serverName “dmgr” -profilePath “D:IBMWebSphereAppServerprofilesCTHIX_DMGR” -logRoot “D:IBMWebSphereAppServerprofilesCTHIX_DMGRlogsdmgr” -logFile “SystemOut.log” -encodeParams -stopArgs “-username wasadmin -password Admin.1” -startType automatic -restart false

For more info - http://ibm.co/1HZv9b9

Configuring Active Directory in Websphere Application Server (22 of 285 technotes for 2015)

http://bit.ly/1FrSyza

How to create a WSRR profile using a response file? (19 of 285 technotes for 2015)

Run:

D:IBMWebSphereWSRRbin>manageprofiles.bat–response WSRR_Node.txt

Sample response file - ‘WSRR_Node.txt’

create
profileName=test_WSRR
serverName=WSRRServer
cellName=WSRRCell
nodeName=WSRRNode
hostName=DEVAPPESB4
profilePath=D:/IBM/WebSphere/WSRR/profiles/test_WSRR
templatePath=D:/IBM/WebSphere/WSRR/profileTemplates/default.wsrr
enableAdminSecurity=false
wsrrDbAlreadyConfigured=false
wsrrDbCreateNew=false
wsrrDbDelayConfig=true
wsrrDbOutputScriptDir=dbscripts
wsrrDbType=MSSQLSERVER_MICROSOFT
wsrrDbJDBCClasspath=D:/IBM/WebSphere/WSRR/jdbcdrivers/SQLServer
wsrrDbSysUserId=testwsr
wsrrDbSysPassword=
wsrrDbHostName=10.20.30.40
wsrrDbServerPort=1533
wsrrDbName=DWSRRDB01
wsrrDbUserId=hixwsr
wsrrDbPassword=
wsrrDbSchemaName=WSRR
actDbSchemaName=WSRRACT
sibDbSchemaName=WSRRSIB
configureBSpace=true

How to create a Websphere Profile using a response file? (18 of 285 technotes for 2015)

Execute:

D:DataIBMWebSphereESBbin>manageprofiles.bat-response  node.txt

Sample response file below - ‘node.txt’

create
templatePath=D:/IBM/WebSphere/ESB/profileTemplates/default.esbserver
profileName=TEST_ESB
serverName=ESBServer
cellName=ESBCell
nodeName=ESBNode
enableAdminSecurity=false
dbServerPort=51000
ceiDbName=event
ceiDbAlreadyConfigured=false
configureBPC=false
dbCreateNew=false
dbCommonForME=true
fileStoreForME=false
dbHostName=172.31.1.188
dbType=DB2_UNIVERSAL
dbName=CMNDB
dbDelayConfig=true
dbAlreadyConfigured=false
applyPerfTuningSetting=standard
dbUserId=testesb
dbPassword=
configureBSpace=true
configureBRM=false
dbJDBCClasspath=D:/Data/TESTESB/jdbc
omitAction=defaultAppDeployAndConfig,samplesInstallAndConfig

How to create a Websphere profile in command line and add as Windows Service? (17 of 285 technotes of 2015)

Step1: WAS – Application server Installation path

D: IBMWebsphereAppserver

Step 2: Go to WAS_HOMEbin location (D:IBMWebsphereAppserver) and run the below cmd

manageprofiles.bat -create -profileNameTEST_CP -hostName DEVAPPPORTAL1 -cellName cell01 -nodeName Node01 -serverName CPServer -enableAdminSecurity -false -winserviceCheck false

Step 3: Once the profile is created add as Windows Service.

From the WAS_HOMEbin location (D: IBMWebsphereAppserver) and run the below cmd

WASService.exe -add TEST_CP -servername CPServer -profilePath D:IBMWebSphereAppServerprofilesTEST_CP

Secure Web Services (13 of 285 technotes for 2015)

Why Web Service security is so important nowadays

1. Interaction between communicating partners increasing from Intranet to Internet
2. Communicating partners are more likely to interact with each other without need for establishing business or human relationship first.
3. Program to program communication increases.
4. Large number of interactions.

Most common way of Interaction - SSL (Secure Socket Layer) used with HTTP i.e. HTTPS.

How to modify Messaging Engine Policy in Websphere? (12 of 285 technotes for 2015)

Messaging Engine Policy Assistance

To use this feature you:

1. Select Service Integration -> Buses in the Admin Console navigation
2. Click the link of the bus which you want to configure a messaging engine policy for.
3. Click on Bus Members in the properties for the bus (This is where it is a little counterintuitive)
4. Click on the link for one of the bus members (This page shows the policy assistance is disabled but you have to go down a level to enable it)
5. Check the box next to the messaging engine for the bus member and click the Enable policy assistance button.
6. Run through the wizard to configure the policy.

Reference: http://ibm.co/1HSeppn

How to change the Default Core Group policy of a Cell in Websphere? (11 or 285 technotes for 2015)

Goto System Administration –> Cell –> Local Topology –> DefaultCoreGroups –> Policy

What are the different deployment topologies in IBM Websphere (10 of 285 technotes for 2015)

IBM Websphere comes with wizards for different topologies.

Different Topologies

Bronze - Single Cluster Topology

• The bronze topology is suitable for a solution that comprises only synchronous web services and synchronous SCA invocations, preferably with short-running flows only.
  
• Java Message Service (JMS), and MQ messaging bindings do not support multiple messaging engines in the same cluster
  

Silver - Remote Messaging

• The silver topology is suitable for a solution that uses long-running processes, but doesn’t need CEI, message sequencing, asynchronous deferred response, JMS or MQ bindings, or message sequencing mechanisms. 
  

Gold - Remote Messaging & Support

• The golden topology is suited for all the remaining cases, in which asynchronous processing plays a significant role in the solution 
  

---

References - http://www.ibm.com/developerworks/websphere/library/techarticles/1008_metzger/1008_metzger.html

http://www-01.ibm.com/support/knowledgecenter/SSQH9M_7.0.0/com.ibm.websphere.wesb.doc/doc/cpln_top_types.html?lang=no

Schema Names of SIB Tables created by Websphere Service Integratoin Bus(9 of 285 technotes for 2015)

The tables created within the CMNDB by the Service Integration Bus Messaging Engines are mentioned below. Whenever there is some issue in the SIB not able to start the Messaging Engine, it is safe to delete all the files that belong to the schema’s below. Generally we do “like ‘CMNS%” and “like ‘CMNC%’” and delete all the tables.

Messaging Engine - has failed to gain an initial lock on the data store (8 of 285 technotes for 2015)

Messaging Engine - is attempting to obtain an exclusive lock on the data store.
Messaging Engine - has failed to gain an initial lock on the data store.

Root Cause - 

An unclean shutdown could left lock owner information down to the database level. so when you bring up the server, it trying to get the same lock, but in the sibowner table, you already had one entry which tell the websphere process server, the lock already have an owner.

Action

Please delete all the tables with schema name like “CMN%” i.e. 

Update ports of a Websphere Node (7 of 285 technotes for 2015)

Goto the node of the WAS profile and update the serverindex.xml

<WAS_INSTALL>profiles<profile_name>configcells<cell_name>nodes<node_name>

eg:

C:IBMWebSphereAppServerprofilesCustom01configcellsdmgr1Cell01nodesesbNode02

Manage Profile Websphere (6 of 285 technotes for 2015)

<was_root>/bin/manageprofiles.sh -listProfiles

wil list the profiles

e.g

[appsrv01]

to remove the profile type:

<was_root>/bin/manageprofiles.sh -delete -profileName appsrv01

result:

INSTCONFSUCCESS: Success: The profile no longer exists.

Manually update Datasource in Websphere Application Server(4 of 285 technotes for 2015)

• Open “Resources.xml” file (see below for the locations)
  
• Search for “resources.jdbc:DataSource” and 
  
• Update the “resourceProperties”
  

Clean up Default WESB System Applications. (3 of 285 technotes for 2015)

Several system applications are provided as part of the vanilla installation of WebSphere Enterprise Service Bus (WESB). However, not all of the default system applications are required for every WESB runtime topology. In an effort to reduce the number of ear files in the WESB environment the below 9 applications may be removed without any adverse effect to WESB environment  Eight/Nine of the applications are related to Business Space and one application is a RAL (Remote Artifact Loader) app.  I recently performed this clean up on a WESB 7.5 environment with excellent success.  Please note that if you are using Business Space, or RAL- do not remove these applications.
The following 9 WESB System Application Ears can be removed:
Business Space Applications

1. BPMAdministrationWidgets_esb_env2.AppTarget
2. BSpaceEAR_esb_env2.AppTarget
3. BSpaceForms_esb_env2.AppTarget
4. BSpaceHelp_esb_env2.AppTarget
5. PageBuilder2_esb_env2.AppTarget
6. REST Services Gateway
7. REST Services Gateway Dmgr
8. mm.was_esb_env2.AppTarget
9. wesbWidget_esb_env2.AppTarget
10. RemoteAL61 (Remote Artifact Loader)

DO NOT REMOVE

1. persistentLkMgr- manages event sequencing
2. sca.sib.mediation- provides mediation services (see pg 97 in linked redbook)
3. wpsFEMgr_7.0.0- provides Failed Event Management Services.

Reference - http://jubergconsulting.gowithclick.com/_blog/websphere/post/Clean_up_default_WESB_System_Applications/

What is "persistentLkMgr" Persistent LK Manager in IBM ESB 7.5? (2 of 285 technotes for 2015)

persistentLkMgr is an application that is installed automatically when IBM ESB 7.5 is installed.

This application is used mainly in Event Sequencing. persistentLkMgr application which is responsible for writing the lock entry in the PERSISTENTLOCK DB table.

For more information please read the article.