Group items tagged

For 64-bit users: wget -O jdk-64bit.tar.gz http://goo.gl/MSzBj wget -O jre-64bit.tar.gz http://goo.gl/yZgjI sudo -s cp -r jre-64bit.tar.gz /usr/local/java sudo -s cp -r jdk-64bit.tar.gz /usr/local/java cd /usr/local/java sudo -s chmod a+x jre-64bit.tar.gz sudo -s chmod a+x jdk-64bit.tar.gz sudo -s tar xvzf jre-64bit.tar.gz sudo -s tar xvzf jdk-64bit.tar.gz

sudo nano /etc/profile Add the following lines at the end of file: JAVA_HOME=/usr/local/java/jdk* PATH=$PATH:$HOME/bin:$JAVA_HOME/bin JRE_HOME=/usr/local/java/jre* PATH=$PATH:$HOME/bin:$JRE_HOME/bin export JAVA_HOME export JRE_HOME export PATH

Now enter following commands one by one in terminal: sudo update-alternatives --install "/usr/bin/java" "java" "/usr/local/java/jre1.7.0_12/bin/java" 1 sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/local/java/jdk1.7.0_12/bin/javac" 1 sudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/local/java/jre1.7.0_12/bin/javaws" 1 sudo update-alternatives --set java /usr/local/java/jre1.7.0_12/bin/java sudo update-alternatives --set javac /usr/local/java/jdk1.7.0_12/bin/javac sudo update-alternatives --set javaws /usr/local/java/jre1.7.0_12/bin/javaws . /etc/profile

Update Apex Tabular form with PLSQL

for i in 1..apex_application.g_f02.count loop update dept set dname = apex_application.g_f03(i) where deptno = apex_application.g_f02(i); end loop;

These are few of the benefits of implementing a good quality CRM All of your clients’ information is stored in one place, it’s easy to update and share with the whole team. Updates by colleagues should be saved immediately. Every member of your team will be able to see the exact point when your business last communicated with a client, and what the nature of that communication was. CRMs can give you instant metrics on various aspects of your business automatically.  Reports can be generated. These can also be used to forecast and plan for the future. You will be able to see the complete history of your company’s interaction with a client. Calendars and diaries can be integrated, relating important events or tasks with the relevant client.  Suitable times can be suggested to contact customers and set reminders.

Finding one system that will fit your needs in one package may not be possible, so be aware that you may need to customise it to fit into your company. There are infinite possibilities here so don’t get too carried away as costs will rise accordingly.

Ensure that the CRM works on mobile devices and can be accessed remotely. Employees aren’t necessarily sat at their desks when it needs to be used or updated. Real-time updates are necessary for ensuring that clients aren’t contacted twice with the exact same follow up.

insert and update a record using cursor in oracle

MERGE INTO studLoad l USING ( SELECT studId, studName FROM student ) s ON (l.studId = s.studId) WHEN MATCHED THEN UPDATE SET l.studName = s.studName WHERE l.studName != s.studName WHEN NOT MATCHED THEN INSERT (l.studID, l.studName) VALUES (s.studId, s.studName)

commit

1. Uninstall BIP desktop from control->Add or remove programs. 2. Open explorer and go to "C:\WINDOWS\assembly". 3. Check if there are assemblies which start with "TB" If present, remove them all. 4. Open the MS Word startup directory and check there are no files there. The directory is normally the following. C:\Documents and Settings\<user name><Application Data\Microsoft\Word\STARTUP5. Open MS Word and check that you don't see the BIP tool bar. -> If you see it, please move Normal.dot to another directory and try again.6. Please check that the OS user you use has an administrator privilege on the PC, this is really important. 7. Please go to Control Panel -> Add or Remove programs and check if the followings have been installed. Shared Add-in Extensibility Update for Microsoft .NET Framework 2.0 (KB908002) Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002) 8. Install BIP Desktop again

Note: Power Pivot and Power View on the standalone retail 32-bit and 64-bit SKUs were added with the October 2013 updates. If you have one of these SKU's but do not see the add-in, please apply the most recent updates and test for improvement. 

