WebSphere FAQs

This section lists to troubleshoot specific properties that you may encounter while installing Kony Fabric (MobileFabric) on WebSphere.

Release V8 SP4, V8SP3, V8SP2, V8SP1, V8, 7.3, 7.2, 7.1, 7.0, 7.0.1, 6.5, and 6.5.x

How to Update an Application Manually if the Application Fails to Start After Installation

After applying any 7.0.1.x patches on WebSphere, if any of the deployed applications fails to get started, you need to update the required applications again.

To update applications, follow these steps:

1. Log in to WebSphere Admin Console.
2. Go to the Applications tab and click WebSphere enterprise applications. You can see the list of applications deployed.
3. Choose the application to update and click Update.

   

4. Provide the path for the .ear file and click Next.

   

5. Choose Detailed option and click Next.

   

6. Use the default option and click Next.

   

7. Select the module and click Next.

   

8. Use the default option and click Next.

   

9. Map the shared libraries as below and click Next.

   

10. Map the shared libraries relationships as below and click Next.

    

11. Map the application to appropriate virtual host and click Next.

    

12. Default context root appears in the Context Root field. Check value and click Next.

    

13. The Map JASPI provider page appears. Select the check boxes for application and module and click Next.

    

14. The Metadata for Modules page appears. Select the check box in the metadata-complete attribute and click Next.

    

15. The Display Module Build Ids page appears. Click Next.

    

16. The Summary page appears with all the details. Click Finish to start update.

How to Enable Kony Fabric (MobileFabric) to Communicate to Third Party (SSL)

When Kony Fabric (MobileFabric) is installed on WebSphere Server, and an administrator wants to enable Kony Fabric to communicate to third party hosted on SSL (for example, Salesforce), the admin needs to import the relevant SSL certificates into WebSphere trust store.

To import cert, follow these steps:

1. Log in to WebSphere Admin Console.
2. Go to the Security tab.
3. Click SSL certificate and key management.
4. Go to Key stores and certificates > NodeDefaultTrustStore > Signer certificates.
5. Click on Add and click on Retrieve from port.
6. Enter the hostname and port - for example: <login.salesforce.com>   and   <443>.
7. Enter some alias - for example, salesforce
8. Click Retrieve signer information.

   

9. Click Apply.
10. Click Save at the top pane.

How to Configure Cluster Setup

While installing Kony Fabric (MobileFabric) on a WebSphere cluster setup, if an admin selects a Server under the Available Server Groups, the installation fails.

To install Kony Fabric on a WebSphere cluster setup, select a cluster or standalone server which is not part of any cluster from the available server groups displayed, shown below.

• Windows:

  

• Linux:

  

  When a WebSphere Server is part of any cluster in WebSphere and if an admin selects only that server during installation of Kony Fabric installation rolls back.

  This is limitation from WebSphere. It does not allow to deploy an application to one of the servers of cluster. It only allows an admin to deploy the application to entire cluster. So an admin has to select cluster instead of individual member in cluster during Kony Fabric installation.

How to Configure Heap Size - WebSphere

Configuring Heap Size for Single Node

When installing Kony Fabric with all components (console, identity and integration) on WebSphere, allocate minimum of 6 GB of heap size for successful installation.

To configure heap size, follow these steps:

1. Log in to WebSphere Admin Console.
2. Go to Servers > Server Types > WebSphere application servers.
3. Click Application Server. (For example, server1, it is the default server created with WebSphere installation).

   

4. Go to Server Infrastructure section, expand Java and Process Management and click Process definition.
5. Go to Additional Properties, click Java Virtual Machine.
6. Enter 6144 as initial heap size.
7. Enter 7168 as maximum heap size.
8. Save the configuration.

Configuring Heap Size for Multinode

1. Log in to Deployment Manager Admin Console.
2. Go to System administration Servers > Deployment manager > Process definition > Java Virtual Machine.

   

3. Enter 4096 as initial heap size.
4. Enter 6144 as maximum heap size.
5. Save the configuration.

6. Go to Servers > Clusters > WebSphere application server clusters.

7. Click  <clusterName> and click cluster members.

   

8. Go to each member of cluster and update heap settings, shown below:

   

How to Configure middleware.home as a -D parameter on WebSphere

Important: From Kony MobileFabric 7.x release onwards, middleware.home is deprecated and not supported.

When a user installs only integration service on WebSphere and would like to use it as a standalone server (without integrating to MobileFabric) for studio apps, the user needs to configure middleware.home as a -D parameter for studio apps to work. These configuration also required when sync is deployed on same WebSphere instance.

