+ Start a Discussion
saisaisaisai 

Org newbie questions

Just wondering if someone can pour some light on these questions:

 

1. Is org like a process on force.com server or is it like a deployement dir or is it like a codebase of our apps we created on the server where the code operates from could u explain from a .net or java developer perspective.

 

2. When we open an account and start developing the data objects r we working on dev org or is it sandbox org.

 

3. How to migrate this to production.

 

4. When we create and account in devforce and do some development and later if we would like another user to test using his email how to access our objects or should we share our username & pwd with them. In other words if we have a dev user and test user and we need to be able to test in parallel how to achieve this.

 

Any input it highly appreciated.

Please help.

Thanks

Sai

Best Answer chosen by Admin (Salesforce Developers) 
AroraAnupAroraAnup

Will try my best to answer your questions:

 

1. Is org like a process on force.com server or is it like a deployement dir or is it like a codebase of our apps we created on the server where the code operates from could u explain from a .net or java developer perspective.

 

ORG is basically your Salesforce.com Instance. Its the environment assigned to you/your organization once you sign up for Salesforce.com licenses, on the Salesforce.com servers. If you understand the whole "Multi-tenancy Architecture", in more layman terms, consider the Salesforce.com server as an apartment building, where multiple tenants live together in their own individual apartments but use shared resources like gym, swimming pool, bbq pits etc :)
This link will help you more in understanding the Multi-Tenancy Architecture of Force.com - http://wiki.developerforce.com/page/Multi_Tenant_Architecture

2. When we open an account and start developing the data objects r we working on dev org or is it sandbox org.

 

Depends. If you are using a Free SFDC account, you are probably working on a Dev org. As part of an implementation, all developments are done on the Sandbox environment and are then migrated/deployed to Production.

3. How to migrate this to production.

 

There are several ways to migrate your configurations & customizations from Sandbox to Production - Change Sets, Eclipe, Force.com IDE, Ant etc.

4. When we create and account in devforce and do some development and later if we would like another user to test using his email how to access our objects or should we share our username & pwd with them. In other words if we have a dev user and test user and we need to be able to test in parallel how to achieve this.

 

Ideally, in an implementation scenario, it is good to have multiple environments so that Testing is not impacted during Development or vice-versa. SFDC never advises you to share passwords and it is recommended that the Testing team has their own access to Salesforce.com. Normally, the following environments are considered:

1. Development environment (Can be a Dev-only Sandbox) where all development is done
2. Testing environment (Can be Dev-only or Fullc-copy sandbox so that testing can be done with considerable data volume) No development is done here and all code changes are deployed from Developer Sandbox
3. UAT environment (for the business to do the UAT) No development is done here and all code changes are deployed from Testing Sandbox
4. Production

 

Hope this helps. Do click KUDOS if this post helps you!