1. Delete the domain folder (meaning base_domain) under %WL_HOME%/user_projects/domains
2. Delete the domain folder (meaning base_domain) under %WL_HOME%/user_projects/apps
3. Remove any references to the domain in the %WL_HOME%/domain-registry.xml file
4. Remove any references to the domain in the file WL_HOME/common/nodemanager/nodemanager.domains
5. Remove any schema/database associated with the domain

FileStoreProvider fileStoreProvider = DirectoryLocator.m_fileStore;

DirectoryLocator has several static methods that can get paths within the filestore to places such as weblayout directory, the vault directory, the temporary directory, the provider directory, etc. It can provide you a String path to almost any directory you want.

IdcFileDescriptor is a class that can provide the pathing to files. From a FileStoreProvider, we can create an IdcFileDescriptor.

IdcFileDescriptor idcFileDescriptor = fileStoreProvider.createDescriptor(binder, null, context);

The first parameter is a DataBinder. This is where the paremeters that are needed to build the path to the file are set. The second parameter is not needed and can be set to null. The third parameter is the ExecutionContext.

The required parameters that need to be in the DataBinder are “RenditionId”, “dDocName”, “dDocType”, “dRevLabel”, “dSecurityGroup”, “dDocAccount”, “dID”, and “dExtension”. RenditionId should be set to “primaryFile” for the primary file and “web” for the alternateFile.

Fortunately, a lot of the time most of these required parameters are already in your the original DataBinder. If you are missing some parameters you should be able to make a service call to DOC_INFO to get a ResultSet which contains all of the necessary parameters. You can then dump these parameters into a new DataBinder and feed it to the createDescriptor method call.

The file descriptor that comes back will give you something like this:

idcFileDescriptor: intradoc.filestore.BasicIdcFileDescriptor{dWebExtension=xml, dID=80, RenditionId.path=primaryFile, dStatus=RELEASED, StorageClass=vault, RenditionId=primaryFile, dSecurityGroup=Public, dDocType=Web, dOriginalName=jh000035.xml, dExtension=xml, uniqueId=c:/oracle/ucm/server/vault/web/80.xml, fileNamePrefix=null, dReleaseState=Y, dDocAccount=, path=c:/oracle/ucm/server/vault/web/80.xml, dDocName=JH000035, dRevLabel=27, dRenditionId=primaryFile}

To get the path to the file, do the following:

fileStoreProvider.forceToFilesystemPath(idcFileDescriptor, null, context);
String filePath = fileStoreProvider.getFilesystemPath(idcFileDescriptor, context);

You can of course turn this file path into a Java object by using:

File myFile = new File(filePath);

One of the often used by seldom explained parts of Profiles is something called Side Effects.  You will find the Side Effects tab on the Add/Edit Activation Conditions screen and it primarily allows you to accomplish two things:

1. Add name/value pairs as IdocScript that will then get pushed to local data if the activation condition is true.
2. Add custom IdocScript to a rule that is only evaluated if the activation condition is true and this can include logic like if and else statements or loops.  Basically all IdocScript is possible here (though all of it may or may not be useful).  As such, once a rule is activated, you can include logic, use includes from a component, etc.

What specifically might one use Side Effects for?  For a simple example let’s pretend we have a profile for some scanned content.  This content is checked in as an image based PDF (no OCR, no searchable text).  Your profile should not display the full text search box in this case.  There is no full text to be searched.  You can accomplish this with a Side Effect in your profile:

<$SearchEngineName="DATABASE.METADATA"$>

Let’s take another example.  Perhaps on the check-in page you want the alternate file field to be removed.  You could go into config.cfg and add this setting, but it would be universal.  More likely you want this to happen in a specific, conditional context.  Try adding this as a Side Effect to your rule:

<$suppressAlternateFile="1"$>

Want more examples of Profiles, Rules and Side Effects? See below:

1. Using Rules & Profiles To Drive Custom Pages
2. Suppressing Alternate File
3. Thumbnail search in Content Server
4. Thumbnail search in Content Server #2
5. Hiding the Primary File field in UCM
6. Metadata field tool tips

In short, 12c looks neat and there looks to be a lot of new features but those toys are not currently part of our playground.

Trays – Before (unsorted)

Trays – After (sorted)

Top Menus – Before (unsorted)

Top Menus – After (sorted)

The first thing we do in this component is hook into the dynamichtml include for custom_finish_layout_init. We want to first call all other includes that might be using this hook by calling super.custom_finish_layout_init. Almost any time you want to add something to a dynamichtml include, the first thing you should do is call super on that include.

<@dynamichtml custom_finish_layout_init@>
  <$include super.custom_finish_layout_init$>