Note: The middleware_home folder can be copied from installer home location.

1. Go to <user install directory>/middleware_home>  folder and copy the middleware_home folder. This step is required only if integration service is installed remotely.
2. Paste the  middleware_home  folder to your WebSphere instance. This step is required only if integration service is installed remotely.
3. Provide  -Dmiddleware.home=<path to middleware_home folder>  in WebSphere instance, shown below:

   

   Note: In case of multi node setup, copy the middleware_home folder to all appropriate nodes at same location.

Publish Fails when Sync is installed on same WebSphere Server Instance as Middleware

When installing Sync on WebSphere, if sync is being installed on same WebSphere node as middleware server, app publish fails.

Configure middleware.home as specified in Configuring middleware.hom as a -D parameter on WebSphere.

How to Configure Metrics on WebSphere

Note: From 7.3 release, the MobileFabric Installer configures Metrics during the installation.

In case of upgrade from versions prior to 7.3, follow these manual steps to configure Metrics.

MobileFabric installer deploys the  Metrics.ear  to WebSphere but will not add any JMS configuration in server. To enable metrics, add the required configurations manually.

To enable metrics.ear configuration after installation via installer, follow these steps:

1. Uninstall the metrics.ear file, which got deployed during installer.
2. Go to <install directory>/deployments folder and check that  metrics.ear file is present.

3. Follow the steps mentioned in sections Configure JMS and Deploy metrics.ear of 6.X in the following link to Manual Installation Guide - WebSphere.

   For more information on this, refer to Configure Metrics on WebSphere.

To disable metrics.ear configuration after installation via installer, follow these steps:

1. Modify the metrics.logging property to  false  in middleware.properties in the admin.ear, services.ear and middleware_home folder in all the WebSphere nodes.

   For example, path for the middleware properties file is as follows:

   • <WAS_INSTALL_ROOT>/AppServer/profiles/AppSrv01/installedApps/WIN-MDP5BJ0RCA3Node01Cell/admin.ear/admin.war/WEB-INF/middleware/middleware-bootconfig/middleware.properties
   • <WAS_INSTALL_ROOT >/AppServer/profiles/AppSrv01/installedApps/WIN-MDP5BJ0RCA3Node01Cell/services.ear/services.war/WEB-INF/middleware/middleware-bootconfig/middeware.properties
   • <WAS_INSTALL_ROOT>/AppServer/profiles/AppSrv01/installedApps/WIN-MDP5BJ0RCA3Node01Cell/middleware.ear/middleware.war/WEB-INF/middleware/middleware-bootconfig/middleware.properties

   • <USER_INSTALL_DIR>/middleware_home/middleware/middleware-bootconfig/middleware.properties

2. Restart WebSphere application server.

How to Configure WebSphere Shared Lib Mapping

How to Configure WebSphere Shared Lib Mapping, refer to the Deploying SyncConsole War File and the Deploying Syncservice WAR File sections in the following link to Kony Fabric Sync Installation on Windows - (Manual Installation)- WebSphere Guide.
For more information on this, refer to Deploying Kony MobileFabric Sync Server.

How to Configure  SSL Configuration for WebSphere 8.5.5.5

To use a signed SSL certificate from a trusted certificate authority, follow these steps:

1. Ensure that you have a Key Store file.
   For example: _.konylabs.net.2016.jks
2. Log in to your WebSphere Admin Console and navigate to Security > SSL certificate and key management  > Key stores and certificates.
3. Configure NodeDefaultKeyStore  and  NodeDefaultTrustStore details as follows:
   1. Find NodeDefaultKeyStore and NodeDefaultTrustStore under Key stores and certificates.
   2. Edit them as described below:
      1. Click on NodeDefaultKeyStore and edit the following fields:
         • Path: <give the path to your Key Store file>. For example, <${CONFIG_ROOT}/cells/.../nodes/.../_.konylabs.net.2016.jks>
         • Password: <give the password of your Key Store>. For example, <changeit>
         • Type: <give the type of your Key Store>. For example, <jks>
      2. Click on NodeDefaultTrustStore and edit the fields in a similar way as described above.

         Note: You can use the same Key Store details that you used for NodeDefaultKeyStore to configure your NodeDefaultTrustStore, if the Key Store has the Personal Certificate and the Signer Certificate.

