Steps:

1. Log in to Siebel Tools and create a new custom business service.e.g: MyBS.
2. Expand to Business Service Method and add a record:
   Name = MyQuery
3. Expand to Business Service Method Arg and add 3 records:

• • SiebelMessage, Type = Input, Data Type= Integration Object, Storage Type=Hierarchy , Integration Object = "EAI Account" (or your preferred IO)
  • MyIO, Type = Output, Data Type= Integration Object, Storage Type = HIERARCHY, Integration Object = "EAI Account" (or your preferred IO)
  • Error Message, Type = Output, Data Type = String, Storage Type = Property

Publishing Inbound Web Services
 

4. Right click the business service name and select Edit Server Scripts.
5. Choose eScript as the programming language.( could be Siebel VB too but the code sample below is eScript). Add the code below, review and compile to the server SRF.
6. Publish the business service as an inbound web service the usual way.
The steps are descriped in Bookshelf: Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Invoking Siebel Web Services Using an External System >
Notice during the publishing process, the BS will NOT be listed. You have to add a new record and type in the BS name as documented in bookshelf.
7. Test. You may want to use a test utility such as SOAPUI or any other tool.
You may as well use use a siebel dedicated client and sample database as seen in How To Test Siebel Inbound Web Services Using a Siebel Client (Doc ID 473838.1).
If testing with a Siebel dedicated client, the following document may be helpful too: How To Create Integration Object Instances Programmatically (Doc ID 556846.1)

The DumpPropSet(Outputs) below helps us understand both how to pass data as output as well as data for input scenarios.

The important here is the structure should have 4 levels :

1) Inputs (or Outputs) property. It does not have any type set.
2) Business service method argument level property. This is a child of (1) above and has type = business service method argument name (in the example below "MyIO")
3) Integration Object representation. This is a child of (2) above and has type =ListOf<IO_NAME>
(in the example below ListOfEAI Account)
4) root integration component level. Should have type = root IC name.
In this case type = Account

In Siebel, Integration Component Fields with Field Type property as "System" are not exported even if these fields are active during a query operation.

This is the expected behavior. This setting prevents the EAI Siebel Adapter from treating the field as a data field, which means for the Query and QueryPage method the EAI Siebel Adapter do not write to the fields.

If such fields are required in an exported message, you can change the Integration Component Field Type property value to 'Data' from 'System'.

Compile the Repository after making the above changes to Integration Object.

Within a workflow process, you can store a property set in a process property of type Hierarchy. To pass the content of a process property to or from a custom business service, however, the Type of the child property set stored in the process property must match the name of the input or output argument of the business service.

The following two examples demonstrate this principle.

Example 1: Getting a Property Set from a Business Service

This example shows how to set up a workflow process to invoke a custom business service, and retrieve a process property that is in a hierarchal property set.

1. In Siebel Tools, create a business service, MyBS, defined with the following method and arguments:
   
   Method Name: Method1
   Arguments:

   Name	Data type	Type	Display name	Storage Type	Optional
   HierarchyArg1	Hierarchy	Input / Output	Hierarchy Argument 1	Hierarchy	True

   The name of the argument, for example, HierarchyArg1, must match the Type of the child property set in the business service script.

   Add the following Server script (eScript):

   function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
    if (MethodName == "Method1") {
        var outPropset = TheApplication().NewPropertySet() ;
        outPropset.SetType("HierarchyArg1") ;
        outPropset.SetProperty("PropName1", "Hello") ;
        outPropset.SetProperty("PropName2", "Goodbye") ;
        Outputs.AddChild(outPropset) ;
        outPropset = null;
        return (CancelOperation);
    }
    else return (ContinueOperation);
}

   
   Create a workflow process, myWF, with a process property defined as follows: 
   
   Name: myHierarchy
   Data Type: Hierarchy

2. You can name this process property with any name you choose. This process property name becomes the Type of your output property set.

3. Add a business service step to the workflow process defined as follows to invoke the business service you created in steps 1 and 2: 
   
   Business Service: MyBS
   Method: Method1
    