Next, we want to determine what version of UCM this component is installed on. There is an Idoc Script variable, ProductVersion, in 11g  that will start with 11 if the UCM instance is 11g. If it is, we call a custom include for 11g. Otherwise, we call a custom include for 10g.

<$if ProductVersion like "11*"$>
  <$include alphabetize_menus_11g$>
<$else$>
  <$include alphabetize_menus_10g$>
<$endif$>

And here is all that code put together.

<@dynamichtml custom_finish_layout_init@>
  <$include super.custom_finish_layout_init$>
  <$if isTrue(#env.EnableMenuSorting)$>
    <$if ProductVersion like "11*"$>
      <$include alphabetize_menus_11g$>
    <$else$>
      <$include alphabetize_menus_10g$>
    <$endif$>
  <$endif$>
<@end@>

10g Menus

We first create a new array. Then we get the children of the node that was passed in.

var sortData = new Array();
var children = navBuilder.getNodeById(menuID).childNodes;

Next, we want to loop through the children. If we find children of children (I suppose you would call these grandchildren), then we recursively call the sortMenu function. After we have finished dealing with any children, we build a JSON style array object containing the node object (what object type that may be) and the text label.

for (var i = 0; i < children.length; i++) {
  if (children[i].childNodes.length > 0) {
    this.sortMenu(children[i].getAttribute("id"));
  }

  sortData[sortData.length] = {
    id: children[i].getAttribute("id"),
    label: children[i].getAttribute("label")
  };
}

Next, we need to sort the array of items on the current level and we do this by defining our own JavaScript sort method.

sortData.sort (
  function (a, b) {
    if (a.label < b.label)
      return -1;
    if (a.label > b.label)
      return 1;
    return 0; [[% a == b %]]
  }
);

After our data (for the current level) is sorted, we loop over the sorted array and add/remove the items to get them in the correctly alphabetized order.

for (var i = 0; i < sortData.length; i++) {
  navBuilder.moveItemInto(menuID, sortData[i].id, false);
  if (its.safari)	{
    navBuilder.deleteItem(sortData[i].id);
  }
}

The last step is to call our menuSortingMachine.sortMenu function. Most people choose to pass in “NAVTREE” which will sort all the menus (except the menubar level items such as My Content Server, Adminsitration, Browse Content, etc.). However, you can pass in a specific “ADMINISTRATION” and that will sort only that menu and its children.

menuSortingMachine.sortMenu("NAVTREE");

And finally all the 10g  Trays and Top Menus layout sorting code together.

var menuSortingMachine = {
  sortMenu:function(menuID) {

    var sortData = new Array();

    var children = navBuilder.getNodeById(menuID).childNodes;

    for (var i = 0; i < children.length; i++) {
      if (children[i].childNodes.length > 0) {
	this.sortMenu(children[i].getAttribute("id"));
      }

      sortData[sortData.length] = {
	id: children[i].getAttribute("id"),
	label: children[i].getAttribute("label")
      };
    }

    sortData.sort (
      function (a, b) {
	if (a.label < b.label)
	  return -1;
	if (a.label > b.label)
	  return 1;
	return 0; [[% a == b %]]
      }
    );

    for (var i = 0; i < sortData.length; i++) {
      navBuilder.moveItemInto(menuID, sortData[i].id, false);
      if (its.safari)	{
	navBuilder.deleteItem(sortData[i].id);
      }
    }
  }
};
[[% menuSortingMachine.sortMenu("ADMINISTRATION"); %]]
menuSortingMachine.sortMenu("NAVTREE");

11g Menus

The navBuilder object that we used in 10g should be considered deprecated in 11g. Instead, we have new objects we can use manipulate menus such as: YAHOO.widget.MenuManager, YAHOO.widget.Menu, YAHOO.widget.MenuItem, YAHOO.widget.TreeView, YAHOO.widget.Node

oMenuBarA is a YAHOO.widget.MenuBar for menuA. This is the menu that contains items such(such as “Search” and “New Check In”).
oMenuBarB is a YAHOO.widget.MenuBar for menuB.
oTreeViewA is a YAHOO.idc.widget.TrayTreeView for the side tray (in Trays layout). Many of the methods from YAHOO.widget.TreeView can be used for the oTreeViewA object.

For more information on the new menu objects in 11g, seeKyle Hatlestad’s post Modifying Navigation Menus in UCM 11g.

11g Top Menus

The first thing we want to do is get the submenus or what we called children in 10g.

var subMenus = menu.getSubmenus();

Next. we want to loop through the submenus and recursively call the sortMenu function.

for (var i = 0; i < subMenus.length; i++) {
  menuSortingMachine.sortMenu(subMenus[i], new Boolean(true));
}

Next, we always add a check to make sure we want to sort this level and check to make sure the menu parent exists.

if (sortLevel == true || typeof menu.parent != "undefined") {}

Next, we get an array of the current level’s children menuItems and we also create a new array to hold our sorted data.

var items = menu.getItems();
var sortData = new Array();

Next, we want to loop through the menuItems and build a JSON style array object containing the MenuItem object and the text label.

for (var j = 0; j < items.length; j++) {
  sortData[j] = {
    element: items[j].element,
    label: items[j].cfg.getProperty("text")
  };
}

Like in 10g, we need to sort the array of items on the current level and we do this by defining our own JavaScript sort method.

sortData.sort (
  function (a, b) {
    if (a.label < b.label)
      return -1;
    if (a.label > b.label)
      return 1;
    return 0; [[% a == b %]]
  }
);

Similar to 10g, after our data (for the current level) is sorted, we loop over the sorted array and add the items to get them in the correctly alphabetized order.

for (var k = 0; k < sortData.length; k++) {
  menu.element.appendChild(sortData[k].element);
}

The last step is to call the menuSortingMachine.sortMenu function. We first check to make sure the variable (oMenuBarA or oMenuBarB has a value) and if so, we can use that menu to start sorting from. If we want the menubar level items for oMenuBarA or oMenuBarB to get sorted alphabetically, we can pass in true boolean value.

if (typeof oMenuBarA != "undefined" && oMenuBarA != undefined) {
  menuSortingMachine.sortMenu(oMenuBarA, new Boolean(false));
}
if (typeof oMenuBarB != "undefined" && oMenuBarB != undefined) {
  menuSortingMachine.sortMenu(oMenuBarB, new Boolean(false));
  [[% menuSortingMachine.sortMenu(YAHOO.widget.MenuManager.getMenu("MENU_B_ADMINISTRATION"), new Boolean(true)) %]];
}

And finally all the Top Menus layout sorting code together.

var menuSortingMachine = {
  sortMenu:function(menu, sortLevel) {

    var subMenus = menu.getSubmenus();

    for (var i = 0; i < subMenus.length; i++) {
      menuSortingMachine.sortMenu(subMenus[i], new Boolean(true));
    }

    if (sortLevel == true || typeof menu.parent != "undefined") {
      var items = menu.getItems();

      var sortData = new Array();

      for (var j = 0; j < items.length; j++) {
        sortData[j] = {
          element: items[j].element,
          label: items[j].cfg.getProperty("text")
        };
      }

      sortData.sort (
        function (a, b) {
          if (a.label < b.label) {
            return -1;
          }
          else if (a.label > b.label) {
            return 1;
          }
          return 0; [[% a == b %]]
        }
      );

      for (var k = 0; k < sortData.length; k++) {
        menu.element.appendChild(sortData[k].element);
      }
    }
  }
};
if (typeof oMenuBarA != "undefined" && oMenuBarA != undefined) {
  menuSortingMachine.sortMenu(oMenuBarA, new Boolean(false));
}
if (typeof oMenuBarB != "undefined" && oMenuBarB != undefined) {
  menuSortingMachine.sortMenu(oMenuBarB, new Boolean(false));
  [[% menuSortingMachine.sortMenu(YAHOO.widget.MenuManager.getMenu("MENU_B_ADMINISTRATION"), new Boolean(true)) %]];
}

11g Trays Menus

For Trays layout, we can do very similar code to that for 10g, except we have some different objects and method calls. We first create a new array. Then we get the children of the node that was passed in.

var sortData = new Array();
var children = node.children;

Similar to 10g, we want to loop through the children and recursively call the sortMenu function. Then we build a JSON style array object containing the YAHOO.widget.Node object and the text label.

for (var i = 0; i < children.length; i++) {
  if (children[i].children.length > 0) {
    this.sortMenu(children[i]);
  }

  sortData[sortData.length] = {
    node: children[i],
    label: children[i].label
  };
}

Like in 10g, we need to sort the array of items on the current level and we do this by defining our own JavaScript sort method.

sortData.sort (
  function (a, b) {
    if (a.label < b.label)
      return -1;
    if (a.label > b.label)
      return 1;
    return 0; [[% a == b %]]
  }
);

Similar to 10g, after our data (for the current level) is sorted, we loop over the sorted array and add/remove the items to get them in the correctly alphabetized order.

for (var i = 0; i < sortData.length; i++) {
  oTreeViewA.popNode(sortData[i].node);
  node.appendChild(sortData[i].node);
}

The last step is to call the menuSortingMachine.sortMenu function. We first check to make sure the variable (oTreeViewA has a value) and then we can use the getRoot() method on the oTreeViewA variable to get the root node to start sorting from.

if (typeof oTreeViewA != "undefined" && oTreeViewA != undefined) {
  menuSortingMachineTrays.sortMenu(oTreeViewA.getRoot());
}

And finally all the Trays layout sorting code together.

var menuSortingMachineTrays = {
  sortMenu:function(node) {

    var sortData = new Array();

    var children = node.children;

    for (var i = 0; i < children.length; i++) {
      if (children[i].children.length > 0) {
	this.sortMenu(children[i]);
      }

      sortData[sortData.length] = {
	node: children[i],
	label: children[i].label
      };
    }

    sortData.sort (
      function (a, b) {
	if (a.label < b.label)
	  return -1;
	if (a.label > b.label)
	  return 1;
	return 0; [[% a == b %]]
	}
      );

    for (var i = 0; i < sortData.length; i++) {
      oTreeViewA.popNode(sortData[i].node);
      node.appendChild(sortData[i].node);
    }
  }
};
if (typeof oTreeViewA != "undefined" && oTreeViewA != undefined) {
  menuSortingMachineTrays.sortMenu(oTreeViewA.getRoot());
}

Note: Any code you see between [[% %]] is an Idoc Script comment.

1. In the custom component directory, create a folder “publish”. Files that are placed within this folder will become relative to the weblayout folder.

2. In Component Wizard -> Build -> Build Settings, add a “Component Extra” entry type and link to the above path (customComponentName/publish/).

3. In Component Wizard, under the Resource Definition tab, click the “Add” button to add a new resource.

4. Check the box for “Resource – Static Table (HTML Format)”. Set the “File name” to something such as “resources/customComponent_published_static_files.htm” so that you can easily identify what this resource definition is by looking at the file name. Set the “Load Order” to “1000″. Click “Next”.

5. Set the “Table Name” to something such as “CustomComponent_PublishedStaticFiles”. Make sure the “Merge To” box is checked and set it to “PublishedStaticFiles”. Click “Finish”.

6. Edit the file that was just created with your favorite text editor. You want the second <tr> to contain something like the following:

<td>publish/resources</td>
<td>resources</td>
<td>resources:sitestudio</td>
<td>1000</td>
<td><$doPublish = 1$></td>
<td>1</td>

1. The first <td> represents the source folder to publish
2. The second represents the path, relative to weblayout, to place the files
3. The third represents the “class” that controls the publishing and processing of the content
4. The fourth is the loadOrder and should be set to 1000 (which is the highest available)
5. The fifth is doPublish.  This is a string of iDocScript that can be used to determine whether or not this set of files should be published.  You can do fancy things like construct time of day, week or month to conduct publishing.
6. The sixth (canDeleteDir) should be set to 1.

That is it! Build your component and try it out.

Note: If you have problems with the files publishing (for example they should publish on start-up) you can manually invoke this action by invoking Administration -> Admin Actions – > Weblayout Publishing -> Publish static, string and dynamic files.  This will likely take a few minutes to complete.

<WLS path>/user_projects/domains/<UCM domain>/cs/config/config.cfg

Add the following entry:

UseSearchCache=true

Save and restart your content server.

Windows

1. Open the domain environment cmd file:

<middleware home>\user_projects\domains\base_domain\bin\setDomainEnv.cmd

2. Locate the following remark, inside the cmd file: (‘Search’ -> “@REM IF USER_MEM_ARGS”)

@REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values

3. Directly after this remark, add the following line:

set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m

4. The portion of the file you have edited looks like this:

@REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values

set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m

if NOT “%USER_MEM_ARGS%”==”" (

set MEM_ARGS=%USER_MEM_ARGS

)

