Where the posted threads are stored

Hi All,
Where the posted threads are stored. In which repository i is storing.
Regards
Krishnamurthy K

Hi,
You can read the documentation about [Content Management Configuration|http://help.sap.com/saphelp_nw70/helpdata/EN/69/d96b7aa84611d5993600508b6b8b11/frameset.htm] , where you can find a lot of information about [Repository Managers |http://help.sap.com/saphelp_nw70/helpdata/EN/69/d96b7da84611d5993600508b6b8b11/frameset.htm] .
Repositories are used for storing and/or retrieving content and metadata.
The KM standard configuration uses several internal repositories that are controlled by CM. They are used for storing and staging various content and metadata and for navigating in this data. These repositories are preconfigured and preactivated in the KM standard configuration. You do not normally need to modify their configuration.
In addition to the aforementioned internal repositories, you can integrate additional external repositories into CM, such as a WebDAV or file system repository. You can establish a connection to these repositories by configuring appropriate repository managers.
Regards,
Lubi
*Hope it will be helpful for you.

Similar Messages

Changing where the sent messages are stored

Hi, I was wondering is there any way you can change where the sent messages are stored. I have switched from a few programs.. and there is a 'sent' folder and ' sent messages' folder on my folder list in addition to that of what mail is putting them in. I just want one folder.

Sounds like you are accessing an IMAP type account.
If so, is this the only email account and account type you are accessing with the Mail.app?

Anybody know where the default templates are stored?

I'd like to access the location where the default templates are stored. I've checked in: "Macintosh HD/Library/Application Support/Logic" but did not find anything.
I see that user templates are in: "Macintosh HD/Users/PROFILE/Library/Application Support/Logic/Project Templates"
Thanks in advance!
Rydah

alienimplant wrote:
The assigned solution to this problem is false. The answer is that they are stored here:
/Users/[username]/Music/Audio Music Apps/Project Templates
That is not correct.
User Project templates are stored in the location you stated but the Default Project templates, which is what the OP asked about, are stored within the app as Blueberry stated....
Note the path I highlighted......

Where the Forum informations are stored?

Hi all,
i need to know, where the forum contents are stored in the KM?
regards,
Kathiresan R

Hi,
Did you press the Advanced mode when you are under repository manager?
If the forums repository is not present, then you did not install Forums Application.
Check this:
http://help.sap.com/saphelp_nw70/helpdata/EN/46/9ca6594e903ef4e10000000a1553f7/frameset.htm
Regards,
Praveen Gudapati

Exact table where the repository objects are stored

Hi,
In which table the repository objects(Program,FM,Data Element,...) are stored exactly.
I checked in TADIR table, but it's a directory for the repository objects.
Also checked TRDIR.
Say, If I delete a transport request which contains a report thru a 'Z_delete_request' prgm, I can still see the report in SE38.Ofcourse I have deleted in TADIR also.
But presents in repository.
Kindly suggest the exact table name.
Regards,
Siva

Hi,
Use seach option in SDN.
[System table in abap where all the programs/FMs created are stored !]
Regards
Sandipan
Edited by: Sandipan Ghosh on Jan 6, 2009 10:51 AM

Where the customized pages are stored (generated through PageService)

I am using ADF's PageService to create some customized pages inside the webCenter framework, after successfully creating a couple of pages, I failed to locate the generated files. Does anyone know where I can find those framework-generated files? Any help will be appreciated!

If you import webcenter spaces ear using weblogic em using the Application export feature. A WebCenter Spaces application is exported into a single export archive (.ear file). The EAR file contains a metadata archive (transport.mar file). This mar file contains all the custom pages in directory(oracle/webcenter/page/scopedMD/<webcenter id>/) . I am trying to find out the location of the files in server where it is stored.

Where the loaded files are stored?

I loaded excel file with data in my FDM app. After the file loaded It could be seen in my HFM app (choosing "Restore Source Document"). Question: where this loaded excel file is stored?

What installation question?
I think there is still some confusion over what can go where.
RoboHelp as a program needs to be installed on the user's PC.
Projects can be stored on a network drive but note that it will be a bit slower and may not be acceptable if your network is slow. Generally it works OK if you accept some processes will be a bit slower. Although more than one user with Rh on their own PC can access the network project, working this way is only intended to allow one person at a time to access the project. If you want multiple authors on the project simultaneously, you need source control.
The outputs you generate from a project should be generated to the same drive as the project, wherever that may be. WebHelp can also be published (it different process) to a web server.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

What is the path and filename where the profile paths are stored?

I currently am storing my profiles on a network drive. Due to some changes coming up in my home network I need to relocate them to a different drive and drive letter. I know there is a file in Firefox that has the locations of the profiles in it. I need to know the fully qualified path to find this file. The operating system is Windows XP and I am currently running the latest Firefox 3.6 on it.

Help > Troubleshooting Information > Profile Directory: Open Containing Folder
See also:
* http://kb.mozillazine.org/Profile_folder_-_Firefox
* http://kb.mozillazine.org/Moving_your_profile_folder

Tables where the XI Data is stored

Dear all,
Can you let me know all the tables in XI in which the data is stored.
Like where the asyncronous messages are stored(which table and what is the abap program name which gets executed to store the message id's etc in the table).
Pl list out all the tables,programs related to XI.
Also pls let me know where IDOC,Proxy,RFC related tables programs.
my mailid is srinivas5780@gmailcom

Hi,
Please go through the below weblog:
/people/gourav.khare2/blog/2007/12/12/interesting-abap-tables-in-xi-150-part-i
Look at the below thread for SXMB_MONI tables and Function module:
In Which Database Table the Messages are Stored in XI
Message Monitoring --> corresponding tables?
For IDOC:
tables are EDIDC control record table and EDIDD-data record table.
Thnx
Chirag

Where the Report info is stored.

Can anyone tell me where the reports logs are stored. I am asking for those which are displayed in showjobs comand.
I am not talking about those which are stored in log folder.

Hello,
The information displayed by the showjobs command is stored in memory and in the "persist file"
http://download-uk.oracle.com/docs/cd/B14099_17/bi.1012/b14048/pbr_conf.htm#i1007034
Regards

Where can I find the file where the static mapping allocations of the DHCP server are stored?

In our company we are using DHCP to assign static ip addresses to our clients.
Now we are forced to change the ip address range. To prevent changing each allocation
of mac-address to ip-address manually with the admin tool i would like to change the allocation
in the file where the allocations are saved. The reason ist that i just have to use copy & paste for all
the allocations.
So how is the file named and where can I find the file where
the static mapping allocations of the DHCP server are stored? Is it just an ASCII file?
Must i note anything when i change the file manually?

From man bootpd:
BOOTP/DHCP STATIC BINDINGS
     Static IP address to ethernet address bindings are stored in the /etc/bootptab file and in Open Directory. Bindings specified in the /etc/bootptab file take precedence over those in Open Directory.
     See bootptab(5) for more information about the /etc/bootptab file.
     For Open Directory, bootpd looks at the /Computers records for the following properties:
/etc/bootptab is a standard text file, while the records in Open Directory can be manipulated either through the command line, or via Workgroup Manager.

I'm trying to change the location where my apps etc are stored

I'm trying to change the location where my apps etc are stored, when I close iTunes and reopen, it is automatically reset to the default location

Take a look at his link, http://support.apple.com/kb/HT1391

Backed up Lightroom 2 to a 'backup plus'. Will be installing Lightroom 5 to a new Win 7 computer and want to move only the photos to a dedicated 1 tb drive in the machine. Anyone know Where my actual photos are stored on 'backup plus'? Thank you

Backed up Lightroom 2 to a Seagate 'backup plus'. Will be installing Lightroom 5 to a new Win 7 computer and want to move only the photos to a dedicated 1 tb drive in the machine. Anyone know where my actual photos are stored on 'backup plus'? Thank you

Thank you for your reply. I have been backing up my entire computer and when I follow anything having to do with Lightroom I am not finding actual photos. I hope to find the photos that have been backed up along with updates to them that my wife has been performing during her edits. Found Lightroom 2 catalog Previews/Lrdata. Could that be it?

Where the feedback content is stored

hi,
if a user is giving feedback for a document. where the content of the feedback will be stored in KM.
can anyone give the path for that.
all helps will be appriciated
Regards,
Shanthakumar.

There is no place in Portal to see the FeedBack content .We provide a folder path for the Discussion/Discussion Group/Km Discussion iVIew in iVIew property "path to root folder " .This is for reference .Suppose we can provide "/documents/discussions/New Discussion" as the folder path where the posts and feedback are supposed to get stored .However the content is actually in stored in the database and not seen in Portal . As correctly provided in the previous reply,study the article to see where it is actually stored . I hope this suffices your answer .
Edited by: Arijit Bhattacharya on Apr 30, 2008 10:55 AM

Where the task payload is stored in the dehydration store

Hi All,
I wanted to get the taskPayload from the BPEL dehydration store. I have gone thru the WFTASK table but I didn't see any column which conains the taskpaylod.
I need this payload to do the following..
- Get the taskPayload
- Modify it so that I can get modifications in the BPEL process when I submitted the task back to BPEL.
Can the above be done from the bpel dehydration store? If yes please help me in finding the exact table for this task payload.
If not guide me how can I access and modify the task payload.
Thank you.

Payloads are generally stored as BLOBS. Here is a definition of all the tables. You can make the payload editable withing the human task if required, so you don't need to go to the DB.
Main tables used by the BPEL engine
cube_instance – stores instance metadata, eg. instance creation date, current state, title, process identifier
cube_scope – stores the scope data for an instance … all the variables declared in the bpel flow are stored here, as well as some internal objects to help route logic throughout the flow.
work_item – stores activities created by an instance … all BPEL activities in a flow will have a work_item created for it. This work item row contains meta data for the activity … current state, label, expiration date (used by wait activities) … when the engine needs to be restarted and instances recovered, pending flows are resumed by inspecting their unfinished work items.
document - stores large XML variables. If a variable gets to be larger than a specific size (configurable via the largeDocumentThreshold property via the domain configuration page) then the variable is stored in this table to alleviate loading/saving time from the cube_scope table.
audit_trail - stores the audit trail for instances. The audit trail viewed from the console is modelled from an XML document. As the instance is worked on, each activity writes out events to the audit trail as XML which is compressed and stored in a raw column. Querying the audit trail via the API/console will join the raw columns together and uncompress the contents into a single XML document.
audit_details - audit details can be logged via the api … by default activities such as assign log the variables as audit details (this behavior can be set via the auditLevel property on the domain configuration page). Details are separated from the audit trail because they tend to be very large in size … if the user wishes to view a detail they click a link from the audit trail page and load the detail separately. There is a threshold value for details too … if the size of a detail is larger than a specific value (see auditDetailThreshold) then it is place in this table, otherwise it is merged into the audit trail row.
dlv_message – callback messages are stored here. All non-invocation messages are saved here upon receipt. The delivery layer will then attempt to correlate the message with the receiving instance. This table only stores the metadata for a message. (eg. current state, process identifier, receive date).
dlv_message_bin – stores the payload of a callback message. The metadata of a callback message is kept in the dlv_message table, this table only stores the payload as a blob. This separation allows the metadata to change frequently without being impacted by the size of the payload (which is stored here and never modified).
dlv_subscription – stores delivery subscriptions for an instance. Whenever an instance expects a message from a partner (eg. receive, onMessage) a subscription is written out for that specific receive activity. Once a delivery message is received the delivery layer attempts to correlate the message with the intended subscription.
invoke_message – stores invocation messages, messages which will result in the creation of a instance. This table only stores the metadata for an invocation message (eg. current state, process identifier, receive date).
invoke_message_bin – stores the payload of an invocation message. Serves the same purpose the dlv_message_bin table does for dlv_message.
task – stores tasks created for an instance. The TaskManager process keeps its current state in this table. Upon calling invoking the TaskManager process, a task object is created, with a title, assignee, status, expiration date, etc… When updates are made to the TaskManager instance via the console the underlying task object in the db is changed.
schema_md – (just added via patch delivered to Veerle) contains metadata about columns defined in the orabpel schema. Use case driving this feature was how to change the size of a custom_key column for a cube_instance row? Changing the db schema was simple but the engine code assumed a certain length and truncated values to match that length to avoid a db error being thrown. Now, column lengths are defined in this table instead of being specified in the code. To change a column length, change the column definition in the table, then change the value specified in this table, then restart the server.
Column-by-column description:
table ci_id_range
- next_range (integer) – instance ids in the system are allocated on a block basis … once all the ids from a block have been allocated, another block is fetched, next_range specifies the start of the next block.
table cube_instance
- cikey (integer) – primary key … foreign key for other tables
- domain_ref (smallint) – domain identifier is encoded as a integer to save space, can be resolved by joining with domain.domain_ref.
- process_id (varchar) – process id
- revision_tag (varchar) – revision tag
- creation_date (date)
- creator (varchar) – user who created instance … currently not used
- modify_date (date) – date instance was last modified
- modifier (varchar) – user who last modified instance … currently not used
- state (integer) – current state of instance, see com.oracle.bpel.client.IInstanceConstants for values
- priority (integer) – current instance priority (user specified, has no impact on engine)
- title (varchar) – current instance title (user specified, no engine impact)
- status (varchar) – current status (user specified)
- stage (varchar) – current stage (user specified)
- conversation_id (varchar) – extra identifier associated with instance, eg. if passed in via WS-Addressing or user specified custom key.
- root_id (varchar) – the conversation id of the instance at the top of the invocation tree. Suppose A -> B -> C, root( B ) = A, root( C ) = A, parent( B ) = A, parent( C ) = B. This instance, instance at the top of the tree will not have this set.
- parent_id (varchar) – the conversation id of the parent instance that created this instance, instance at the top of the tree will not have this set.
- scope_revision (integer) – internal checksum of scope bytes … used to keep caches in sync
- scope_csize (integer) – compressed size of instance scope in bytes
- scope_usize (integer) – uncompressed size of instance scope in bytes
- process_guid (varchar) – unique identifier for the process this instance belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
- process_type (integer) – internal
- metadata (varchar) – user specified
table cube_scope
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- modify_date (date) – date scope last modified
- scope_bin (blob) – scope bytes
table work_item
- cikey (integer) – foreign key
- node_id (varchar) – part of work item composite key, identifier for bpel activity that this work item created for
- scope_id (varchar) – part of work item composite key, identifier for internal scope that this work item created for (note this is not the scope declared in bpel, the engine has an internal scope tree that it creates for each instance, bpel scopes will map to an internal scope but there will be other internal scopes that have no mapping to the bpel definition).
- count_id (integer) – part of work item composite key, used to distinguish between work items created from same activity in the same scope.
- domain_ref (integer) – domain identifier
- creation_date (date)
- creator (varchar) – user who created work item … currently not used
- modify_date (date) – date work item was last modified
- modifier (varchar) – user who last modified work item … currently not used
- state (integer) – current state of work item, see com.oracle.bpel.client.IActivityConstants for values
- transition (integer) – internal use, used by engine for routing logic
- exception (integer) – no longer used
- exp_date (date) – expiration date for this work item; wait, onAlarm activities are implemented as expiration timers.
- exp_flag (integer) – set if a work item has been called back by the expiration agent (ie. expired).
- priority (integer) – priority of work item, user specified, no engine impact
- label (varchar) – current label (user specified, no engine impact)
- custom_id (varchar) – custom identifier (user specified, no engine impact)
- comments (varchar) – comment field (user specified, no engine impact)
- reference_id (varchar) -
- idempotent_flag (integer) – internal use
- process_guid (varchar) – unique identifier for the process this work item belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
table document
- dockey (varchar) – primary key for document
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- classname (varchar) – no longer used
- bin_csize (integer) – compressed size of document in bytes
- bin_usize (integer) – uncompressed size of document in bytes
- bin (blob) – document bytes
- modify_date (date) – date document was last modified
table audit_trail
- cikey (integer) – foreign key
- domain_ref – domain identifier
- count_id (integer) – many audit trail entries may be made for each instance, this column is incremented for each entry per instance.
- block (integer) – when the instance is dehydrated, the batched audit trail entries up to that point are written out … this block ties together all rows written out at one time.
- block_csize (integer) – compressed size of block in bytes
- block_usize (integer) – uncompressed size of block in bytes
- log (raw) – block bytes
table audit_details
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- detail_id (integer) – part of composite key, means of identifying particular detail from the audit trail
- bin_csize (integer) – compressed size of detail in bytes
- bin_usize (integer) – uncompressed size of detail in bytes
- bin (blob) – detail bytes
table dlv_message
- conv_id (varchar) – conversation id (correlation id) for the message…this value is used to correlate the message to the subscription.
- conv_type (integer) – internal use
- message_guid (varchar) – unique identifier for the message…each message received by the engine is tagged with a message guid.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – identifier for process revision
- operation_name (varchar) – operation name for callback port.
- receive_date (date) – date message was received by engine
- state (integer) – current state of message … see com.oracle.bpel.client.IDeliveryConstants for values
- res_process_guid (varchar) – after the matching subscription is found, the process guid for the subscription is written out here. – res_subscriber (varchar) – identifier for matching subscription once found.
table dlv_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of delivery message payload in bytes
- bin_usize (integer) – uncompressed size of delivery message payload in bytes
- bin (blob) – delivery message payload
table dlv_subscription
- conv_id (varchar) – conversation id for subscription, used to help correlate received delivery messages.
- conv_type (integer) – internal use
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- process_id (varchar) – process identifier for instance
- revision_tag (varchar) – revision tag for process
- process_guid (varchar) – guid for process this subscription belongs to
- operation_name (varchar) – operation name for subscription (receive, onMessage operation name).
- subscriber_id (varchar) – the work item composite key that this subscription is positioned at (ie. the key for the receive, onMessage work item).
- service_name (varchar) – internal use
- subscription_date (date) – date subscription was created
- state (integer) – current state of subscription … see com.oracle.bpel.client.IDeliveryConstants for values
- properties (varchar) – additional property settings for subscription
table invoke_message
- conv_id (varchar) – conversation id for message, passed into system so callbacks can correlate properly.
- message_guid (varchar) – unique identifier for message, generated when invocation message is received by engine.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – revision tag for process
- operation_name (varchar) – operation name for receive activity
- receive_date (date) – date invocation message was received by engine
- state – current state of invocation message, see com.oracle.bpel.client.IDeliveryConstants for values
- priority (integer) – priority for invocation message, this value will be used by the engine dispatching layer to rank messages according to importance … lower values mean higher priority … messages with higher priority are dispatched to threads faster than messages with lower values.
- properties (varchar) – additional property settings for message
table invoke_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of invocation message payload in bytes
- bin_usize (integer) – uncompressed size of invocation message payload in bytes
- bin (blob) – invocation message bytes
table task
- domain_ref (integer) – domain identifier
- conversation_id (varchar) – conversation id for task instance … allows task instance to callback to client
- title (varchar) – current title for task, user specified
- creation_date (date) – date task was created
- creator (varchar) – user who created task
- modify_date (date) – date task was last modified
- modifier (varchar) – user who last modified task
- assignee (varchar) – current assignee of task, user specified, no engine impact
- status (varchar) – current status, user specified, no engine impact
- expired (integer) – flag is set if task has expired
- exp_date (date) – expiration date for task, expiration actually takes place on work item in TaskManaged instance, upon expiration task row is updated
- priority (integer) – current task priority, user specified, no engine impact
- template (varchar) – not used
- custom_key (varchar) – user specified custom key
- conclusion (varchar) – user specified conclusion, no engine impact

Where the posted threads are stored

Similar Messages

Maybe you are looking for