Difference between revisions of "Set up CRM2"
(→First Steps) |
(→Setting up for opentaps 1.x) |
||
Line 35: | Line 35: | ||
=== Setting up for opentaps 1.x === | === Setting up for opentaps 1.x === | ||
− | + | If you are using an older AMI which does not have "crm2" in its name, or if you are running opentaps on your own server, then you will have to get the code for crm2. You can check it out of our subversion repository into the opentaps/ directory (opentaps 1.5) or hot-deploy directory (earlier versions) like this: | |
<pre> | <pre> | ||
Line 73: | Line 73: | ||
opentaps/purchasing/widget/purchasing/screens/supplier/SupplierScreens.xml | opentaps/purchasing/widget/purchasing/screens/supplier/SupplierScreens.xml | ||
</pre> | </pre> | ||
+ | |||
+ | Then, follow the instructions above to configure your <tt>crm2/config/crm2.properties</tt> file and restart opentaps. |
Revision as of 23:35, 15 October 2013
First Steps
This shows you how to set up opentaps CRM2
The first step is to request an account with an API key by contacting us.
Once you have received your permanent authorization token key by email, reset it
$ curl -X POST 'https://crm2.opentaps.com/admin/reset-token' -d clientDomain= ${yourDomain} -d authToken=${authToken}
Keep your new auth token secret! Someone with this token will be able to access everything in your account.
Setting Up with opentaps in the Cloud
If you are using an opentaps in the Cloud Amazon EC2 instance from an instance which says "crm2", then CRM2 is already pre-loaded for you. Simply edit the file hot-deploy/crm2/config/crm2.properties and populate your settings:
crm2.activities.widget.baseOpentapsUrl = https://your-ec2-instance-ip.compute-1.amazonaws.com crm2.activities.widget.authToken = your-auth-token-value crm2.activities.widget.clientDomain = your-domain.com
Then, restart opentaps
$ /etc/init.d/opentaps restart
You should see an activities widget similar to those from Tour of CRM2 in your CRM system.
Setting up for opentaps 1.x
If you are using an older AMI which does not have "crm2" in its name, or if you are running opentaps on your own server, then you will have to get the code for crm2. You can check it out of our subversion repository into the opentaps/ directory (opentaps 1.5) or hot-deploy directory (earlier versions) like this:
$ svn co svn://svn.opentaps.org/opentaps_crm2/opentaps_1.5/crm2 crm2
Out of the box, this code works for opentaps 1.5. If you are using opentaps 1.4 or earlier versions, you will need to replace some of the lines which are for opentaps 1.5 with those for earlier versions. Edit the file src/com/opentaps/crm2/ContactExportService.java and search for "opentaps 1.5" and follow the instructions to comment out and uncomment the appropriate lines.
Next, compile the new module with
$ ant
Add the new module to either opentaps/component-load.xml or hot-deploy/component-load.xml file with
<load-component component-location="crm2"/>
Uncomment lines between
<!-- Uncomment to use Crm2 application and -->
in the following files:
opentaps/crmsfa/webapp/crmsfa/orders/viewOrder.ftl opentaps/crmsfa/widget/crmsfa/screens/accounts/AccountsScreens.xml opentaps/crmsfa/widget/crmsfa/screens/contacts/ContactsScreens.xml opentaps/crmsfa/widget/crmsfa/screens/leads/LeadsScreens.xml opentaps/crmsfa/widget/crmsfa/screens/orders/OrdersScreens.xml opentaps/opentaps-common/webapp/common/WEB-INF/common-controller.xml opentaps/purchasing/webapp/purchasing/order/viewOrder.ftl opentaps/purchasing/widget/purchasing/screens/order/OrderScreens.xml opentaps/purchasing/widget/purchasing/screens/supplier/SupplierScreens.xml
Then, follow the instructions above to configure your crm2/config/crm2.properties file and restart opentaps.