4. To extract the certificate, navigate to NodeDefaultKeyStore > Personal certificates, then select your certificate and click Extract.
5. Provide a Certificate file name to which you want to extract to. For example, konylabs.crt.
6. Find the konylabs.crt file created at: Websphere/AppServer/profiles/AppSrv…/etc
7. Import the certificate into cacerts:

   Import the konylabs.crt into the local JRE’s trust store - cacerts using keytool.

   Command (run as administrator):

   >keytool -import -trustcacerts –alias *.konylabs.net -file konylabs.crt -keystore cacerts

8. Restart your WebSphere Application Server.
9. Run the Kony Fabric Consolidated Installer. When asked for Key Store and Trust Store details, choose   _.konylabs.net.2016.jks  as both your Key Store and Trust Store file, provide corresponding password.

To user a self-signed SSL certificate, follow these steps:

WebSphere self-signed SSL certificate needs to be imported into the IBM java keystore for https hosted Kony Fabric to work properly.

Path to keystore: <WAS_INSTALL_ROOT >/AppServer/java/jre/lib/security/cacerts

1. 1. Execute this following command to import the cert:

   keytool -import -trustcacerts -alias "win-mdp5bj0rca3" -file C:/WIN-MDP5BJ0RCA3.crt -keystore <WAS_INSTALL_ROOT >/AppServer/java/jre/lib/security/cacerts

2. Restart your WebSphere Application Server.

How to Configure ulimit Parameter Size in CentOS

While installing Kony Fabric on WebSphere Cluster setup on CentOS, if the system throws the following error, increase the ulimit value on WebSphere instance

java.security.PrivilegedActionException: java.io.IOException: Too many open files .... Caused by: java.io.IOException: Too many open files....

To increase ulimit size in WebSphere, follow these steps:

1. Navigate to /opt/IBM/WebSphere/wp_profile/bin/setupCmdLine.sh (in case you are running Portal as root).
   Otherwise, you need to set this in your user's profile.

   Note: The limit can be appropriate for your environment.

2. Set ulimit -n 40000 before starting WebSphere Portal.
3. Restart WebSphere Server.

How to Configure WAS_INSTALL_ROOT in WebSphere Variables at Cell Scope Level

When user clicks test connection for data source in WebSphere Console, the following error occurs:

The test connection operation failed for data source XXX on server dmgr at node bpmtestCellManager01 with the following exception: com.ibm.wsspi.runtime.variable.UndefinedVariableException: Undefined variable WAS_INSTALL_ROOT. View JVM logs for further details.

To configure WAS_INSTALL_ROOT in WebSphere, follow these steps:

1. Add WAS_INSTALL_ROOT in WebSphere Variables at Cell Scope level.
2. Check connection again. The system displays the following test successful message:

   The test connection operation for data source sampledatasource on server dmgr at node testCellManager01 was successful.

How to Configure Validate Existing Pooled Connections

When Kony Fabric hosted on WebSphere is kept idle for 10 hours or more, and if you try to hit the Kony Fabric Console URL (for example, http://<IP address>/mfconsole), the system throws an error page for the first hit. To avoid this behavior, add these following steps at the end of installation steps:

1. Log in to WebSphere Admin Console.
2. Check that datasources are created successfully under Resources > JDBC > Data sources.
3. Click each of the datasource created during installation.
4. In the right-pane, click WebSphere Application Server data source properties.
5. In the Connection validation properties section, select the Validate existing pooled connections check box. The Retry interval text box is enabled.

   

6. In the Retry interval text box, enter 10 seconds for interval value.
7. Save the changes and restart WebSphere Server.

How to Delete Kony Fabric (MobileFabric) Artifacts Manually if Uninstallation of Kony Fabric Fails on WebSphere

In case uninstalling Kony Fabric fails, some the artifacts need to be deleted manually.

1. Log in to WebSphere Admin Console and go to Applications.
2. Select all the check boxes for Kony Fabric related applications such as accounts, authService, console, integration, workspace, admin, services, and middleware, and click Remove or Uninstall at the top.

   

3. After above step is successful, go to Resources> JDBC > JDBC providers and delete all the providers created as part of Kony Fabric installation.

   

4. Go to Security > Global Security > Java Authentication and Authorization Service > J2C authentication data and delete the authentication entries added during Kony Fabric installation.

   

Log in issues with Salesforce, Google or Facebook

Issue:

If you get the error "message": "sun/security/ec/NamedCurve" while trying to log in to Salesforce, Google or Facebook, follow these below resolution to fix the issue.

Resolution: Set the following properties in websphere jre/lib/security/java.security file.

• Below is commented by default. Remove the comment symbol.

  #Default JSSE socket factories
  ssl.SocketFactory.provider=com.ibm.jsse2.SSLSocketFactoryImpl
  ssl.ServerSocketFactory.provider=com.ibm.jsse2.SSLServerSocketFactoryImpl

• Below is not a comment by default. Comment it.

  #WebSphere socket factories (in cryptosf.jar)
  #ssl.SocketFactory.provider=com.ibm.websphere.ssl.protocol.SSLSocketFactory
  #ssl.ServerSocketFactory.provider=com.ibm.websphere.ssl.protocol.SSLServerSocketFactory

How to Enable TLSv Protocol on WebSphere

If your Kony Fabric instance on WebSphere that is updated with IBM Java 7 SDK fix pack 7.0.9.60, the identity fails to log-in to Salesforce. Because the TLSv1.0 protocol is disabled on Kony Fabric and on the other external sites that Kony Fabric wants to connect - for example, Salesforce. To avoid log-in issues with external back-ends, add the -D parameters into JVM Arguments.

HTTPS Connections to Kony Fabric components and other backend services. For example, Salesforce fails if TLS v1.2 is not used. Please follow the below steps to enforce TLS 1.2 as the security protocol.

To add -D parameters in the JVM arguments, follow these steps:

1. Log into WebSphere Admin Console.
2. Go to Application servers > server1 > Process definition > Java Virtual Machine. 
3. Under the Configuration > General Properties > Generic JVM arguments, add the following -D parameter:

   -Dhttps.protocols=TLSv1.2 -Dcom.ibm.jsse2.overrideDefaultTLS=true

   

4. Go to Security > SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP) settings.

