Make Development little bit easy, By pass ACP !!
DISABLE ACCESS CONTROL CHECK WHILE DEVELOPMENT PERIOD
Go to wc-server.xml
follow below screen or find BootstarpMulti in wc-server and add ' AccessControlUnitTest="true" ' before this tag.
Important Links
Managment center (CMC)
https://localhost:8000/lobtools - wcsadmin/wcsadmin
Accelerator
https://localhost:8000/webapp/wcs/tools/servlet/ToolsLogon?XMLFile=common.mcLogon&storeId=0
Admin Console
https://localhost:8002/webapp/wcs/admin/servlet/ToolsLogon?XMLFile=adminconsole.AdminConsoleLogon&storeId=0Org Admin Console
https://localhost:8004/webapp/wcs/orgadmin/servlet/ToolsLogon?XMLFile=buyerconsole.BuyAdminConsoleLogon&storeId=0
Dynacache
https://localhost:9043/cachemonitor/
WasAdminConsole
https://hostname:9043/ibm/console
Config Files
WC config
[Toolkit Folder]/xml/config/wc-server.xml
Promotion Engine Configuration
[Toolkit Folder]/xml/PromotionEngineConfiguration/WCSPromotionEngineConfig.xml
Folders
Log Files
[Toolkit folder]/wasprofile/logs/server1/*.log
Temp folder
[Toolkit folder]/wasprofile/temp
Changing DB
Go to WCTK\bin
Execute the following command -
setdbtype oracle C:\oracle\product\10.2.0\db_1 <ServiceName> <DBAName> <DBAPwd> <DBUserID> <DBUserPwd> <DBHost> <DBServerPort>
Execute the following command -
setdbtype oracle C:\oracle\product\10.2.0\db_1 <ServiceName> <DBAName> <DBAPwd> <DBUserID> <DBUserPwd> <DBHost> <DBServerPort>
Troubleshooting
CONFLICT ON PORT 8880, WHILE STARTING WAS SERVERThis happens when there are other application which is also using the port 8880. So to resolve the issue, we need to find which application is using the port 8880 through 'netstat' command in command prompt or update our WAS server to not use 8880.
We can update the WAS server through these steps:
1) Shut down WAS.
2) Browse to or search for the serverIndex.xml, for example, at "C:\WAS\AppServer\config\yourNode\nodes\yourNode\serverindex.xml"
3) Open the file and locate the following lines:
endPointName="SOAP_CONNECTOR_ADDRESS">
4) Change "port 8880" to an available port
5) Save the serverindex.xml and restart WAS
Follow the link : http://www-01.ibm.com/support/docview.wss?uid=swg21191681
We Might get these TCP error, port 80 nad 443 already in use and TCP_2 initialization failed
The socket bind failed for host * and port 80. The port may already be in use.
The socket bind failed for host * and port 443. The port may already be in use.
_______________
Sometimes we are getting the above errors in console and application won't work properly.
Reasons for the error :
a) It clearly says port 80 and 443 is already used by some other application.
b) or the virtual host configuration in commerce server may be not functioning properly.
Soln :
We can follow the below link of info center 'http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.developer.doc/refs/rdetbde.htm' or run 'netstat-aon' to check which application is suing the port 80,
most of the cases 'skype' is using the poty 80 and 443 which causes issue, either kill skype or check skype to uncheck the common property which uses port 80 and 443.
sometimes vmware application if installed, it uses port 443.
and sometimes system PID 4 is usng the port 80, to fix this, go to Device Manager -- > Non-plug and Play Driver --> http and disable this and reboot the system.
Enabling Traces
Tracing log into wasconsole
Right click on the server -> goto admin console
Upon logging in go to Servers -> Application Servers
Click Server 1
Click "Logging and Tracing" under Troubleshooting.
Click "Change Log Detail Level"
Enter the following and click Ok.
*=info:enable.trace.log.*=all:
com.ibm.websphere.commerce.WC_USER=all:
com.ibm.websphere.commerce.WC_SERVER=all:
com.ibm.websphere.commerce.WC_ACCESSCONTROL=all
Tracing SQL logs into wasconsole
Follow the above steps and add following
*=info: com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement=all
EJB Tracing
*=info:EJBContainer=all:PMGR=all.
Promotion Engine Tracing
Go to folder WCTK -> xml -> PromotionEngineConfiguration
Open WCSPromotionEngineConfig.xml
Set <Debug>true</Debug>
Enabling CMC ( open laszlo logs )
Right-click LOBTools and click Properties. Select OpenLaszlo Settings.
Click Enable the debug console check box. Click Apply.
Important SQLs
Roles of user
select u.logonid,r.name,org.orgentityname from mbrrole mbr, userreg u,orgentity org,role r where mbr.member_id=u.users_id and org.orgentity_id=mbr.orgentity_id
and mbr.role_id=r.role_id
and u.logonid ='wcsadmin';
1) RESET THE PASSWORD FOR BUSINESS TOOLS
(Commerce Accelerator, Administration Console ......... )
Run the below query, this will reset the password to initial password wcsadmin.
Run the below query, this will reset the password to initial password wcsadmin.
update userreg set logonpassword = x'74434f61354f51593862415655304d5268424e54723865685653356151374a2b353163506c4261363730633d202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020' where logonid='wcsadmin';
update userreg set salt = 'hsdbacehyoyn' where logonid='wcsadmin';
update userreg set status = 1 where logonid='wcsadmin';
update userreg set passwordexpired = 1 where logonid='wcsadmin';
Start Dev Environment
startWCToolkit.bat in [Toolkit Folder]\bin
IBM WCS tips file
[Toolkit Folder]\hintsandtips.html