UNIX/Linux

1. Open the domain environment sh file:

<middleware home>\user_projects\domains\base_domain\bin\setDomainEnv.sh

2. Locate the following remark, inside the sh file: (‘Search’ -> “#REM IF USER_MEM_ARGS”)

#REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values

3. Directly after this remark, add the following line:

USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m

4. The portion of the file you have edited looks like this:

#REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values

USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m

if NOT “%USER_MEM_ARGS%”==”" (

MEM_ARGS=%USER_MEM_ARGS

)

References

Note that the basic difference between Windows and UNIX/Linux regarding this issue is the use of the “set” command for the Windows environment.

Final Thoughts

This is certainly not the only way to accomplish this task, and it does affect all managed servers in the domain.  However, if you’re running a dev box with plenty of memory it is the simplest and gives you the best “umph” when running your various instances with the least amount of work.

1. Using JDeveloper (for 11g SSXA) or Site Studio Designer, open the element definition for the WYSIWYG in question.

2. Check the box for “Do Not Enclose Text in Editor”.

The 10gR4 Site Studio Designer Guide has this to say about the topic:

Do Not Enclose Text in Editor: Used to define how carriage returns are handled in HTML. If text is enclosed, each time the contributor enters a return, a paragraph is created. If not enclosed, a line break is inserted for each return.