SalesForce Integration and Environment in Cloud Computing


An environment in Force.com lets you develop and test your cloud computing application immediately without any delay and without touching even a single server. So an environment lets you deploy or create applications with different features depending on its configuration.

Few significant characteristics of an environment:

  • Used for development, testing and production.
  • Contains data and customizations.
  • All environments can be accessed through a web browser.
  • Each environment is based on an edition.


Custom Domain names lets you run your own website on a platform.


We perform all these through point & click mechanism

  • Sales force provides a special type of test
  • Developer’s responsibility is to test ‘test method

     ↓→   It Governs the  limits and based on this, execution  works from the starting till the ending

We must write and select the test method

    ↓→  Must practice best only (we have to work on all these test methods).

  • We can have ’n’ number of test methods in a single program
  • Every test method will work in system mode and not in user mode as they work against the govern limits

G .L worst work -> Ajax  -> test the code -> G.L will work love



  • We can convert the test mode from system mode to user mode

To achieve this,

  1. We use test method
  2. System. Run As (user 1)

     The  ↓→    Special method is used to run at user mode




 By default apex & VF will execute in system mode only, if we want to execute apex & VF in user mode then perform the operation again back to the system mode

  • In sales force, there is a standard class termed as ‘user’

       → System.runs AS    (user) ↑   ↑→    S object

User clerk = [select  an ID from the user where,  first name = ‘OSEARIT’ limit 1]

System.runs As [clerk] {

  • The limit will restrict the records
  • We can share the limit b/w statements
  • The run As method will work inside the test method only

      Public test method static void main (){

   System. run As (clerk) {



An Apex annotation adapts the manner in which a method is used.

Annotations are used to give additional information to the compilers at the run time. Annotations illustrated with an initial @symbol followed by a certain appropriate keyword. @isTest annotation defines a method that contains the code used for application.

  • @ is Test → annotation
  • @ is Test → to test the performance of  a single test



         Global class annot {

          @is test

          Public static void test me (){

          System. Debug (‘hello, hi’);


          Test method {

          Test. Start test ()   ]

          |   →   Write inside the test method only

          Test. Stop test ()    ]


         In this we can double the governor limits

  • In each test method we shall only perform this once and not more than it
  • Apex provides batch apex, where we can work up to 15 million records
  • We can run multiple batch Apex’s at a time
  • Schedule apex:- executes at a specific time
  • We can get the features of the OS through interfaces
  • Apex provides interfaces
  • Apex utilizes the OS features

SalesForce Integration

Integration between several related apps helps the organization to achieve efficiency, consistency and quality in real time.

      ↓→  Different app’s



Collection of resources to serve these applications


MANAGED: We can add new features even after release

UN NAMED: Develops and provides


Salesforce creates copies of your organization in separate environments.It uses them for development and testing. Different types of sales force.com sand box supports different activities. Sand Box is completely isolated from the Salesforce production organization.  Its types are:

  • Full Sandbox
  • Partial copy Sandbox
  • Developer Pro Sandbox
  • Developer Sandbox

There are two kinds of sales force.com environments

  • Production environment
  • Sandbox environment


The Sand box is an environment stored by sales force.com for the testing and the development purpose and is mostly used by developers and testers


Production is an environment where the actual users work with the actual data and is maintained by administrators

  • Migration from sandbox to production environment can happen via ellipse tall or SFDC, where change sets eclipse toll is a much more recommended approach
  • There are three kinds of sand boxes in SFDC and the difference lies at the limit of data storage


This is the most basic sand box provided by SFDC. This comes as free and can be created by a single developer. Multi users can log in and share this single developer Sandbox.

It can store 10 MB of data and can be refreshed every day (features of winter 11 release), this sandbox can be created from PRD environment


This is a paid sand box and costs around 10% of production environment, this is mostly used when the system needs to be tested with a good check of the data

This sandbox can be created directly from the production environment and can be refreshed every day. This sand box has the data limit up to 500mb.


This is also a paid sand box and costs around 15% to 20% of PRD environment. The full copy sand box of SFDC is an exact replica of the production environment and even stores the actual business data.

This sandbox can be created from the SFDC Prd environment and can be refreshed after every 28 days. The full copy sand box has same data limit as the PRD environment has.

  • From sand box, the project will move to PRD

            Sandbox  →  PRD

            ↓→    This process is called deployment


Deployment is a connection between two sales force environments to move, change sets from one environment to the other environment.

  • PASS

           Force.com  (development environment)



→ Eclipse IDE provides an environment, where we write the code, test and deploy the code

  • While sharing, it executes an Apex programming as per the profiles and page layouts
  • Whereas without sharing, it works in system mode


Annotations are used as additional information to the compilers at the run time

  • @ is test à annotation

          Are used to test the performance of a single test



                Global class all  {

                @ is test

                Public static void test me () {

                System.debug (‘hello, hai Ashok’);


Enroll For Instructor Led Live SalesForce Training @ Mindmajix

0 Responses on SalesForce Integration and Environment in Cloud Computing"

Leave a Message

Your email address will not be published. Required fields are marked *

Copy Rights Reserved © Mindmajix.com All rights reserved. Disclaimer.