4. For the output argument of the business service step, add a record as follows: 
   
   Property Name: myHierarchy
   Type: Output Argument
   Output Argument: Hierarchy Argument 1

   The execution of this step puts the property set built in the myBS business service into the myHierarchy process property. Please refer to the Note at the end of this FAQ for additional information about this step.

5. Run the workflow process in the workflow process simulator. At the end of the business service, the myHierarchy process property with the following structure is available:

   Type	Value	Child Type
   myHierarchy		HierachyArg1

   Type	Value	Property Key	Property Value
   HierachyArg1		PropName1	Hello
   		PropName2	Goodbye

Example 2: Passing the Process Property to a Business Service

This second example builds on the workflow and business service developed in Example 1 and assumes that you have a workflow process with a hierarchy process property that has been initialized by another step. This example shows how to pass a property set from a workflow process to a business service. For this example, the Type of the property set must be stored within this process property.

In Example 1, the step calling the MyBS business service returned a property set with a Type of HierarchyArg1 into the myHierarchy process property. In this example, this process property is passed to another business service called MyBS2 using the Method2 method.

1. Create a new business service named MyBS2 and define it with the following method and argument (created in Siebel Tools):  
   
   Method Name: Method2
   Arguments:

   Name	Data type	Type	Display name	Storage Type	Optional
   HierarchyArg1	Hierarchy	Input / Output	Hierarchy Argument 1	Hierarchy	True

2. Add the following Server script (eScript) to the business service:

   function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
    if (MethodName == "Method2") {
        var childPropset = TheApplication().NewPropertySet();
        childPropset = Inputs.GetChild(0);
        var a = childPropset.GetProperty("PropName1");
        var b = childPropset.GetProperty("PropName2");
        var outPropset = TheApplication().NewPropertySet();
        outPropset.SetType("HierarchyArg1");
        outPropset.SetProperty("PropName3", a+b);
        Outputs.AddChild(outPropset);
        outPropset = null;
        childPropset = null;
        return (CancelOperation);
    }
    else return (ContinueOperation);
}

   
   Modify the workflow process from Example 1 to add another business service step and a new process property of type hierarchy called myHierarchy2.

3. The business service step invokes the MyBS2 business service you created above. This step should be added after the step that invokes the MyBS business service. In that step, pass it the process property as indicated below:
   
   Business Service: MyBS2
   Method: Method2

4. Add a record into Input Arguments applet as follows: 
   
   Input Argument: Hierarchy Argument 1
   Type: Process Property
   Property Name: myHierarchy

5. For the output argument of the business service step, add a record as follows: 
   
   Property Name: myHierarchy2
   Type: Output Argument
   Output Argument: Hierarchy Argument 1
   
   The execution of the MyBS2 business service step passes the content of the myHierarchy process property (a hierarchical process property) into a child property set having a Type of HierarchyArg1. The HierarchyArg1 property set is received by the Service_PreInvokeMethod function of the MyBS2 business service.
    
6. Run the workflow process in the workflow process simulator. At the end of the business service, the myHierarchy2 process property with the following structure is available:
   
   

   Type	Value	Child Type
   myHierarchy2		HierachyArg1

   
   

   Type	Value	Property Key	Property Value
   HierachyArg1		PropName3	HelloGoodbye

 Note.  In above steps (Example 1, step 5 and Example 2, step 4) the Output Argument and Input Argument columns show the display name of the argument, not its name. This is the reason why the Type of the property set is HierarchyArg1 and not Hierarchy Argument 1.

Siebel 7.7.2.10 and higher supports attachments encoded as base-64.
All you need is :

We do not have detailed and exact step by step procedure as this is mostly a design decision and as such is beyond scope of support.
I am glad to share ideas though and suggest the following exercise to gain insight:

1) Use the thin client.Query for an account or service request.
Add an attachment to it in the UI.
Ensure you can attach and download a file from the UI.if not, fix it first.

2) Use an integration object with the correct structure for attachments.
Some siebel versions had issues with the siebel tools wizard when creating an IO with attachments so I suggest you try a standard one and once it works you can use it as a reference for other objects.
e.g: activate and compile Sample Account.
or use Service Request IO
(once this works you can just extend your own IO to have an attachment IC with the same fields)

