How can I commit my local m/c code to staging?

Question

Hi
How can we commit local m/c code to staging? Do we have to publish code from local m/c to staging environment? or is there some different procedure?
Thanks

Answer 1

Publishing is a step by step process.
in high level i can Say in 4 steges:
stege1:  you will make your Delivery System Ready.
stege2: You'll move Site Configuration Data to the Destination Database(this time what are all the Tables(assettypes) are in your source system will be created in Delivery system). Site level Information
stege3:You'll approve list of asset to be moved to Delivery system.
stege4:You'll publish(move) the List of assets which you approved in previous step.
In your case you got stopped  in stege 2 i thinks(reason as i know Some of the table have already been created in you delivery system, when you try to do the same step again , it is giving error)
And,
Though you  didn't get a SUCCESS from the Contribution System, You can see list of sites in your delivery system, why because(as you are in stege2) some of the table are already moved. So you can able to see some sites in your delivery system even though your publishing process failed.
Delete the Site completely in Delivery System which is partially published.
Then check with the  bellow steps:
step 1: Create the Batch User Account (If One Does Not Exist):
A batch user account is required before any type of publishing can take place. We can use fwadmin user account for publishing. If we want another separate user follow this step:
Log in to the administrator’s interface on your source system.
In the Admin tab, expand Management Tools and double-click User.
Assign following ACL’s for the above created User:
Browser
ElementEditor
PageEditor
TableEditor
UserReader
Visitor (if your installation includes Oracle WebCenter Sites: Engage)
VisitorAdmin (if your installation includes Oracle WebCenter Sites: Engage)
-xceladmin
–xceleditor
Step 2: Create the RealTime user on the destination system:
For publishing we can use fwadmin user account in destination system. It is always advisable to create a specific user for destination system by following the below steps:
In delivery system Log in to the administrator’s interface on your source system.
In the Admin tab, expand Management Tools and double-click User.  
Provide the basic privileges for the above created User by assigning following ACL’s
Browser
ElementEditor
PageEditor
TableEditor
Visitor
VisitorAdmin
xceladmin
xceleditor
Step 3: If a Proxy Server Exists, Identify it to the Source System
To identify the local proxy server to the source system for all destinations
1. Open futuretense.ini in the Property Editor on the source system, select the Export/Mirror tab, and specify values for the following properties:
cs.mirrorproxyserver
Set this property to either the name or the IP address of the local proxy server.
cs.mirrorproxyserverport
Set this property to the port number of the local proxy server.
2. Save the property file and close the Property Editor.
3. Restart the application server.
To identify the local proxy server to the source system per destination
1. In the Admin interface, select the Admin tab. Expand Publishing, then expand Destinations, and open the destination.
The destination opens in the main screen.
2. Click Edit.
The “Edit Destination” screen for the destination displays.
3. In the More Arguments field, enter
PROXYSERVER=wcs.example.com&PROXYPORT=8080
Where wcs.example.com is the local proxy server, and 8080 is the port the proxy is
running on.
4. Click Save.
If no proxy server exists then this step is optional and not needed.
Step 4: Identify the Mirror User to the Source System:
Identify the name and password of the mirror user on the destination system to the source system by setting property values in the futuretense.ini file on the source system.
1. Start the Property Editor and open the futuretense.ini file on the source Sites system.
2. In the Export/Mirror tab specify values for the following properties:
cs.mirroruser= above created user of destination system
cs.mirrorpassword=password of above user
                       3. Save the property file.
Step 5: Create a RealTime Destination Definition on the Source System
To create a RealTime destination definition
1. On the source system, log in to the administrator’s interface.
2. In the Admin tab, expand Publishing, then Destinations.
3. Under Destinations, double-click Add New.
  4.fill the details.then " add new Destination"
Step 6: Initialize the Destination Database:
You must initialize the destination database before you can publish to it.
To initialize the destination database follow the below steps
               1. In the Admin tab on the source system, expand Publishing, then Destinations.
               2. Under Destinations, double-click the RealTime destination you want to initialize.
               3. In the “Publish Destination” form, click Initialize RealTime Destination.
                    The “Initialize RealTime Destination” screen appears:
               4.click on  "Initialize RealTime Destination" only once.
Step 7: Mirror the Site Configuration Data to the Destination Database
In this step, we will mirror the source’s site configuration data (such as asset types and start menu items) to the destination database.
To mirror the site configuration data follow the below steps:
1. In the Admin tab on the source system, expand Sites and double-click the site whose data you want to publish to the destination.
2. In “Publish Destinations” (near the bottom of the screen), click Mirror site
configuration for destination
Step 8: Approve Assets(Bulk approval)
We can approve single asset or multiple assets for publishing. For approving group of assets follow below steps:
1. In the Admin tab, expand Publishing, then expand Destinations, and then expand the destination that you want to approve assets for.
2. Under that destination, double-click the Approve Multiple Assets option.
The “Approve Assets” form appears:
3. select the list of assets you want approve for publishing.
Step 9:Publish the Assets
To run a test publishing session on the approved assets
1. On the source system, Select the "Admin" app , then click "Publishing" in the button bar.
2. In the Publish Console, select your RealTime destination from the drop-down list and
click Select Destination.
3. WebCenter Sites displays information about the assets that are ready to be published
to this destination.
4. Click Publish.
After this log in to Delivery system, assign user to Site and give the ACLs and Roles.
Refresh it.
You can find your Site in Destination.
Please let me know if you have any issue.
Thanks,
Rajendar Pilli.