Posts

Registering a WebSphere windows services

Image
Registering a WebSphere windows services are very similar to adding a linux service. From a cmd prompt: Change directory to %WAS_HOME%/bin – in this example it is D:\IBM\WebSphere\AppServer\bin The syntax of the command is wasservice –add <service name> -serverName <name of server> -profilePath <path to server profile> To enable the server to restart automatically and to encode the user name and password additional parameters are required wasservice -add Dmgr -serverName dmgr -profilePath D:\IBM\WebSphere\AppServer\profiles\Dmgr01 -encodeParams -restart true -startType automatic -stopArgs "-username wasadmin -password password" wasservice -add Node -serverName nodeagent -profilePath D:\IBM\WebSphere\AppServer\profiles\AppSrv01 -encodeParams -restart true -startType automatic -stopArgs '-username wasadmin -password password -stopservers' Once the wasservice command has been run successfully the new services will be visible ...

Registering WebSphere as a linux service

Image
Registering WebSphere as a linux service is straight forward. User the wasservice script which is held in the $was_home/bin directory (default is /opt/IBM/WebSphere/AppServer/bin ). #!/bin/bash cd $WAS_HOME / bin ./ wasservice . sh - add Dmgr - serverName dmgr \ - profilePath / opt / IBM / WebSphere / AppServer / profiles / Dmgr01 \ - stopArgs '-username wasadmin -password password' \ - encodeParams ./ wasservice . sh - add Node - serverName nodeagent \ - profilePath / opt / IBM / WebSphere / AppServer / profiles / AppSrv01 \ - stopArgs '-username wasadmin -password password -stopservers' \ - encodeParams chkconfig -- add Dmgr_was . init chkconfig -- add Node_was . init chkconfig -- level 2345 Dmgr_was . init on chkconfig -- level 2345 Node_was . init on Running the wasservice commands with the appropriate arguments (see example above for syntax), w...

How to fix: User, group, or role '*' already exists in the current database. (Microsoft SQL Server, Error: 15023)

Image
Create failed for User 'TMS'. (Microsoft.SqlServer.Smo) User, group, or role 'TMS' already exists in the current database. (Microsoft SQL Server, Error: 15023)   To fix this there are two different methods depending on the version of SQL Server you are using. Both of these commands re-map the user's Security Identifier (SID) to match the sql server login's SID.   SQL Server 2008 / SQL Server 2008 R2 If you have already created the server login for the user, run this in the database with the login problem. (Change ' user'  to be the database username you wish to fix, and ' serverlogin ' is the sql server login to map the user to).  ALTER USER user WITH LOGIN = serverlogin For full details of the ALTER USER command see MSDN  http://msdn.microsoft.com/en-us/library/ms176060.aspx

IBM Error: ERROR: The system was unable to find the specified registry key or value.

Technote (troubleshooting) Problem(Abstract) While installing InfoSphere Information Server (IS) on Windows 2012 R2, there is severe message in the installation log. Symptom The following severe message can be seen in Information Server Installation log, but the installation is successful. 2015-07-08T10:55:39.740, INFO: CDIIN2753I:Command Array: reg query HKLM\Software\Microsoft\Windows NT\CurrentVersion /reg:64 /v CSDVersion, env = null, workingDir =null 2015-07-08T10:55:39.771, INFO: Exit Code: 1, Info: , Info ERROR: The system was unable to find the specified registry key or value. 2015-07-08T10:55:39.771, SEVERE: com.ibm.is.install.core.PlatformWindows Exit Code: 1, Info: , Error: ERROR: The system was unable to find the specified registry key or value. 2015-07-08T10:55:39.771, INFO: _windowsCsdVersion = null Cause This is caused because IS Installer is trying to get the Service Pack level for the host operat...

IBM Cognos: XQE-JDB-0004 A problem occurred finding the driver class “com.ibm.db2.jcc.DB2Driver”.

When you are trying to test the connection to the DB2 database from Cognos configuration and you are getting this error message: XQE-JDB-0004 A problem occurred finding the driver class "com.ibm.db2.jcc.DB2Driver". This error cause because the Cognos cannot find the DB2 drivers. Solution of this problem is simple. You have to copy files db2jcc.jar and db2jcc4.jar to <Install_Cognos>\v5dataserver\lib and <Install_Cognos>\webapps\p2pd\WEB-INF\lib. After you copy these files you need to restart the Cognos server.

The requested URL was not found - permalink error

When I update the permalinks to anything but default, links in the site give the error The requested URL ### was not found on this Server . Enable rewrite_module in apache Introduction In this tutorial, we will activate and learn how to manage URL rewrites using Apache2's mod_rewrite module. This tool allows us to rewrite URLs in a cleaner fashion, translating human-readable paths into code-friendly query strings. This guide is split into two halves: the first sets up a sample web application and the second explains commonly-used rewrite rules. Prerequisites To follow this tutorial, you will need: One fresh Ubuntu 14.04 Droplet A sudo non-root user, which you can set up by following steps 2 and 3 of this tutorial Step 1 — Installing Apache In this step, we will use a built-in package installer called apt-get . It simplifies management drastically and facilitates a clean installation. First, update the system's package index. This will ens...

How to change the default location of the Information Server Reporting workspace.

Technote (FAQ) Question How can I change the drive or path of the Reporting workspace directory to a different location than where Information Server creates it by default? Cause The Information Server Reporting workspace is used at run time for holding temporary status and information related to report generation. The amount of space required varies depending on the number, types and complexity of reports created. In some cases, the default location of the Reporting workspace does not have adequate space so it may be necessary to relocate to a different location. When the workspace is located in a tmp directory location, it could potentially be vulnerable to being deleted or files removed as part of some system administrator or user maintenance activity. To avoid this problem you may wish to change the default reporting workspace to a different directory. Answer The default reporting workspace location is dif...