SQL1032N - Issues with DB2START - DB2 9.5 ESE & DB2 9.7 ESE

If db2start command fails giving the error code SQL1042C SQL1032N

SQL8000N DB2START processing failed; a valid product license was not found.
SQL1032N No start database manager command was issued. SQLSTATE=57019

Cause

These error typically indicate that the DB2 UDB product license has not been activated.

Answer

To activate the DB2 UDB product license, run this command:

db2licm -a license_filename

Where license_filename is the name of the license file.

Example:

The file db2ese.lic is the DB2 Enterprise Server Edition license file. The license file should be copied to a local directory (e.g. /tmp) and updated with the following command (resulting output shown):

=> db2licm -a /tmp/db2ese.lic
DBI1402I License added successfully.

DBI1426I This product is now licensed for use as specified in
the License Acceptance and License Information
documents pertaining to the licensed copy of this
product. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF
THE TERMS OF THE IBM LICENSE ACCEPTANCE AND LICENSE
INFORMATION DOCUMENTS, LOCATED IN THE FOLLOWING
DIRECTORY: /usr/opt/db2_08_01/license/en_US.iso88591

The license information can be queried with this command (resulting output shown):

=> db2licm -l
Product Name = "DB2 Enterprise Server Edition"
Product Password = "DB2ESE"
Version Information = "8.1"
Expiry Date = "Permanent"
Registered Connect User Policy = "Disabled"
Number Of Entitled Users = "5"
Enforcement Policy = "Soft Stop"
Number of processors = "1"
Number of licensed processors = "1"
Annotation = ""
Other information = ""

Management Center : Increasing the Promotion Code Upload Limit

By default, the maximum file size of your CSV file or .zip is 10 MB. You can change the maximum file size.

The maximum file size limit is defined in both the Open Lazlo client and Websphere Commerce instance file.

Below are the steps required to be performed to increase the promotion code upload limit :

1. Update the client

1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
2. In the Enterprise Explorer view, expand LOBTools > WebContent > config> commerce> promotion> objectDefinitions
3. Open the PromotionCodeImportPrimaryObjectDefinition.def file, and locate the defination name proBasePromotionCodeImportPrimaryObjectDefinition.
4. Update the value of the maximumFileSize attribute. The default value is 10000000 bytes. You can change this value as needed, however, keep in mind the impact that larger files might have on your server.
   <PrimaryObjectDefinition copyProtected="true" creatable="true" definitionName="proBasePromotionCodeImportPrimaryObjectDefinition" displayName="${promotionResources.promotionCodeImportObjectName}" displayNameProperty="fileName" fileNamePropertyName="fileName" fileSizePropertyName="fileSize" headerIcon="promotionCodeImportHeaderIcon" helpLink="tasks/tprimportpromo.htm" icon="promotionCodeImportIcon" idProperty="promotionCodeImportId" isBaseDefinition="true" isFileObject="true" maximumFileSize="new_size" newDisplayName="${promotionResources.promotionCodeImport_newPromotionDisplayName}" newObjectMenuItemText="${promotionResources.contextMenuNewPromotionCodeImport}" objectGroups="PromotionCodeImportGroup" propertiesDefinitionName="proPromotionCodeImportProperties" searchType="FindPromotionCodeImports" writeUsage="IBM_ManagePromotionTool"> 
   
   where new_size is the size you want (in bytes).

2. Update the server.
   1. Open the Updating the WebSphere Commerce configuration file, and locate the command element for com.ibm.commerce.promotion.commands.CreatePromotionCodeImportCmd name.
   2. Change the value of the maxuploadsize attribute to match the value specified for the client.
   3. Run the ANT target: UpdateEAR target to update the runtime configuration with the master configuration file.

After you complete your customization:

1. Right-click LOBTools Project; then click Build OpenLaszlo Project to produce an updated ManagementCenter.swf file under the workspace_dir\LOBTools\WebContent directory. This setting is the default environment setting.
2. Test your changes by viewing them in the Management Center, using this URL: https://hostname:8000/lobtools.
3. Deploy your changes to your production environment.

Remote Widgets

Found this cool video which talks about Remote Widgets.. Hope this post also goes viral ! ;)

RESOLVED : An EJB JAR does not exist for the selected project and Map Validation cannot run

Issue:

1. Incase if you ever see the below error in the "Problems" tab of the RAD -

    "An EJB JAR does not exist for the selected project and Map Validation cannot run"

2. The Deployment Descriptor file is not seen/found in the "WebsphereCommerceServerExtensionData" project

3. Clicking on the Map.mapxmi , the file does not open and an error is displayed "The ejb or database is nor defined in the ejb-jar.xml"

Resolution:

It is implicitly assumed in RAD 6 that the source folder which contains the deployment descriptor xml file (DD) should be the FIRST source folder of the project. Otherwise the DD cannot be found.

So, the solution for this problem is to put the folder that contains the deployment descriptor at the top of the Order and Export list in the Project Properties. Then the DD can be found.

So, move the folder "WebsphereCommerceServerExtensionData/ejbModule" to the top in the Order/Export list in the Project Properties.

Incase you do not find that folder in the list , use the following steps to create the new folder -

1. Open RAD and create a new EJB project
2. Right click on the Project in Project Explorer, and choose: Properties
3. Select Java Build Path
4. Go to the Source tab
5. Click Add Folder...> Create New Folder...
6. Go to Order and Export, move the new folder upwards so that it is found at the top of the list.
7. Press OK to close the properties View
8. Run Project > Clean (followed by Build Automatically)
9. Check the Problems view; you will see the above errors

 

A file does not exist for module element having uri: Rest.war

When you start the WebSphere Commerce Test Server, you receive an error that states that a file does not exist.

Problem

When starting the WebSphere Test Server after enabling the Management Center feature, a file does not exist error is displayed in the startup logs. For example,

[11-3-1 15:02:39:484 CST] 00000009 ApplicationMg E   WSVR0100W: An error occurred 

initializing, WC
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NoModuleFileException: 

A file does not exist for module element having uri: Rest.war

Solution

To resolve this issue, you need to rebuild the LOBTools project and republish the test server, as follows:

1. Open your WebSphere Commerce Developer workspace.
2. Right-click the LOBTools project and rebuild it.
3. If necessary, start the test server in the Servers view and ignore the error that states the file does not exist.
4. After the test server starts, right-click the test server and click Publish. After publishing is complete, the error should no longer be displayed when you subsequently restart the test server.

Know what features are enabled on WCS 7?

Query the database table SITE and you can find the list of features enabled in your WCS 7 application.
You can aslo find out the fix pack level.

You can find out the fix pack level and installed feature pack details using the versionInfo.bat

Day 7 : Generating Sitemaps to submit to search engine providers

A Sitemap is an xml list of all the pages in your store that is submitted to search engines so that they will know what to crawl and index. The Sitemap Generator has been enhanced in Feature Pack 3 to index the new friendly website addresses and search landing pages.

For more information on Sitemaps, see WebSphere Commerce integration with sitemaps.

With the WebSphere Commerce integration with sitemaps, you can create a sitemap XML file, sitemap_ storeID.xml, that contains a list of URLs for your site. This way, customers are able to easily find your site when they perform a search, promoting activity to your site, and increasing the probability of sales.

The sitemap_ storeID.xml file is placed in the following directory:

• WC_eardir /Stores.war
• WCDE_installdir /workspace/Stores/WebContent

The OOB command SitemapGenerate can be scheduled at regular intervals to generate the SiteMap XML. Please refer the link Creating and scheduling the SitemapGenerate job for more details on the scheduling.

This concludes our week long SEO marathon. :)

Related Blogpost

Smarter SEO for Smarter Commerce