3) Log in to thin client.
Site map -> administration - Business service -> Simulator.
Simulate EAI Siebel Adapter, method Query and provide the input arguments:
OutputIntObjectName = Sample Account (or Service Request, or other of your choice).
PrimaryRowId = a valid row id for accounts, srs or the object you chose. This object must have an attachment.
 
4) once #3 works. scroll down to the lowermost applet. Click save to file.
This will save the output to file and now you have a sample message to play with and know what the attachment looks like in the XML. (SIEBEL MESSAGE at this point. not a SOAP.)

5) since the goal is to use webservices... once #3 is good, create a custom BS or a workflow that calls EAI Siebel Adapter with the specific IO you tested and publish it as a webservice.

6)To thest the web service you may want to download http://www.soapui.org. This is a free 3rd party tool. We do not offer support for it and have limited experience with it. You may find it usefull for simple tests though.
Import the siebel inbound web service WSDL to it.
Call the method query.
Give it a valid row id for a record that has an attachment and there you are !!! you have a sample SOAP message this time (item 3 gave you a sample Siebel message as opposed to SOAP)
The attachment should be in base-64

Edit the response message to call a different method e.g: insert and make sure the message has a new parent data (like a new account or a new SR).
Send it through SOAP UI and it should create a new record with the same attachment.

Now you know how to query and also how to insert.
Your last point of attention is :
 

Once you can get this simple example to work it should be feasible extend the idea to your existing web service.
Basically you just have to create an extra IC for attachments using a standard attachment IC as an example.

This section explains how to manipulate a property set in a workflow without custom script. The mechanisms used here are:

• The Workflow Utilities business service, echo method.

• Workflow process aliases

• The dot notation.

The following techniques allow reading and setting property set content. It is limited to hierarchies that do not have many children of the same type. For example, if a hierarchy has an Account and several Activities, retrieving the value of an Activity attribute is only possible for the first activity of the hierarchy.

If the requirement is to navigate the property set and loop through children, scripted is needed.

• Aliases

Workflow Processes can have Process Properties of type "Alias". This kind of Process Property works as a pointer to a specific attribute inside a Property Set. Aliases can be used to get an attribute from or set an existing attribute in a Property Set.

Syntax description:
ProcessProperty/[PropertySeta]/[PropertySetb]/.../[PropertySetn]/@attribute

• ProcessProperty (mandatory): an existing Workflow Process Property of type Hierarchy.

• PropertySeta to PropertySetn (optional): any sub-property set used to reach the sub-levels of the hierarchy.

• @attribute (mandatory): the attribute being referenced in the alias.

"/" is the mandatory separator between the ProcessProperty, sub-propertysets and the attribute
Example:
psSiebelMessage/ListOfOrder Interface/Orders/@Account Id
Below Table describes the behavior of different Aliases

Alias	Get	Set	Comments
psSiebelMessage/ListOfOrder Interface/Orders/@Id	1-110CJ	1-110CJ
psSiebelMessage/ListOfOrder Interface/@Id	Empty value	Nothing happens	There is no attribute called "Id" inside the psSiebelMessage/ListOfOrder Interface.
psSiebelMessage/ListOfOrder Interface//@Id	Error	Error	There is a syntax error in the Alias "//@Id"

• Dot Notation - Read Attributes

As an alternative for Aliases, the dot notation can also be used to get attributes from a PropertySet. We commonly use Echo Steps with dot notation.
The table below shows the behavior of reading values from PropertySets using dot notation and an Echo step. Assuming the Input argument is called with the Process Property psSiebelMessage.

Output Argument	Get	Comments
psSiebelMessage.ListOfOrder Interface.Orders.Account Id	1-110CJ
psSiebelMessage.ListOfOrder Interface.Account Id	Error	There is no attribute called "Account Id" inside the PS

• Dot Notation - Set Attributes

As an alternative for Aliases, the dot notation can also be used to set attributes from a Property Set. We commonly use Echo Steps with dot notation.