Mistake 1.  Not putting a strong interdisciplinary team together. It is impossible to put together an analytics platform without understanding the needs of the customers who will use it.  Sounds simple, right?  Who wouldn’t do that?  You’d be surprised how many analytics projects are wrapped up by IT because “they think” they know the customer needs.  Not assembling the right team is clearly the biggest mistake companies make.  Many times what is on your mind (and if you’re an IT person willing to admit it) is that you are considering converting all those favorite company reports.  Your goal should not be that.  Your goal is to create a system—human engineered with customers, financial people, IT folks, analysts, and others—that give people new and exciting ways to look at information.  It should give you new insights. New competitive information.  If you don’t get the right team put together, you’ll find someone longing for the good old days and their old dusty reports.  Or worse yet, still finding ways to generate those old dusty reports. Mistake 2.  Not having the right talent to design, build, run and update your analytics system.  It is undeniable that there is now high demand for business analytics specialists.  There are not a lot of them out there that really know what to do unless they’ve been burned a few times and have survived and then built successful BA systems.  This is reflected by the fact you see so many analytics vendors offer, or often recommend, third-party consulting and training to help the organization develop their business analytic skills.  Work hard to build a three-way partnership between the vendor, your own team, and an implementation partner.  If you develop those relationships, risk of failure goes way down.

Mistake 3.  Putting the wrong kind of analyst or designer on the project. This is somewhat related to Mistake 2 but with some subtle differences.  People have different skillsets so you need to make sure the person you’re considering to put on the project is the right “kind.”  For example, when you put the design together you need both drill-down and summary models.  Both have different types of users.  Does this person know how to do both?  Or, for example, inexperience in an analyst might lead to them believing vendor claims and not be able to verify them as to functionality or time to implement. Mistake 4.  Not understanding how clean the data is you are getting and the time frame to get it clean.  Profile your data to understand the quality of your source data.  This will allow you to adjust your system accordingly to compensate for some of those issues or more importantly push data fixes to your source systems.  Ensure high quality data or your risk upsetting your customers.  If you don’t have a good understanding of the quality of your data, you could easily find yourself way behind schedule even though the actual analytics and business intelligence framework you are building is coming along fine. Mistake 5.  Picking the wrong tools.  How often do organizations buy software tools that just sit on the shelve?  This often comes from management rushing into a quick decision based on a few demos they have seen.  Picking the right analytics tools requires an in-depth understanding of your requirements as well as the strengths and weaknesses of the tools you are evaluating.  The best way to achieve this understanding is by getting an unbiased implementation partner to build a proof of concept with a subset of your own data and prove out the functionality of the tools you are considering. Bottom Line.  Think things through carefully. Make sure you put the right team together.  Have a data cleansing plan.  If the hype sounds too good to be true—have someone prove it to you.

sudo su

/etc/init.d/apparmor stop update-rc.d -f apparmor remove apt-get remove apparmor apparmor-utils

groupadd mysql useradd -r -g mysql mysql

memory_limit - Recommended setting: 512M or higher. The memory_limit parameter mainly comes into play when executing large transactions such as mass update, export and import. If this setting is too low when trying to perform one of these actions, the end user will encounter a fatal error and the process will not complete. upload_max_filesize and post_max_size - Recommended setting: 30M or higher. Both of these settings work in conjunction with each other when uploading files through SugarCRM which includes future upgrades as well as document and note attachments. Please note that there is also a setting in the application which can limit file upload file size for end users so the settings in PHP should be high enough to allow any future upgrade files to be loaded without error. max_execution_time = Recommended setting: 300. This setting controls how long a PHP process will remain active. It is important to set this parameter to a value that will allow for large requests to complete if necessary but also will not hamper performance of the server if running too long.

In regards to PHP setup, the following parameters should be set with values as indicated:

Maximum upload size Admin > System Settings 30000000 (~30 MB) The 'Maximum upload size' controls the maximum file size your users can upload into Sugar. This setting should not exceed the post_max_size and upload_max_filesize parameters in your PHP configuration.

# cd /etc/yum.repos.d # wget http://public-yum.oracle.com/public-yum-el5.repo

Open the yum configuration file in a text editor Locate the section in the file for the repository you plan to update from, e.g. [el4_u6_base] Change enabled=0 to enabled=1

One of the most challenging aspects of performance tuning is knowing where to begin. To maximize Oracle® Business Intelligence Enterprise Edition performance, you need to monitor, analyze, and tune all the Fusion Middleware / BI components. This guide describes the tools that you can use to monitor performance and the techniques for optimizing the performance of Oracle® Business Intelligence Enterprise Edition components.

SuiteCRM was forked from the 6.5.x branch of SugarCRM because a segment of the community felt that SugarCRM Inc. was paying too much attention to its commercial editions and dragging its feet on updating the community edition. In addition to packaging up the latest SugarCRM codebase, SuiteCRM added a number of third-party extensions, resulting in a new system that is comparable to SugarCRM Professional in terms of features and functionality.