5. Under General Properties > Protocol, select the TLSv1.2 protocol.

   

6. If your Kony Fabric is installed on WebSphere with IBM Java 8, add the following parameter to JVM arguments:

   -Dcom.ibm.jsse2.overrideDefaultTLS=true

   For more details, refer to Salesforce disabling TLS 1.0.

How to Enable DELETE with IHS and WebSphere

An app Unpublish fails with IHS and WebSphere Application Server, the unpublish error message is "400 Bad Request". Because the DELETE is not allowed from IHS to WebSphere Application Server by default.

To enable the DELETE on IHS and WebSphere Application Server, follow these steps:

1. In IBM WebSphere Console, navigate to Servers > Server Types > Web server > "web_server_name" > Plug-In properties > Request and response.

2. Select the Accept content for all requests check box.

   

3. Click OK and SAVE.

   For more details, refer to IBM Support.

Product Logs Location for WebSphere Installation for Kony Fabric (MobileFabric)

• Logs for Single Node Installation:
  • Kony Fabric (MobileFabric) Windows Installer Guide
    Kony Fabric on Windows Install Guide
  • Kony Fabric (MobileFabric) Linux Installer Guide
    Kony Fabric on Linux Install Guide
• Logs for Multinode Installation:
  • Kony Fabric (MobileFabric) Windows Installer Guide
    Kony Fabric on Windows Install Guide
  • Kony Fabric (MobileFabric) Linux Installer Guide
    Kony Fabric on Linux Install Guide

How to clean the temp files of WebSphere

1. Clean the wstemp folder of the App server and the DMGR (Deployment Manager).

   Location: {WebSphere Installation}/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp

2. Run the clear class cache command.

   Location: {WebSphere Installation}/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

   • clearClassCache.sh / clearClassCache.bat
   • osgiCfgInit.sh / osgiCfgInit.bat

How to fix Identity URL host port error on Kony Fabric launch

If you encounter the following error in the logs while trying to launch the Kony Fabric Console installed on WebSphere:

000000e8 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[mbaasportal]: org.scribe.exceptions.OAuthException: Response body is incorrect. Can't extract token and secret from this: 'Error 401: No credentials found for the consumer key [UhG8h6K8DQpOp41i1QWDsShwXdoFtGmnX2ve9fnM] No app found

This could be the case where port in the Identity URL is not matching the registered URL of Identity. Check in the authService.log to see if the printed URL matches the registered URL. In that case, it can be fixed by performing the following steps:

1. Log into the WebSphere Admin Console.
2. Go to Application servers > server_name.
3. Go to Web Container Settings > Custom Properties.
4. Add the following properties:
   • Name: trusthostheaderport

     Value: true

   • Name: com.ibm.ws.webcontainer.extractHostHeaderPort

     Value: true

5. Save the changes and restart WebSphere Server(s).

Copyright © 2015 Kony, Inc. All rights reserved.