| Oracle® Fusion Middleware User's Guide for Site Studio Designer 11g Release 1 (11.1.1) E10613-01 |
|
 Previous |
 Next |
Home > User's Guide for Site Studi... > Working With Definitions
| Oracle® Fusion Middleware User's Guide for Site Studio Designer 11g Release 1 (11.1.1) E10613-01 |
|
Previous |
Next |
Home > User's Guide for Site Studi... > Working With Definitions
The templates (page templates, subtemplates, region templates) are used to control how data is displayed. The definitions - placeholder definitions, region definitions, and element definitions - control which data is presented, and additionally control how the contributor interacts with the data.
This section covers the following topics:
When a definition is used, it then prescribes what can be contained in the asset the definition is associated with. Placeholder definitions specify which region templates, region definitions, and subtemplates can appear in a placeholder, region definitions specify which elements can appear in a region template, and element definitions control how the contributor can modify the data within the contributor data file.
This section covers the following topics:
Placeholder definitions are what connect each placeholder to the content and other assets associated with that place holder to display. Since the placeholder is simply a marker on the page, the placeholder definition is used to determine whether a contributor can edit the content displayed within the placeholder, if they can view reports, and other actions.
Additionally, the placeholder definition includes the region definitions that can be used within the area of the placeholder (also called a contribution area), and these region definitions are then connected to one or more region templates that are also controlled in their availability by listing them in the placeholder definition.
A subtemplate, which is a section of HTML that may include multiple placeholders (and by association other placeholder definitions), can also be listed as available in the placeholder definition. A subtemplate can be used in the contribution region instead of a region definition and a region template.
The placeholder definition controls which region definitions are available within the placeholder. By including more region definitions in the placeholder definition, then you have more options to use the region definition as a method of controlling the data file assigned to the contribution region.
Templates, such as region templates, subtemplates, and page templates, are used to control how the associated data is displayed. Definitions, such as region definitions, placeholder definitions, and element definitions, control what data is displayed, and how the contributor interacts with that data.
See "Working With Placeholder Definitions" for more information.
The typical region definition contains multiple elements, and various combinations of these elements are used on several different region templates. Each region definition contains a list of the elements available to place on the associated region template. This enables multiple region templates to access the same grouping of elements (but it does not have to be the same data file) and arrange them in different ways.
Because the region definitions limit the availability of elements in the contribution model, it is especially important to follow good naming conventions for region definitions. It is possible that you have more region definitions than any other site asset. A good naming convention helps you sort out which definitions are best suited for the different region templates you create without having to open multiple region definitions and see what exactly they do.
Since the creation of a region template requires you associate it with a region definition, it is recommended that you create region definitions first, then create region templates.
See "Region Definition Dialog" and "Working With Region Definitions" for more information.
Elements are the objects used to define how the contributors can edit the data. The available elements are WYSIWYG (What You See Is What You Get), plain text, image only, static lists, and dynamic lists. You can also create custom elements that can be used for several situations, including processing data-driven site creation.
To create a definition, perform these tasks:
In the menu on the Site Assets pane, select the definition type.
Click the Create New icon (Figure 9-1), select New, and then the definition type.
The Assign Info Form displays for you to check the item into the content server.
Enter appropriate values for the Assign Info Form.
For guidelines on naming Site Studio assets, see "Naming Site Assets".
When complete, click Assign Info.
The definition is created.
Editing each definition uses different interfaces. Each interface maximizes the ease in making the changes specific to the type of definition you are working with.
This section includes the following topics:
The placeholder definition should contain the region definitions, region templates, and subtemplates that would be used to control the content used in the contribution region.
To edit a placeholder definition, perform these tasks:
In the menu on the Site Assets pane, select Placeholder Definitions.
From the list, select the placeholder definition to be edited and click the Edit icon (Figure 9-2).
The placeholder definition dialog opens. See "Placeholder Definition Dialog" and "Working With Placeholder Definitions" for more information.
Enter a description for the placeholder definition. You should use a good naming convention for placeholder definitions. If you can understand what the placeholder definition does from the name, then you won't have to view the definition each time you consider using it.
Select or deselect the actions you want to allow with the placeholder definition. All of these actions impact how the contributor works with the contribution region.
In the allowed region definitions, click Add to add a region definition, and a region template.
In the allowed subtemplates, click Add to add a subtemplate.
Click Remove in any section to remove the selected region definition, region template, or subtemplate, as applicable.
When editing the placeholder definition, you should keep the region definitions, region templates, and subtemplates in mind.
See "Placeholder Definition Dialog" and "Working With Placeholder Definitions" for more information.
When the region definition has been created, you can open it to include the element definitions you need.
To edit a region definition, perform these tasks:
In the menu on the Site Assets pane, select Region Definition.
From the list, select the region definition to be edited and click the Edit icon (Figure 9-3).
The region definition dialog opens. See "Region Definition Dialog" for more information.
Enter a description for the region definition.
Click Add to add elements to the region definition.
The element dialog opens.
The Name you give the element is the name used to identify the element within the region definition, and in any other site assets that refer to this region definition.
The Label you give the element definition is the name of the element (located in the toolbar) in Contributor.
The Info you enter for the element you add displays as a tooltip when the contributor hovers the mouse over the Label.
Select an element and click Remove to remove an element.
Select an element and click Move Up or Move Down to change the order of elements in the region definition.
The order of elements is the order that they display in when Contributor is opened for the contribution region based on this region definition.
In this dialog, you should include all of the elements you want to include in the region definition. You can use and place these element definitions in the region template when the region template and region definition are associated.
See "Working With Region Definitions" for more information.
To edit an element definition, perform these tasks:
In the menu on the Site Assets pane, select Element Definitions.
From the list, select the element definition to be edited and click the Edit icon (Figure 9-4).
A dialog opens that enables you to edit the selected element definition. Depending on the element type, one of these screens is displayed:
Enter the info for the element definition. This is a short description of the element to help you remember how the element definition was set up. The information you provide here helps you remember, at a glance, which specific settings you have placed in the element definition. This is especially helpful if you have created multiple similar element definitions with only slight differences in the actions from each other.
Select or deselect the actions you would like to allow the contributor to have for the selected element definition.
If you are creating a custom element, the process is different.
In each case, the main focus of the editing is to select which objects are available to the contributors on the toolbars. Each element you define has its own toolbar, and what appears on the toolbar (for example, toolbar buttons allowing changes to font size, font style, paragraph formatting, and so forth) is defined when you select or clear the checkboxes in the actions list of an element definition.
It is recommended that you have multiple definitions of each type, to allow for different toolbars that the users can have in different instances. For specific information on the actions available to modify in each element definition, see the specific screen listed above.
It is simple to copy a definition from one you have already made, allowing you to modify one or two aspects of it to make asset creation go much faster.
To copy a definition, follow these steps:
Copying a Definition from the list
In the menu on the Site Assets pane, select the definition type.
Select the definition you want to copy from the list.
Click the Create New icon (Figure 9-5), select Copy, and then Selected:
The Assign Info Form displays for you to check the item into the content server.
Enter appropriate values for the Assign Info Form.
When complete, click Assign Info.
The definition is copied.
When the definition has been copied, it can then be opened to edit.
Copying a Definition from the server
In the menu on the Site Assets pane, select the definition type.
Click the Create New icon (Figure 9-5), select Copy, and then from Server.
A search results page displays.
Click the corresponding Select button of the ones you want to copy.
The Assign Info Form displays for you to check the item into the content server.
Enter appropriate values for the Assign Info Form.
When complete, click Assign Info.
The definition is copied.
Copying a Definition from your local instance
In the menu on the Site Assets pane, select the definition type.
Click the Create New icon (Figure 9-5), select Copy, and then from Local.
An open file dialog displays.
On your local instance, navigate to the definition you want to copy.
Select the definition and click Open.
The Assign Info Form displays for you to check the item into the content server.
Enter appropriate values for the Assign Info Form.
When complete, click Assign Info.
The definition is copied.
To view content information for a definition, perform these tasks:
In the menu on the Site Assets pane, select the definition type.
Select a definition from the list.
Click the Doc Info icon (Figure 9-6).
To add a definition to a site, perform these tasks:
In the menu on the Site Assets pane, select the definition type.
Click the Add to Site icon (Figure 9-7).
A search results page displays.
Select the definition or definitions to add, click Site Studio, and then Select Marked Documents.
Depending on your configuration, you may receive a caution that you are about to add existing asset(s) to your site. Click OK.
The definition is now associated with the Web site, and you can now open the definition to edit.
To remove a definition from a site, perform these tasks:
In the menu on the Site Assets pane, select the definition type.
From the list, select the definition to be removed and click the Remove From Site icon (Figure 9-8).
When you remove a definition, you are simply removing it from the site, not deleting from the content server.
When you insert a placeholder on a page template, it is simply a named marker where content displays. The placeholder definition controls how the data displays in the placeholder. Placeholder definitions also control if the contributor can approve or reject the assets in workflow, if the contributor can view web reports, if the contributor can edit the assets in the placeholder, and more.
The relationship between the placeholder name and the placeholder definition is called the mapping. These mappings are used to determine the placeholder definition used as the default when you create a new placeholder.
The mappings can be done in four ways. A default mapping is defined in the Web site properties under the Default Placeholder Definition. If a mapping is made here, then it is the one used between a placeholder definition and a placeholder name if none of the other three mappings have been defined.
A global mapping, made in the Placeholder Definition Mappings dialog (see "Placeholder Definition Mappings Dialog"), establishes a default mapping for the placeholder name throughout the site. The placeholder name can be used on multiple templates in multiple sections, and the same mapping applies.
A section property mapping is defined in the section properties under the Primary Page Placeholder Definition Mappings and Secondary Page Placeholder Definition Mappings. The section this is done in now uses a different mapping from any other section where the placeholder is used. The section property mapping overrides a global mapping and a default mapping, but not a mapping in a tag.
The fourth method of creating a mapping is by defining the mapping in the placeholder tag itself. This type of mapping overrides all other mappings, including global mappings. When you define a mapping in the placeholder tag, you are making a change to the placeholder tag in source view. When you use a mapping this way, this means that every time the page template is used, the placeholder on the template always uses the specified placeholder definition regardless of where in the Web site the page template is used.
What the contribution region identified by the placeholder contains, and how it looks on the site, is defined using region templates and region definitions (see "Region Templates and Region Definitions"). A page template may contain multiple placeholders, each of which represents a contribution region on the page. There are no files associated with placeholders; that is, there are no "placeholder files" on the content server.
This section covers the following topics:
"Creating a Section Property Placeholder Definition Mapping"
"Specifying a Placeholder Definition Directly in the Placeholder Tag"
"Associating a Placeholder with a Global Placeholder Definition"
"Associating a Region Template with a Placeholder Definition"
The default placeholder definition is the placeholder definition used when no other mappings apply. It is considered more of a "catch-all."
To specify a default placeholder definition, follow these steps:
In the Web Site Properties, click in the Default Placeholder Definition.
Click the additional information icon that appears.
A content server search displays, showing the available placeholder definitions.
Select the placeholder definition to use as the default.
The default placeholder definition appears in the Web site properties.
The list of available global placeholder mappings are defined on the Placeholder Definition Mappings dialog (see "Placeholder Definition Mappings Dialog"), which is available by selecting Tools from the menu bar, then selecting Define Placeholder Definition Mappings. The placeholder mappings allow a placeholder to have a different definition depending on whether the placeholder is used on a primary or a secondary page. The mappings are stored in the project file for the Web site.
The global placeholder definition mapping overrides the mapping created as the default placeholder definition in the Web site properties (see"Specifying a Default Placeholder Definition").
To create a global placeholder mapping, follow these steps:
From the menu bar, select Tools, and then Define Placeholder Definition Mappings.
The Placeholder Mappings dialog opens (see "Placeholder Definition Mappings Dialog").
Click Add to create a new mapping.
The Define Placeholder Definition Mapping dialog opens (see "Define Placeholder Definition Mapping Dialog").
Enter a placeholder name that is easy to recognize, and also helps you understand what the mapping does. In the two menus, enter a placeholder definition that the placeholder uses on a primary page and on a secondary page. You can enter for either a primary page or a secondary page, or both.
Click OK.
Your placeholder definitions now display in the Placeholder Mappings dialog, and are available to select when you insert a placeholder.
The section property placeholder definition mapping lists the mapping between a placeholder name and a placeholder definition. The section this mapping is in uses a different mapping from any other section where the placeholder is used.
The section property placeholder definition mapping overrides the global placeholder definition mapping and the default placeholder definition.
There are two ways to make this section property, by using a dialog, and by entering the placeholder name and placeholder definition directly in the section properties. The dialog uses a friendlier user interface.
To create a section property placeholder definition mapping using the dialog, follow these steps:
Right-click a page template within the appropriate section in the hierarchy. In the menu, select Placeholder Section Properties...
The Placeholder Section Properties dialog opens (see "Placeholder Section Properties Dialog").
Click Add.
The Edit Placeholder Section Properties dialog opens (see "Edit Placeholder Section Properties Dialog").
Enter the Name, and the placeholder definition ID . If you want to include a region template, subtemplate, or contributor data file in the section property, add those as well.
Click OK to close the Edit Placeholder Section Properties dialog.
The section property placeholder name mapping is created.
Click OK to close the Placeholder Section Properties dialog.
To create a section property placeholder definition mapping directly in the section properties, follow these steps:
View the section properties for the section you want to create the mapping in.
In the Primary Page Placeholder Definition Mappings, enter the placeholder name and placeholder definition in this format:
name=contentID
where the name is the placeholder name, and the content ID is the content ID of the placeholder definition. To enter multiple placeholder names and placeholder definitions, use an ampersand ('&') between each pairing, in this manner:
name1=contentID1&name2=contentID2&name3=contentID3
For the secondary pages, enter a placeholder name and placeholder definition for the Secondary Page Placeholder Definition Mappings. Multiple name and definition pairings are allowed just as in the Primary Page Placeholder Definition Mappings.
The Primary and Secondary Page Placeholder Definition Mappings display in the section properties.
The placeholder tag can be written so that the placeholder definition is specified explicitly in the placeholder tag. This direct specification is used each time the page template is used.
This method of correlating a placeholder definition and a placeholder tag overrides all other placeholder definition mappings.
To specify the placeholder definition directly in the placeholder tag, follow these steps:
Open the page template that contains the placeholder.
Click the Source View tab.
In the placeholder tag, enter the mapping in this manner:
<!--$wcmPlaceholder("Sales", "placeholderDefinitionDocName=placedef_salescontact")-->
In this example, the placeholder name is Sales, and the placeholder definition content ID is placedef_salescontact.
The mapping is now created in the tag.
You can also assign a placeholder definition to be written in the tag from the Define Placeholder dialog (see "Define Placeholder Dialog"):
Open the page template that contains the placeholder.
Double-click the placeholder.
The Define Placeholder dialog opens.
You can also do this by inserting a new placeholder.
The name in the menu is the name of the placeholder you selected (unless the placeholder is new). Check the Optionally specify the placeholder definition on the template check box.
The dialog expands. Select the placeholder definition to map in the placeholder tag from the menu.
The mapping is now created in the tag.
When you have created the placeholder mappings, the placeholder definition is associated to placeholders you create according to the mappings.
By using a different placeholder definition in a placeholder, you can use different subtemplates, region templates, or allow for some instances of a placeholder to be available to contributors for editing, or any other aspect that has been defined in your placeholder definition.
To associate a placeholder with a global placeholder definition, follow these steps:
Insert the placeholder on the page template (see "Inserting Placeholders")
As you insert the placeholder, the Define Placeholder dialog (see "Define Placeholder Dialog") opens. Select a placeholder name.
Click OK.
The placeholder definition is now associated with the placeholder.
The placeholder definitions list the region definitions, region templates, and subtemplates associated (and thus available to use) with the placeholder. Adding a region definition to, or removing a region definition from, a placeholder definition is a very simple task.
When a region definition is associated with a placeholder, then only those elements that are associated with that region definition are available to use in Contributor. This is especially important to remember in those cases where you might give a contributor access to switch the region content or the region template.
To associate a region definition with a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Region Definitions pane, click Add.
The Select a Region Definition Dialog appears.
Select a region definition, and click OK.
The region definition is now associated with the placeholder definition.
When you have added a region definition, you may want to add a region template to associate with the definition.
To remove a region definition from a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Region Definitions pane, select a region definition.
Click Remove.
The region definition is now removed from the placeholder definition.
The placeholder definition lists the region definitions, region templates, and subtemplates associated (and thus available to use) with the placeholder. Adding a region definition to, or removing a region definition from, a placeholder definition is a very simple task.
When a region template is associated with a placeholder, then the region template along with the region definition used, can define the element definitions which displays the data and be available in Contributor. Region templates are used to define a specific layout of elements; when a region template is added, it must be associated with a region definition already in the placeholder definition.
To associate a region template with a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Region Definitions pane, select a region definition that the region template is used with.
In the Allowed Region Templates pane, click Add.
The Select a Region Template Dialog appears.
Select a region definition, and click OK.
The region definition is now associated with the placeholder definition.
Only those region templates that are associated to a region definition displays in the Select Region Template dialog. The association between a region template and a region definition is stored as metadata on the region template.
To make a region template the default, complete these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Region Definitions pane, select a region definition.
The Allowed Region Templates pane displays the associated region templates.
In the Allowed Region Templates pane, select a region definition.
Click Make Default.
The region template is now the default template for the selected region definition within this placeholder definition.
To remove a region template from a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Region Templates pane, select a region template.
Click Remove.
The region template is now removed from the placeholder definition.
The placeholder definition lists the region definitions, region templates, and subtemplates associated (and thus available to use) with the placeholder. Adding a subtemplate to, or removing a subtemplate from, a placeholder definition is a very simple task.
When you use a subtemplate associated with a placeholder, the site assets, and any placeholders on the subtemplate, appear on the final web page. It is not necessary to use a subtemplate.
A subtemplate can be any section of HTML comprised of static assets and placeholders, each with their own definitions. This is especially important to remember in those cases where you might give a contributor access to switch the region content or the region template.
To associate a subtemplate with a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Subtemplates pane, click Add.
The Select a Subtemplate dialog appears.
Select a subtemplate, and click OK.
The subtemplate is now associated with the placeholder.
To remove a subtemplate from a placeholder definition, follow these steps:
Open the placeholder definition from the Site Assets pane.
The Placeholder Definition dialog (see "Placeholder Definition Dialog") appears.
In the Allowed Subtemplates pane, select a subtemplate.
Click Remove.
The subtemplate is now removed from the placeholder definition.
Each region definition contains a list of associated element definitions. This list of definitions is the complete list of elements available to use in the layout of the region template, after the region template and region definition are associated.
A region template is not required to use all elements available in a region definition. Usually, not all elements are used to display in the region template. However, after Contributor is launched, all elements displays in the editor, whether they are displayed in the associated region template or not.
The association between a region template and a region definition is stored in the xRegionDefinition metadata for the region template.
Associating an element definition with a region definition
The region definitions list the element definitions available to use with the region template. Adding an element definition to, or removing an element definition from, a region definition is a very simple task.
To associate an element definition with a region definition, follow these steps:
Open the region definition from the Site Assets pane.
The Region Definition dialog (see "Region Definition Dialog") appears.
Click Add.
The Element Dialog (see "Element Dialog") appears.
Enter the information for the element (using a good naming convention to easily recognize the element definition as it is used), select the element definition from the menu, and click OK.
The element definition is now associated with the region definition.
It is also possible to embed the element definition in the region definition. When you embed the element definition, you are creating a singular instance of the named element definition within the region definition, which is not affected by global changes in the way that including the element definition by reference would.
To embed an element definition in a region definition, add it as you would normally, but on the Element Dialog (see "Element Dialog"), check the Embed the element definition inside the region definition check box.
To remove an element definition from a region definition, follow these steps:
Open the region definition from the Site Assets pane.
The Region Definition dialog (see "Region Definition Dialog") appears.
Select an element definition. Click Remove.
The element definition is now removed from the region definition.
Region definitions define the types of content used on a Web site. They are essentially groups of individual elements which define the various chunks of reusable information for a particular site content type.
In addition to defining site content types in terms of its constituent parts (elements), region definitions also specify the content creation and switching options available to contributors for its associated contribution region(s). For example, if a contribution region is set up to allow contributors to switch the content of that region, they might be allowed to use existing contributor data files on the server only (not native documents or new contributor data files). (Please note that placeholder definitions control whether contributors can actually switch content in contribution regions.) Finally, region definitions also set the default metadata for content in contribution regions as it is checked into the content server.
Each element definition is used to specify a toolbar, and any customization scripts and validation scripts you may want to include. These scripts are included when creating each element definition.
Elements are controlled by element definitions. An element is basically an instantiation of its associated element definition, which specifies the editing experience available to contributors for the element on the web page (specifically, what editing features are available in the Contributor editor). Element definitions are individually managed site assets, which means that they can be reused within a Web site, or even across Web sites (providing all sites are managed on the same content server). Elements of the same type may have different element definitions associated with them to provide different editing environments for contributors depending on the context in which the element is used. Similarly, multiple elements may share the same element definition, providing the same editing experience to contributors for each of the elements.
There are two ways to view a definition while in Designer: Source view, and Form view. Each offers a different way to look at each definition while working with that template in Designer.
In each definition window in the Designer workspace, there will be two tabs at the bottom. Select the tab to choose the Source view or the Form view for that definition.
This section covers these topics:
Form view is a graphical user interface for working with a definition. Using the form view, the different options for each definition are easily modified within the dialog. All options available to modify in form view are also available in source view.
Form view provides a dialog in which you can set the properties of definitions; for example, element definitions, region definitions, placeholder definitions, and conversion definitions. Figure 9-9 shows an example of a region definition in form view. Most form views have a Help button that you can click to see context-sensitive help information for the current form.
Source view displays the code for the definition.
The information in source view is displayed as color-coded text:
Black is used for XML code, HTML tag attributes, and text that appears on the web page.
Purple is used for HTML tags.
Blue is used for HTML tag attribute values.
Green is used for Idoc Script, HTML comments, and code inserted by Site Studio.
You can change many of these settings, including the typeface, indentation levels, and line wrapping. See "Formatting the Code in Source View" for more information.
Source view offers complete control over the site template. This can be especially true if you are implementing several custom assets. In fact, you may find yourself starting off in design view to create the page and then switching to source view to customize the appearance and behavior of the page.
Definition bundles are bundles of site assets; typically a definition and related templates. However, it can be a varying combination of definitions and templates depending on how the bundle is constructed.
This section covers the following topics:
Definition bundles are zipped (compressed) collections of definitions (and related templates, if applicable). A definition bundle is a simple method to take a related grouping of definitions and copy them to another Web site, or to a completely different content server.
The definition bundle includes the selected definition, and the related definitions below the selected definition in the hierarchy. If you bundle a selected region definition, then it will include all associated region templates, and element definitions. If you select a placeholder definition, it will bundle all subtemplates, region definitions, region templates, and element definitions associated with the placeholder definition.
When you choose to download a bundle, it is automatically zipped for you, and you will download the zipped file. There are two ways you can download a definition bundle.
You can download a definition bundle based on a selected definition directly from the site assets pane, or you can use the Oracle Content Server to select a definition and download the bundle based on that definition.
Downloading from the Site Assets Pane
To download a definition bundle from the site assets pane, perform these steps:
Select a definition (either placeholder definition, region definition, or element definition) in the site assets pane.
Right-click the definition.
A menu is displayed.
Select Download Definition Bundle.
The save dialog appears.
Name and save the bundle to the local instance.
Downloading from the Menu Bar
To download a definition bundle from the menu bar, perform these steps:
From the menu bar, select File, then Definitions, then Download.
Select either Placeholder Definition Bundle, Region Definition Bundle, or Element Definition Bundle.
Oracle Content Server search results are displayed based on the selected definition type.
Select the definition to create and download the bundle from.
The save dialog appears.
Name and save the bundle to the local instance.
When you upload a bundle in Designer, it is automatically unpacked and associated with the Web site you had open in Designer when you uploaded.
The bundle, when packed and downloaded, has the Web site you bundled it from still associated with it in the xWebsites metadata field (for more information on metadata, see the Technical Reference Guide for Site Studio). The site that is open in Designer will have its metadata value added to the xWebsites field. If you upload the bundle again, it will have the new Web site value appended to the xWebsites metadata field, and so forth. The previous value will not be deleted; this means that the site assets you upload this way will have both Web sites in the value.
If you upload through the Oracle Content Server, the bundle will not be immediately unpacked. When you upload through Designer, there is a reference point of which Web site the bundle should be associated with once unpacked. When uploading through Oracle Content Server, there is no reference for updating the xWebsites field. You will be prompted to select which Web sites to associate the content with when you unpack the bundle. Unpacking a bundle on the Oracle Content Server is a separate step from uploading a bundle.
When you go to the Manage Archives page (see the Administrator and Manager's Guide for Site Studio), you will need to further unpack it and associate it with the appropriate Web site or sites.
Uploading from Designer
To upload a definition bundle to the Oracle Content Server from Designer, perform these steps:
From the menu bar, select File, then select Definitions, then select Upload Definition Bundle....
In the Open dialog, browse to the definition bundle on your file system and then click Open.
The definition bundle is automatically uploaded to the Oracle Content Server.
Once uploaded, it is automatically unpacked and the xWebsites metadata field data is filled with the Web site that was open in Designer when you uploaded the bundle.