The table below shows the behaviour of setting values to Property Sets using dot notation and an Echo step. Assuming the Input argument is called with the Process Property psSiebelMessage and the psSiebelMessage is recaptured in the Output of the Echo step from the PS.

Input Arguments	Result	Comments
psSiebelMessage.ListOfOrder Interface.Orders.Account Id	The new value is replaced inside the Property Set
psSiebelMessage.ListOfOrder Interface.Orders.Id	The new value is added to the Hierarchy	A new attribute called "Id" will be created under the hierarchy "psSiebelMessage.ListOfOrder Interface.Orders"
psSiebelMessage.ListOfOrder Interface.Orders..Id	The new value is added to a Hierarchy without name	A new non-named hierarchy (or PropertySet) will be created under the hierarchy "psSiebelMessage.ListOfOrder Interface.Orders" with an attribute called "Id".

When the sample workflow attached to this document  is simulated/tested to set the attributes using dot notation, output after populate alias step in the workflow for the following elements will be as follows:
sLocationIntegrationId:Testing String - value added
sMessageId:Test Message Id via Alias

SiebelMessage/@MessageId, SiebelMessage/ListOfOrder Interface/Orders/ListOfLine Items/Line Items/ListOfRequested Schedule Lines/Requested Schedule Lines/@Source Inventory Location Integration Id in siebel message are undisturbed.

If you want to populate the SiebelMessage/@MessageId then you need to specify the property name as aMessageId in output arguments.

Summary

• Dot notation can create new items under hierarchies, aliases cannot. This operation doesn't Error-out with any of them.

• Dot notation Error-outs when reading a non-existing attribute from a Property Set. Aliases do not.

• Dot notation has a limitation of 75 characters (maximum size for step input/output arguments). Aliases can have up to 255 characters.

• Process property of type Alias will not show up in Watch Windows.

• There is no need to echo the Alias to a process property if it is used it in an expression or decision step. It is considered by the workflow as the value it is pointing to in the PropertySet.

• To read attributes from Generic Inbound messages, the Dispatch Rule transformation should be used to populate the attribute value inside the Workflow Process Property, avoiding additional Echo Steps. Use aliases if the attribute is not part of the message.

While trying to deploy a workflow process or a custom business service as Web Service, using "Deploy as Web Service..." right mouse click menu item of in Siebel Tools:

1) Unable to create the Business Service 'Web Service Deployment Service'(SBL-DAT-00227)
2) Could not find 'Class' named 'Web Service Deployment Service'. This object is inactive or
    nonexistent.(SBL-DAT-00144)

Cause
The missing standard Business Service is part of the Siebel Repository change that comes with the ACR331 delivery of the Siebel Fix Pack: 7.8.2.5 and above.

This ACR Backports Siebel Customer Order Management version 8.0 Catalog, Asset, Pricer, and CFG broker Web Services to Siebel 7.8.2.5, and also it backports the core framework (Hierarchy and EAI IO to XML Converter) to support the ability to subscribe to catalogs, customer assets, and prices from an external application as a service.

Solution
Complete the ACR 331 installation steps, outlined in the "Instructions for ACR 331" section of the "Configuration Instructions for Enhancements and Updates" chapter in the "Siebel Maintenance Release Guide" document.

This document is supplied starting  with the 7.8.2.5 Fix Pack of 7.8 Release

After running of the Fix Pack for Siebel Tools, the REPPATCH folder of Siebel Tools installation root, will contain the "ACR331ImportFilesApps.v1205.zip" and "ACR331ImportFilesCore.zip" files with the to be installed Siebel Repository improvements.

When starting a task for JMSReceiver server component using Siebel server command line you may encounter below error:

start task for comp JMSReceiver with ReceiverConnectionSubsystem= CRMAEAIJMSConnSubSys, ReceiverDataHandlingSubsystem=SiebelEcho, ReceiverMethodName=ReceiveDispatchSend 

SBL-ADM-60070: Error reported on server 'ss_migsvil1' follows:
SBL-SVR-01014: Internal: Could not send the HELLO message: (null)
SBL-NET-01033: The SISNAPI handshake timed out. The Siebel Service may not be running.

Cause

