i want to create my own customized placeholders in publication.i browsed through forum,found out that it can be done using sdk and there is one hidden placedholders.
I would like to understand these placeholders should be getting populated from any properties,parameter files stored at installation package.
Am i sounding logical?..then we can edit that properties file to have our own placeholders.?
BOnd007 
(BOB member since 2009-08-11)
<>
Server Intelligence components
A BusinessObjects Enterprise deployment consists of the following components:
*
Enterprise nodes.
*
Installs.
*
Service containers.
*
Services.
*
Servers.
Enteprise nodes
An enterprise node is the context of a BusinessObjects Enteprise installation. It contains:
*
The physical location of the installed binaries (host machine and hard drive).
*
The base installation directory.
*
The operating system user account under which binaries are run.
*
Placeholders for values used by the Server Intelligence framework, including the absolute paths to the JRE bin directory and the directory where temporary audit log files are stored.
*
The Server Intelligence Agent process, which monitors the status of all the servers in the deployment.
The simplest type of deployment, where all the BusinessObjects Enteprise components are installed on a single machine, has only one enterprise node. A complex deployment has multiple enterprise nodes, one for each physical machine.
The com.businessobjects.sdk.plugin.desktop.enterprisenode.IEnterpriseNode interface is used to represent enterprise nodes.
**Installs
An install is a set of BusinessObjects Enteprise binaries. It defines placeholders for the platform-specific relative paths and filenames of BusinessObjects Enterprise binaries.
Note that an install does not represent an actual installation. It is similar to a manifest containing a list of binaries and their relative paths. The Server Intelligence framework uses this information in conjunction with the information in an enterprise node to determine the absolute paths to the actual binaries on a physical machine.
The simplest type of BusinessObjects Enterprise deployment has only one enterprise node, which would have one install. A complex deployment could have many enterprise nodes and one install, in which case each node would have the same binaries installed. Alternatively, a complex deployment could have multiple installs, in which case different nodes could have different sets of binaries installed.
The com.businessobjects.sdk.plugin.desktop.install.IInstall interface is used to represent BusinessObjects Enterprise installs.
**Service containers
A service container is an executable binary file that can be configured to run one or more services. A service container can be used by multiple servers. A server is associated with only one service container.
The com.businessobjects.sdk.plugin.desktop.servicecontainer.IServiceContainer interface is used to represent BusinessObjects Enterprise executables.
Note: The com.crystaldecisions.sdk.occa.infostore.CeSecurityCUID.ServerIntelligence interface defines constants that can be used to retrieve IServiceContainer objects from the repository.
**Services
A service is a binary file that is loaded by a service container to provide some application functionality, such as report caching, auditing, or report scheduling. A server can host one or more services. The service container determines which services can be hosted by the server.
The com.businessobjects.sdk.plugin.desktop.service.IService interface is used to represent BusinessObjects Enterprise services.
Note: The com.crystaldecisions.sdk.occa.infostore.CeSecurityCUID.ServerIntelligence interface defines constants that can be used to retrieve IService objects from the repository.
**Servers
A server is a running instance of a service container. It contains the configuration information used to launch the associated service container and host one or more services.
The com.crystaldecisions.sdk.plugin.desktop.server.IServer interface is used to represent BusinessObjects Enterprise servers. Each server contains:
*
An com.businessobjects.sdk.plugin.desktop.common.IConfiguredContainer object, which can be retrieved by calling the getConfiguredContainer method of the IServer interface. The IConfiguredContainer object contains the settings that are used to configure the service container executable when the server is started.
*
An com.businessobjects.sdk.plugin.desktop.common.IConfiguredServices collection, which can be retrieved by calling the getConfiguredServices method of the IServer interface. IConfiguredServices contains one com.businessobjects.sdk.plugin.desktop.common.IConfiguredService object for each service that is hosted by the server. Each IConfiguredService object contains the configuration information that is passed to the service when the server is started.
BOnd007 (BOB member since 2009-08-11)
my perception is that whatever present in this CMS repository in following table,would be accessible in placeholders.
CI_SYSTEMOBJECTS
Contains objects that are often used to build the admin desktop and internal system objects, such as servers, connections, users, and user groups.
BOnd007 (BOB member since 2009-08-11)