- About us
- Services
- Skills
- Web Development
- ColdFusion Development
- SharePoint Development
- Classic ASP Development
- ASP.NET Development
- Modern ASP .Net Development
- DotNetNuke Development
- Java/JSP/servlets Development
- Python Development
- PHP Development
- Perl Development
- Ruby on Rails (RoR) Development
- Lasso Development
- Real Basic Development
- Google API Integration Services
- Mobile Development
- Database & Client server Development
- Plug-in Development
- Reports/BI Development
- Automated Testing
- QA/Testing Skills
- Domain-based Testing
- E-Commerce Development
- CMS Development
- Desktop Development
- RIA Development
- App-based development
- Salesforce Development
- SugarCRM Development
- Dynamics GP GreatPlains development
- Dynamics SL Solomon development
- Microsoft Dynamics CRM Consulting Development
- Dynamics RMS development
- LiveCycle development
- QuickBooks development
- Drupal development
- Joomla development
- Typo3 development
- Magento development
- Dolphin social development
- Others
- Web Development
- Industries
- Knowledge
- Process
- Models
- Clients
- Career
| |
|
Commerce Server: Packaging Existing Site Using SitePackager
The Commerce Server deployment tool Site Packager is used to package your Site, its applications and its resources to a single file. Now this single PUP file can be moved to any other environment and unpacked there for fresh installation. The SitePackager also used to unpack the single file.
When you package a site, you save your applications and settings in a single package file with a .pup extension.
Follow the steps given below to package an existing Site using SitePackager
STEP – I
Click Start > Programs > Commerce Server 2009 > Tools > Site Packager.
STEP – II
On the Welcome to the Commerce Server Site Packager page, select Package an existing site, and then click Next.
STEP – III
Select the existing Sitename from the DropDown to Package and specify the location where the PUP file will be generated at the 'PackageSite' page.
Now click the Next button present at the lower part of the page.
STEP – IV
We can specify the script to create schema elements for the Profile System or add data to the Profiling System if the Profiles resource was added to the site that we are packaging.
|
For |
Do this |
|
Schema definition scripts |
Export the definitions (schema) from the SQL database to a .sql file, and then specify the name of that file here. When you unpack your site, you will specify this file so the definitions will be unpacked into the Profiles tables in the runtime data stores . |
|
Data population scripts |
Export the profile data from the SQL database to a .sql file, and then specify the name of that file here. When you unpack your site, you can specify that .sql file to populate your Profiles tables in the runtime data stores. |
Now click OK after specifying the sql file locations.
STEP – V
Now the Packaging continues showing the following window on the screen.
After this the final Finish page appears with the informations about the SQL databases created and the IIS application created.
STEP – VI
Finally press the Finish button to close the SitePackager.