Error was caused by the DLL parameter used/required by this component was referencing the wrong version of the DLL/.so library file.

Customer enabled detailed logging on the server component, reproduced the error, inspected the log file and was able to see to detailed error message indicating that "SBL-EAI-05006: Failed to load the JVM Dll"

Customer is on HP-UX, they were setting the DLL parameter to value:

"/opt/java1.5/jre/lib/IA64W/server/libjvm.so"

However, this is not the correct version to use.  The correct version for HP-UX is from "/opt/java1.5/jre/lib/IA64N/server/libjvm.so"

The library file that should be used is from "/opt/java1.5/jre/lib/IA64N/server/libjvm.so", as this is the version documented in Siebel Bookshelf:

Siebel Bookshelf > Siebel Application Deployment Manager Guide > Configuring and Administering the ADM Framework > Process of Configuring the ADM Framework after Installing Siebel Management Server and Siebel Management Agent > Configuring the Siebel Server for ADM:

Select the JVM DLL Name parameter, and verify that the entry in the Value field references the location of the jvm.dll file in the JRE installation.

The JVM DLL Name parameter value depends on the operating system. See the following table for the values for the different operating systems.

Operating System Parameter Value

Windows: JRE_HOME/bin/client/jvm.dll
Solaris: JRE_HOME/lib/sparc/client/libjvm.so
AIX: JRE_HOME/bin/j9vm/libjvm.so (IBM JRE)
Novell SUSE Linux JRE_HOME/lib/i386/client/libjvm.so
Oracle Enterprise Linux: JRE_HOME/lib/i386/client/libjvm
HP-UX: JRE_HOME/lib/IA64N/server/libjvm.so



Solution
Once the DLL parameter was updated to "/opt/java1.5/jre/lib/IA64N/server/libjvm.so", the error no longer occurred.

When you Need to add a property called SessionId to a SiebelMessage header to pass it to an external application. To illustrate this example, the integration uses the EAI XML Write to File business service and writes the XML to a file for easy inspection. In this case, the XML Converter business service is not needed because the EAI XML Write to File business service uses a property set as an input instead of an XML string. This will simplify the workflow process a bit. The workflow process will have 4 steps : Start, Query an Account, Write to File, and End.

1. Create a new workflow process record called SessionId and define 4 steps, one start step, two business service steps, and finally an end step.

2. Connect each step and rename them as shown above.

3. In the Query an Account step, use the EAI Siebel Adapter business service and Query method.

4. In the Write to File step, use the EAI XML Write to File business service and Write Siebel Message method.

5. Define an additional Process Property on the workflow process with Type = Hierarchy and Name = Accnt Msg.

6. Set the Object Id process property with the value of the ROW_ID of an existing Account in the Siebel database.

7. For the Query an Account step, create the following input arguments:

8. For the Query an Account step, create the following output arguments:

9. For the Write to File step, create the following input arguments:
    

Scenario 2: Using the same workflow process, need to set a value for the MessageId property in the SiebelMessage header.

Scenario 3: Need to add a property called SessionId to a SiebelMessage header when using the EAI XML Converter to pass the XML as a string to the transport business service.

1. Create a new workflow process record called SessionIdEAIXMLConverter and define 5 steps, one start step, three business service steps, and finally an end step.

2. Connect each step and rename them as shown above.

3. In the Get Account step, use the EAI Siebel Adapter business service and Query method.

4. In the Convert to XML step, use the EAI XML Converter business service and Property Set to XML method.

5. In the Contact External App step, use the EAI File Transport business service and the Send method.

6. Define two additional process properties on the workflow process:

7. Set the Object Id process property with the value of the ROW_ID of an existing Account record in the Siebel database.

8. For the Get Account step, create the following input arguments:

9. For the Get Account step, create the following output arguments:

10. For the Convert to XML step, create the following input arguments:

11. For the Convert to XML step, create the following output arguments:

12. For the Contact External App step, create the following input arguments:

Scenario 4: Using the same workflow process as scenario 3, need to set a value for the MessageId property in the SiebelMessage header.

Scenario 5: Using the same workflow process as scenario 4, need to update the value for the Home Page property of the Account.