Hi Friends,
Well you must have come across various situations when you need to quickly edit the /etc/sudoers file for making changes.
Though it is not straight forward to open in an vi editor & edit it, below are time saving commands for Linux & Unix to quickly edit the same:
Linux:
bash-3.00$ sudo visudo
Unix:
bash-3.00$ /usr/local/bin/sudo /usr/local/sbin/visudo
VISUDO opens the /etc/sudoers file in a temporary editable mode, which can be changed and saved to reflect changes immediately.
Hope this tip helps :-)
Keywords:
Linux, Unix, Red Hat, Solaris, /etc/sudoers, vi, visduo, sudo, edit, etc
Thursday, January 13, 2011
Thursday, December 23, 2010
Dynamic Pricing - Siebel 8.1.1.x and above
Hi Friends,
Well, up to Siebel 8.0.0.x versions, we had to manually configure dozens of things to ensure that we successfully enable Dynamic Pricing (Complete Manual Instructions), but now that is no longer the case from Siebel 8.1.1.x and above versions :-)
Dynamic Pricing can now be enabled at a click of a button from:
Sitemap -> Administration - Pricing -> Pricelists -> Menu -> Enable Dynamic Pricing
Hope this tip helps!
Enjoy!
Keywords:
comparison pricing,competitive pricing,dynamic price,dynamic pricing,market pricing,price waterfall,pricer,pricing management,pricing strategy,product pricing,siebel crm,value pricing
Well, up to Siebel 8.0.0.x versions, we had to manually configure dozens of things to ensure that we successfully enable Dynamic Pricing (Complete Manual Instructions), but now that is no longer the case from Siebel 8.1.1.x and above versions :-)
Dynamic Pricing can now be enabled at a click of a button from:
Sitemap -> Administration - Pricing -> Pricelists -> Menu -> Enable Dynamic Pricing
Hope this tip helps!
Enjoy!
Keywords:
comparison pricing,competitive pricing,dynamic price,dynamic pricing,market pricing,price waterfall,pricer,pricing management,pricing strategy,product pricing,siebel crm,value pricing
Tuesday, November 23, 2010
IE8 - SBL-UIF-00296: You already have a web browser accessing the current web session.
Hi Friends,
With Siebel CRM recently releasing IE8 compatibility, one common issue faced on day one is
"SBL-UIF-00296: You already have a web browser accessing the current web session. Multiple browsers are not allowed to share the same web session"
No matter what you do, you are not able to open multiple Siebel instances in IE8!
Well, those who are new to IE8, there seems to be a session replication builtin which causes to replicate the session in the multiple instances you open causing Siebel to give the error.
The correct way to resolve this is to start a new IE8 Siebel Session using
a) File -> New Session or [From IE8 UI]
b) iexplore.exe -nomerge [Command line -nomerge option]
This way we explicitly instruct IE8 not to replicate session allowing us to open multiple Siebel instances.
Please remember that never open multiple Siebel instances in different IE Tabs! It is not supported and can cause a big issue with your data.
Hope this tip helps :-)
Keywords:
IE8, 8.0.0.8, 8.1.1.3, Siebel CRM, siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel support web,siebel systems, Internet Explorer, Session Replication, etc
With Siebel CRM recently releasing IE8 compatibility, one common issue faced on day one is
"SBL-UIF-00296: You already have a web browser accessing the current web session. Multiple browsers are not allowed to share the same web session"
No matter what you do, you are not able to open multiple Siebel instances in IE8!
Well, those who are new to IE8, there seems to be a session replication builtin which causes to replicate the session in the multiple instances you open causing Siebel to give the error.
The correct way to resolve this is to start a new IE8 Siebel Session using
a) File -> New Session or [From IE8 UI]
b) iexplore.exe -nomerge [Command line -nomerge option]
This way we explicitly instruct IE8 not to replicate session allowing us to open multiple Siebel instances.
Please remember that never open multiple Siebel instances in different IE Tabs! It is not supported and can cause a big issue with your data.
Hope this tip helps :-)
Keywords:
IE8, 8.0.0.8, 8.1.1.3, Siebel CRM, siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel support web,siebel systems, Internet Explorer, Session Replication, etc
Tuesday, November 02, 2010
Joomla LDAP Setup
Hi Friends,
Few days back i was playing with an internal setup of WAMP Server having Apache 2.2.11, PHP 5.3.0 & MySQL 5.1.36 deployed with Joomla 1.5.21 CMS.
Joomla provides a native LDAP Authentication plugin which can be enabled to connect to your LDAP directory for authentication. It can be found under your Joomla Admin Panel -> Extensions -> Plugin Manager -> Authentication - LDAP
In our environment we have Red Hat Directory Server providing us the directory services.
It supports bind & search kind of authentication over LDAP, so below are the settings needed to be done on the joomla authentication plugin
Host: ldaphost.domain.com
Port: 389 [Default, change it if you run on other port number]
Authorisation Method: Bind & Search
Base DN: dc=value,dc=value [e.g. dc=domainname,dc=com]
Search String: uid=[search] [Note, here uid is the attribute which stores user id. So in your environment you have userid as the attribute, then the correct value is userid=[search] ]
User's DN: [This should be blank & only used if you are using Authorisation Method as bind directly as a user. ]
Connect Username: uid=directoryadminusername,ou=directoryadminusergroup,dc=value,dc=value
[Notes:
uid - Is the attribute which stores user id. If you have userid as the attribute, the it should be userid=
directoryadminusername - This should be your LDAP Directories Admin user's id
directoryadminusergroup - This should be your LDAP Directory Admin user's group name
dc=value,dc=value - This should be similar to your Base DN ]
Connect Passwod: Specify the directory admin user password here
Map Full name: fullnameattribute [Specify the attribute within LDAP Directory which stores the full name]
Map Email: emailattribute [Specify the attribute within LDAP Directory which stores the email address]
Map Userid: useridattribute [Specify the attribute within LDAP Directory which stores the userid]
Note, once you enable the LDAP Authentication, any new user logging in will have an automatic user record creation within Joomla. So in essence, you should take off the "Register" link on the login form!
If you face issues while setting this up, then please ask in the comments section :-)
Enjoy!
Keywords:
Joomla 1.5.21, PHP, MySQL, WAMP, Apache, CMS, LDAP, etc
Few days back i was playing with an internal setup of WAMP Server having Apache 2.2.11, PHP 5.3.0 & MySQL 5.1.36 deployed with Joomla 1.5.21 CMS.
Joomla provides a native LDAP Authentication plugin which can be enabled to connect to your LDAP directory for authentication. It can be found under your Joomla Admin Panel -> Extensions -> Plugin Manager -> Authentication - LDAP
In our environment we have Red Hat Directory Server providing us the directory services.
It supports bind & search kind of authentication over LDAP, so below are the settings needed to be done on the joomla authentication plugin
Host: ldaphost.domain.com
Port: 389 [Default, change it if you run on other port number]
Authorisation Method: Bind & Search
Base DN: dc=value,dc=value [e.g. dc=domainname,dc=com]
Search String: uid=[search] [Note, here uid is the attribute which stores user id. So in your environment you have userid as the attribute, then the correct value is userid=[search] ]
User's DN: [This should be blank & only used if you are using Authorisation Method as bind directly as a user. ]
Connect Username: uid=directoryadminusername,ou=directoryadminusergroup,dc=value,dc=value
[Notes:
uid - Is the attribute which stores user id. If you have userid as the attribute, the it should be userid=
directoryadminusername - This should be your LDAP Directories Admin user's id
directoryadminusergroup - This should be your LDAP Directory Admin user's group name
dc=value,dc=value - This should be similar to your Base DN ]
Connect Passwod: Specify the directory admin user password here
Map Full name: fullnameattribute [Specify the attribute within LDAP Directory which stores the full name]
Map Email: emailattribute [Specify the attribute within LDAP Directory which stores the email address]
Map Userid: useridattribute [Specify the attribute within LDAP Directory which stores the userid]
Note, once you enable the LDAP Authentication, any new user logging in will have an automatic user record creation within Joomla. So in essence, you should take off the "Register" link on the login form!
If you face issues while setting this up, then please ask in the comments section :-)
Enjoy!
Keywords:
Joomla 1.5.21, PHP, MySQL, WAMP, Apache, CMS, LDAP, etc
Friday, October 29, 2010
Joomla PHP/MySQL Performance Tuning
Hi Friends,
Few days back i was playing with an internal setup of WAMP Server having Apache 2.2.11, PHP 5.3.0 & MySQL 5.1.36 deployed with Joomla 1.5.21 CMS.
For a 500 user base below are Apache & MySQL Parameters for optimal Joomla Performance on a Windows Deployment:
Apache mpm_winnt_module
# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
ThreadLimit 1000
ThreadsPerChild 500
MaxRequestsPerChild 0
KeepAlive On
KeepAliveTimeout 60
MaxKeepAliveRequests 100
MaxMemFree 100
MySQL my.ini
key_buffer = 150M
max_allowed_packet = 1M
table_cache = 1000
sort_buffer_size = 1M
net_buffer_length = 8K
read_buffer_size = 1M
read_rnd_buffer_size = 768K
myisam_sort_buffer_size = 64M
basedir=D:/wamp/bin/mysql/mysql5.1.36
log-error=D:/wamp/logs/mysql.log
datadir=D:/wamp/bin/mysql/mysql5.1.36/data
query_cache_limit=1M
query_cache_size=32M
query_cache_type=1
tmp_table_size=32M
key_buffer_size=64M
These changes are tested & found be working at acceptable levels in my environment. Please consider your deployment sizing & other aspects before adopting above settings.
Keywords:
Apache, WAMP, PHP, MySQL, Performance, Tuning, etc
Few days back i was playing with an internal setup of WAMP Server having Apache 2.2.11, PHP 5.3.0 & MySQL 5.1.36 deployed with Joomla 1.5.21 CMS.
For a 500 user base below are Apache & MySQL Parameters for optimal Joomla Performance on a Windows Deployment:
Apache mpm_winnt_module
# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
ThreadLimit 1000
ThreadsPerChild 500
MaxRequestsPerChild 0
KeepAlive On
KeepAliveTimeout 60
MaxKeepAliveRequests 100
MaxMemFree 100
MySQL my.ini
key_buffer = 150M
max_allowed_packet = 1M
table_cache = 1000
sort_buffer_size = 1M
net_buffer_length = 8K
read_buffer_size = 1M
read_rnd_buffer_size = 768K
myisam_sort_buffer_size = 64M
basedir=D:/wamp/bin/mysql/mysql5.1.36
log-error=D:/wamp/logs/mysql.log
datadir=D:/wamp/bin/mysql/mysql5.1.36/data
query_cache_limit=1M
query_cache_size=32M
query_cache_type=1
tmp_table_size=32M
key_buffer_size=64M
These changes are tested & found be working at acceptable levels in my environment. Please consider your deployment sizing & other aspects before adopting above settings.
Keywords:
Apache, WAMP, PHP, MySQL, Performance, Tuning, etc
Subscribe to:
Posts (Atom)