Hi need help in ALE service !

If i want to create the Ale service for only one client which will act as both server and receiver  then what r the steps ?

The code works for me.
Put a e.printStackTrace(); inside the catch block to see what exceptions are thrown (if the code isn't working then ignoring exceptions is the worst thing you could do when trying to find out what's wrong):    } catch (IOException e) {
        e.printStackTrace();
    }- Marcus

Similar Messages

  • Need help in ALE configuaration !

    Please send me an example of how to create an ALE configuaration with in one client !

    HI,
    What is ALE?
    ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.
    Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.
    How does it work?
    Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.
    In fact, 3 layers are involved in this process:
    An application layer which selects and records data in R/3.
    A distribution layer which filters and converts data.
    A communication layer which ensures the actual communication of records generated in a standard format.
    The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.
    The Intermediate Document (IDoc)
    The data transferred using ALE must have a SAP standard format to be understood from all partners in the communication. This format is the Intermediate Document (IDoc) which represents an intermediary structure between raw SAP data and EDI formats. This structure is not constant, it depends on the data to be transferred and SAP provides the structures for most SAP standard objects such as customers master data, sales orders, ...
    An IDoc with a specific structure is said to have a specific type. The IDoc type is nothing more than a version of a specific IDoc structure designed to contain data for a specific object type. For example, the IDoc type DEBMAS05 is the fifth version of a structure that represents a customer master data. The management of versions for IDocs structures is necessary because the objects evolve with time and tend to become more and more complex with new data fields or tables being added regularly.
    The conversion of raw data forth (for the sender system) and back (for the receiver system) to the IDoc format is also ensured by SAP standard function modules as long as you transfer standard objects. For non standard objects (enhancements), you must define your own IDoc structure and write your own conversion function modules.
    RFC connections
    The data communication between the SAP servers may be done by several ways. The 2 most common ways are the transactional RFC and the file. The RFC connection is used to make a direct connection between servers while the file interface speaks for itself, it uses a file containing the IDocs from the sender system as input in the receiver(s) system(s).
    The selection of a communication method is made though the ports configuration as we will see in the next section. For the purpose of this article, we are going to choose the most efficient method: the transactional RFC method. To set it up, we first need to define the RFC destinations of the partner systems.
    An RFC destination may be seen as a set of settings necessary to connect to a system using the RFC protocol. These settings include the address and type of the partner system along with connection information such as the user ID and password to use.
    The RFC destinations of all partners systems must be defined on all systems to include in the distribution model. The transaction to use for this purpose is SM59.
    Definition of the communication ports
    The communication ports determine the type of data communication that must occur between systems. When the communication is to use the RFC protocol, transactional RFC ports must be created specifying the RFC destinations of the partner systems. Use transaction WE21 for this purpose.
    Partners profiles
    In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.
    Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.
    A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.
    For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:
    A process code used to indicate which function module will be used to convert the IDoc data to SAP data.
    The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).
    The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.
    For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:
    The receiver port to which the data will be sent.
    The sending method: one IDoc at a time or by packets.
    The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.
    Definition of the distribution model and data filtering
    We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.
    The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.
    Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.
    If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners systems.
    The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems. You may afterwards add more sending and receiving systems in the model as well as more message types.
    For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.
    There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).
    This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP system and then post some business data through it to another SAP system. Business data will be picked up from custom data dictionary tables.
    ALE – Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.
    The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.
    Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.
    Now, let us understand the ALE Configuration by means of an example scenario below:
    The Scenario
    Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.
    Create three tables as shown below.
    Creating Custom IDoc type and Message type
    All the objects created should be present on both source as well as target system(s).
    1. Create segments – Transaction WE31
    Create a segment ZRZSEG1
    Add all fields of table ZCUSTOMERS to it
    Save the segment
    Release it using the menu path Edit -> Set Release
    Similarly create two more segments given below
    Seg. ZRZSEG2 – to hold all fields of table ZSOHEADERS
    Seg. ZRZSEG3 – to hold all fields of table ZSOITEMS
    2. Create Basic IDoc type – Transaction WE30
    Create a Basic type ZRZORDER
    Add the created segments in the hierarchy shown
    Maintain attributes for each of the segments
    Save the object and go back
    Release the object using the menu path Edit -> Set Release
    3. Create/Assign Message type – Transactions WE81/WE82
    Go to WE81
    Create a new Message type ZRZSO_MT
    Save the object
    Go to WE82 and create new entry
    Assign the message type ZRZSO_MT to the basic type ZRZORDER
    Also specify the Release Version
    Save the object
    Thus we have defined the IDoc structure which will hold the data to be transferred. In the [1] next part of the article we will understand the outbound settings, i.e. the settings to be done in the source system.
    Outbound Settings
    Define Logical Systems and Assign Client to Logical System – Transaction SALE
    Go to Define Logical System (See the figure)
    Define a new logical system to identify the local system and save it
    Now, go to Assign Client to Logical System (See the figure)
    Add a new entry
    Specify the client, previously created logical system and other attributes
    Save the entry
    Define a new logical system to identify the partner system and save it
    Maintain RFC Destinations – Transaction SM59
    Create a new RFC destination for R/3 type connection
    Specify the target host on Technical settings tab
    Provide the Logon credentials on the Logon/Security tab
    Save the settings
    To verify the settings, Click on Test connection or Remote logon
    Define Ports – Transaction WE21
    We need to define a tRFC port for the partner system
    Click on Transactional RFC node
    Create a new port
    Provide a description
    Specify the name of the target RFC destination
    Save the object
    Maintain Distribution Model – Transaction BD64
    Click on Change
    Create a new model view
    Provide a Short text and Technical name to the model view
    Add message type
    Specify sender and receiver systems
    Also, specify the message type that we created previously
    Save the Distribution model
    Generate/Create Partner Profile – Transactions BD82/WE20
    To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
    Otherwise, you may use transaction WE20 to create a partner profile
    On selection screen, specify the model view, target system and execute
    The result log will be displayed on the next screen
    To verify the partner profile go to WE20
    Check the partner profile for the target system
    Distribute Model View – Transaction BD64
    Select the Model View
    Go to menu path Edit -> Model View -> Distribute
    Result log will be displayed on the next screen
    Outbound IDoc Generation Program
    Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:
    Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria
    Fill the control record structure of type EDIDC
    Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver
    Fill the data records
    Define structures like the IDoc segments
    Fill the structures with fetched data
    Pass the segment name and the above structure to the appropriate fields of EDIDD type structure
    Append the EDIDD structure to the EDIDD type internal table
    Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table
    Commit work if return code is zero
    Function module returns a table of type EDIDC to provide the details about generated IDoc
    Display appropriate log
    You can [2] download sample code for the above program here.
    Thus we have completed sender side configuration required for ALE. In the [3] next part we will see how to configure the receiving system to be able to receive and post the inbound IDoc.
    Inbound IDoc Posting Function Module
    In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.
    Add Include MBDCONWF. This include contains predefined ALE constants.
    Loop at EDIDC table
    Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
    Loop at EDIDD table
    Append data from the segments to appropriate internal tables
    For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
    Update the DDic tables from internal tables
    Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
    Status 53 => Success
    Status 51 => Error
    You can [3] download the sample ABAP code for the above function module here.
    Inbound Settings
    Define Logical Systems – Transaction SALE (Please refer to Outbound Settings discussed in [4] previous part)
    Assign Client to Logical System – Transaction SALE (Please refer to Outbound Settings discussed in [5] previous part)
    Maintain RFC Destinations – Transaction SM59 (Please refer to Outbound Settings discussed in [6] previous part)
    Define Ports – Transaction WE21 (Please refer to Outbound Settings discussed in [7] previous part)
    Generate/Create Partner Profile – Transactions BD82/WE20 (Please refer to Outbound Settings discussed in [8] previous part)
    Assign Function Module to Logical message – Transaction WE57
    Create a new entry
    Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
    Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
    Save the entry
    Define Input method for Inbound Function Module – Transaction BD51
    Create a new entry
    Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
    Specify the Input method as 2
    Save the entry
    Create a Process Code – Transaction WE42
    Create a new Process Code ZPCRZ
    Select Processing with ALE Service
    Choose Processing type as Processing by function module
    Save the entry
    On the next screen, select your function module from the list
    Save the changes
    Now you will be taken to the next screen
    Double-click on Logical message
    In the Assignment to logical message, specify the message type ZRZSO_MT
    Save the changes
    Send and receive data
    On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.
    Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.
    Thus to summarize we have learned how to:
    *& Report  ZRZ_ORDER_IDOC                                              *
    REPORT  ZRZ_ORDER_IDOC                          .
    PURPOSE OF REPORT *
    Generats an Idoc for Customer Master, Sales Master
    and Sales item table.
    TABLES : ZCUSTOMERS, "Cutomer Header
             ZSOHEADERS, "Sales Header
             ZSOITEMS. "Sales Items
    DATA : S_CTRL_REC LIKE EDIDC, "Idoc Control Record
           S_ZRZSEG1 LIKE ZRZSEG1, "CUSTOMER Header Data
           S_ZRZSEG2 LIKE ZRZSEG2, "SALES HEADER Data
           S_ZRZSEG3 LIKE ZRZSEG3. "SALES Detail Data
    DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.
    DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.
    DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.
    DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE."Data Records
    DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
    "Generated Communication IDOc
    CONSTANTS :
    C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG1',
    C_ZRZSEG2 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG2',
    C_ZRZSEG3 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG3'.
    CONSTANTS: C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZRZORDER'.
    Selection Screen
    SELECT-OPTIONS : S_KUNNR FOR ZCUSTOMERS-KUNNR OBLIGATORY,
                     S_VBELN FOR ZSOHEADERS-VBELN.
    PARAMETERS :  C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZRZSO_MT',
                  "Message Type
                  C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',
                  "Partner type of receiver
                  C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'Y901',
                  C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000226',
                  C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'LSSENDS',
                  C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.
    "Destination System
    ***START-OF-SELECTION
    START-OF-SELECTION.
      PERFORM GENERATE_DATA_RECORDS.
      PERFORM GENERATE_CONTROL_RECORD.
      PERFORM SEND_IDOC.
    *&      Form  generate_data_records
    FORM GENERATE_DATA_RECORDS .
      PERFORM FETCH_ZCUSTOMERS.
      PERFORM FETCH_ZSOHEADERS.
      PERFORM FETCH_ZSOITEMS.
      PERFORM ARRANGE_DATA_RECORDS.
    ENDFORM.                    " generate_data_records
    *&      Form  fetch_zcustomers
    FORM FETCH_ZCUSTOMERS.
      SELECT *
      FROM ZCUSTOMERS
      INTO TABLE T_ZCUSTOMERS
      WHERE KUNNR IN S_KUNNR.
      IF SY-SUBRC NE 0.
        MESSAGE E398(00) WITH 'No Customers Found'.
      ENDIF.
    ENDFORM.                    " fetch_zcustomers
    *&      Form  fetch_zsoheaders
    FORM FETCH_ZSOHEADERS.
      SELECT *
      FROM ZSOHEADERS
      INTO TABLE T_ZSOHEADERS
      WHERE VBELN IN S_VBELN
        AND KUNNR IN S_KUNNR.
      IF SY-SUBRC NE 0.
        MESSAGE I398(00) WITH 'No Sales orders found'.
      ENDIF.
    ENDFORM.                    " fetch_zsoheaders
    *&      Form  fetch_zsoitems
    FORM FETCH_ZSOITEMS.
      IF NOT T_ZSOHEADERS[] IS INITIAL.
        SELECT *
        FROM ZSOITEMS
        INTO TABLE T_ZSOITEMS
        FOR ALL ENTRIES IN T_ZSOHEADERS
        WHERE VBELN = T_ZSOHEADERS-VBELN.
        IF SY-SUBRC NE 0.
          MESSAGE I398(00) WITH 'No Sales order items found'.
        ENDIF.
      ENDIF.
    ENDFORM.                    " fetch_zsoitems
    *&      Form  generate_control_record
    FORM GENERATE_CONTROL_RECORD .
      S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
      S_CTRL_REC-MESTYP = C_MESTYP. "Message type
      S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
      S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
      S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
      S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
      S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
    ENDFORM.                    " generate_control_record
    *&      Form  send_idoc
    FORM SEND_IDOC.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          MASTER_IDOC_CONTROL            = S_CTRL_REC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = T_COMM_IDOC
          MASTER_IDOC_DATA               = T_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 1
          ERROR_WRITING_IDOC_STATUS      = 2
          ERROR_IN_IDOC_DATA             = 3
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
          OTHERS                         = 5.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ELSE.
        COMMIT WORK.
        LOOP AT T_COMM_IDOC.
          WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " send_idoc
    *&      Form  arrange_data_records
    FORM ARRANGE_DATA_RECORDS .
      DATA: W_INDEX1 LIKE SY-TABIX,
            W_INDEX2 LIKE SY-TABIX.
      SORT T_ZCUSTOMERS BY KUNNR.
      SORT T_ZSOHEADERS BY KUNNR VBELN.
      SORT T_ZSOITEMS BY VBELN POSNR.
      LOOP AT T_ZCUSTOMERS.
        S_ZRZSEG1-KUNNR = T_ZCUSTOMERS-KUNNR.
        S_ZRZSEG1-NAME1 = T_ZCUSTOMERS-NAME1.
        S_ZRZSEG1-ORT01 = T_ZCUSTOMERS-ORT01.
        S_ZRZSEG1-LAND1 = T_ZCUSTOMERS-LAND1.
        T_EDIDD-SEGNAM = C_ZRZSEG1.
        T_EDIDD-SDATA = S_ZRZSEG1.
        APPEND T_EDIDD.
        CLEAR T_EDIDD.
        CLEAR W_INDEX1.
        READ TABLE T_ZSOHEADERS WITH KEY KUNNR = T_ZCUSTOMERS-KUNNR BINARY SEARCH.
        IF SY-SUBRC = 0.
          W_INDEX1 = SY-TABIX.
          LOOP AT T_ZSOHEADERS FROM W_INDEX1.
            IF T_ZSOHEADERS-KUNNR NE T_ZCUSTOMERS-KUNNR.
              EXIT.
            ENDIF.
            S_ZRZSEG2-VBELN = T_ZSOHEADERS-VBELN.
            S_ZRZSEG2-KUNNR = T_ZSOHEADERS-KUNNR.
            T_EDIDD-SEGNAM = C_ZRZSEG2.
            T_EDIDD-SDATA = S_ZRZSEG2.
            APPEND T_EDIDD.
            CLEAR T_EDIDD.
            CLEAR W_INDEX2.
            READ TABLE T_ZSOITEMS WITH KEY VBELN = T_ZSOHEADERS-VBELN BINARY SEARCH.
            IF SY-SUBRC = 0.
              W_INDEX2 = SY-TABIX.
              LOOP AT T_ZSOITEMS FROM SY-TABIX.
                IF T_ZSOITEMS-VBELN NE T_ZSOHEADERS-VBELN.
                  EXIT.
                ENDIF.
                S_ZRZSEG3-VBELN = T_ZSOITEMS-VBELN.
                S_ZRZSEG3-POSNR = T_ZSOITEMS-POSNR.
                S_ZRZSEG3-MATNR = T_ZSOITEMS-MATNR.
                S_ZRZSEG3-NETWR = T_ZSOITEMS-NETWR.
                S_ZRZSEG3-ZMENG = T_ZSOITEMS-ZMENG.
                T_EDIDD-SEGNAM = C_ZRZSEG3.
                T_EDIDD-SDATA = S_ZRZSEG3.
                APPEND T_EDIDD.
                CLEAR T_EDIDD.
              ENDLOOP.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " arrange_data_records

  • Need help configuring Excel Services

    I've configured both the Excel Serives and Secure Store Target applications and continually receive the following error message when trying to view the Simple Projects List sample report:
    An error occurred while accessing application id ProjectServerApplication from Secure Store Service. The following connections failed to refresh:
    Project Server - Simple Projects List
    The Server Logs show the following errors:
    Access Denied: Claims stored in the credentials did not match with the group claim for a group app.
    The Microsoft Secure Store Services application Secure Store Service failed to retrieve credentials.  The error returned was 'Access Denied.' ...
    Access is denied. (Fault Detail is equal to Microsoft.Office.SecureStoreService.Server.SecureStoreServiceFault)
    SSS has failed with the following exception: Access is denied.
    Unable to esablish a connection using credentials retrieved from SSS.  This could be because the Unattended Service Account is not configured or because the credentials retrieved from SSS are not valid. 
    I've repeated the steps to create these configurations a few times, and continue to get the same errors.  Any help would be appreciated!
    Thanks

    Hello,
    I need help setting up excel services.
    Excel service is already running on sharepoint server.
    I have one reporting file which is generated by DBA with database connection. i want to upload that file under document library and i want whenever user open it through document library, it gets updated through database connection 
    This is my first time, so pls guide me
    Reporting file has authentication set to --> None 
    Do i require any specific settings for authentication? like unattended account ? which username should i use
    Connection String -->
    Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;User ID=ExcelServices;Initial Catalog=SurveyData;Data Source=jdb1;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RSTKW7W-06709;Use Encryption for Data=False;Tag
    with column collation when possible=False
    http://../training/sptestsite/Medication_Audit_Report
    http://../training/sptestsite/Medication_Audit_Data_Connection_Library/
    Trusted File Location - is this place do i need to upload that reporting file? 
    Trusted Data Connection Libraries - is this place do i need to save connection file .odc ?
    If i am not wrong, should i put
    Trusted File Location = http://../training/sptestsite/Medication_Audit_Report
    Trusted Data Connection Libraries = http://../training/sptestsite/Medication_Audit_Data_Connection_Library/
    http://../training/sptestsite/Medication_Audit_Report -- Here only reporting file will be uploaded right?
    http://../training/sptestsite/Medication_Audit_Data_Connection_Library/ -- Here only database connection .odc file will be uploaded?
    what other settings are required. please correct me
    my email address - [email protected]
    Harsh

  • Need Answer on ALE Service Layer

    In my  cusomized outbound program i am using a function module MASTER_IDOC_DISTRUBUTE to generate the IDOCS. I am passing the both sender and reciever values to the function module MASTER_IDOC_DISTRUBUTE then distribution model in BD64 is not required. if we are not passing the both sernder and reciever to the MASTER_IDOC_DISTRUBUTE, the MASTER_IDOC_DISTRUBUTE will pick both the sender and reciever from the ALE Distribution model (ALE Service Layer)  . What my doubt if i pass both sender and reciver need it won't execute distribution model in the BD64. In this situation  If i need a filters and converstion for the recievers  then i should use the diribution model. In this situaion if i pass both sender and reciever to the MASTER_IDOC_DISTRUBUTE does the ALE Service Layer ( Conversions & Filtters )  will execue?

    Hi,
    >>>>But I don't know how to achieve this. I guess using Distribute Model,
    yes of course
    >>>> If so, a client for edi subsystem(non-sap system) need be defined in SAP R3 system. I doubt about this.
    yes a logical system for example
    >>>>Another problem is how to define a client for non-sap system in SAP R3 sytem.
    logical system
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Need help abt bluetooth services on windows 8 enterprise

    glad to join hp forums and thats help me too much persoanlly also at work 
    got problem in bluetooth services nd iam using windows 8 enterprise all bluetooth services was working well on windows 7 professional but i upgraded ma os nd now just i can send and recive files via bluetooth , cant play music directly too , i got screen shot thats will explain more :    
    thats what i need i got this screen shot from help its full services  i got just one option its file transfer
    and this is what i got right now   
    need help i like win 8 more than 7 so i wont back to use win 7 

    With the Error 2, let's try a standalone Apple Application Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of the issue.
    Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
    http://www.apple.com/itunes/download/
    Download and install the free trial version of WinRAR:
    http://www.rarlab.com/download.htm
    Right-click the iTunesSetup.exe (or iTunes64Setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
    Go into the folder and doubleclick the AppleApplicationSupport.msi to do a standalone AAS install.
    Does it install properly for you?
    If instead you get an error message during the install, let us know what it says. (Precise text, please.)

  • Need help in URL Service Data Control

    Hi Everyone,
    I'm working on JDev11gUp2, ADF-RC
    I am using URL Service Data Control to fetch data from CSV File and i got success but I need to know that is there any way to pass File Connection URL Dynamically at run time, As i know we have to provide URL string at design time, but i have multiple files to pass at run time , Then?
    And one more question that Once the data is uploaded into af:Table from my CSV file. then after Any data change in CSV file must reflect in af:table with that change like other iterator refresh functionality. but I'm not able to do that, Simple question is, How to Re fetch the data from CSV file at run time?
    Your answer would be really appreciated as it would really help me.
    Thanks
    Fizzz...

    Hi Fizz,
    Not sure of the answer to your specific question. A couple of thoughts, though:
    You could try putting some code in a backing bean action listener to get the data control from an iterator binding (where you have added an iterator binding to your page definition) and then using the debugger to inspect the runtime type of the data control returned - then look to see if that type has a setURL method.
    [url http://database.in2p3.fr/doc/oracle/Oracle_Application_Server_10_Release_3/web.1013/b25947/adv_data_controls005.htm]this link talks about creating your own data control type - where you could certainly expose a method to set a URL. More work, but you have complete control.
    Hope this at least gives you an idea or two.
    John

  • Need help calling SOAP service deploy in WebLogic

    Hi bros & sisters,
    My name is veda.
    Need some help in calling a SOAP binding web service deploy in Weblogic, using classic ASP
    After reading this link http://www.aspfree.com/c/a/ASP/Consuming-a-WSDL-Webservice-from-ASP/,
    1. i still do not know what value to pass in for parameter SoapURL. I did try http://invicta.app.vic:8002/RTO/RTOService/getCustomerOffers, but return a negative result.
    2. Am i right to say i cannot do a SoapRequest.Open "GET",
    or SoapRequest.Open "POST", because i only have a SOAP protocol binding instead of HTTP protocol binding.
    I really appreciate any help to enlighten me.
    Below is my complete wsdl. Its quite a small wsdl
      <?xml version="1.0" encoding="utf-8" ?>
    - <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com.gtr.ma.rto/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://com.gtr.ma.rto/" name="RTOService">
    - <types>
    - <xsd:schema>
      <xsd:import namespace="http://com.gtr.ma.rto/jws" schemaLocation="http://invicta.app.vic:8002/RTO/RTOService?xsd=1" />
      </xsd:schema>
    - <xsd:schema>
      <xsd:import namespace="http://api.interact.coycorp.com/xsd" schemaLocation="http://invicta.app.vic:8002/RTO/RTOService?xsd=2" />
      </xsd:schema>
      </types>
    - <message name="getCustomerOffers">
      <part xmlns:ns1="http://com.gtr.ma.rto/jws" name="parameters" element="ns1:getCustomerOffers" />
      </message>
    - <message name="getCustomerOffersResponse">
      <part xmlns:ns2="http://com.gtr.ma.rto/jws" name="parameters" element="ns2:getOffersResponse" />
      </message>
    - <message name="endCustomerSession">
      <part xmlns:ns3="http://com.gtr.ma.rto/jws" name="parameters" element="ns3:endCustomerSession" />
      </message>
    - <message name="endCustomerSessionResponse">
      <part xmlns:ns4="http://com.gtr.ma.rto/jws" name="parameters" element="ns4:endCustomerSessionResponse" />
      </message>
    - <portType name="RTOImpl">
    - <operation name="getCustomerOffers">
      <input message="tns:getCustomerOffers" />
      <output message="tns:getCustomerOffersResponse" />
      </operation>
    + <operation name="endCustomerSession">
      <input message="tns:endCustomerSession" />
      <output message="tns:endCustomerSessionResponse" />
      </operation>
      </portType>
    - <binding name="RTOImplPortBinding" type="tns:RTOImpl">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    - <operation name="getCustomerOffers">
      <soap:operation soapAction="" />
    - <input>
      <soap:body use="literal" />
      </input>
    - <output>
      <soap:body use="literal" />
      </output>
      </operation>
    - <operation name="endCustomerSession">
      <soap:operation soapAction="" />
    - <input>
      <soap:body use="literal" />
      </input>
    - <output>
      <soap:body use="literal" />
      </output>
      </operation>
      </binding>
    - <service name="RTOService">
    - <port name="RTOImplPort" binding="tns:RTOImplPortBinding">
      <soap:address location="http://invicta.app.vic:8002/RTO/RTOService" />
      </port>
      </service>
      </definitions>

    Use a proper Java web service client stack that will make your life easier.

  • Need help with ALE

    We are trying to go live with our XI / ICH implementation and are getting the following error
    <b>Unable to convert sender service to an ALE logical system</b>
    Can someone point me to where I can fix this?
    Thanks
    Mike

    Hi Michael,
    there are two things you need to check
    1. compare with SLD (for technical system name) in SLD
    2. you can also put another business system in <b>sender system</b>
    field of your receiver agreement
    both approaches described in:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Hi  all , Need help on Core Services , RFC and Enterprise Services

    Can  anyone provide me links on how to use Core Services , RFC and Enterprise Services.
    I need to communicate with two systems , one uses RFC and the other uses Enterprise Service , so I need to differentiate between them .

    For RFC:
    http://help.sap.com/saphelp_nwce10/helpdata/en/8f/0f6f4132f15c58e10000000a1550b0/frameset.htm
    For modelling external services:
    http://help.sap.com/saphelp_nwce10/helpdata/en/45/174ae492ef5d79e10000000a11466f/frameset.htm
    For Web services:
    http://help.sap.com/saphelp_nwce10/helpdata/en/44/f6087db2b12952e10000000a11466f/frameset.htm
    Developing first web service:
    http://help.sap.com/saphelp_nwce10/helpdata/en/46/917a26cf75581ce10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_nwce10/helpdata/en/27/e49122a62d4dc189b7308c2b0c852e/frameset.htm

  • I need help for printing service in Java

    Hello :
    I need to print some file from java program .
    I did every thing , but when i run the program : it didn't return any printer as print service from the system, although I install 2 printers in my system.
    by the way : i use Windows XP

    I was in a rush this morning and forgot my crystal ball. Please post your code and remember to use the code tags.

  • Need help with Gateway / Services

    Running a standalone OWSM install - 10g 10.1.3
    We have been through the Gateway config and deployment several times.
    Also have a test service registered to the gateway, however, no matter what we try, we continue to get a 500 Internal Server Error when attempting to access the service URL: Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
    Which application log do I need to look at? The gateway log doesn't register any errors...
    I'm sure I'm missing something, but I can't find it...

    I'm not sure why or how, but it's fixed...
    I set logging to 'FINEST' and restarted everything and suddenly it all started working as expected.
    Set logging back to INFO and restarted - still working.
    No idea why it would just start working...

  • Need help with Web Services SDK.

    I am new to Web Services SDK can I get documentation on same.

    For documentation about the BOE XI R2 SP2 Web services go to our DevLibrary: http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm
    then locate the Web Services topic under which, you will find the necessary info to help you deal with BOE Web Services.
    Cheers
    Alphonse

  • Need help in Assembler service

    I installed Adobe Livecycle ES3 with WAS. I'm able to login to the adminui but could not see assemblerservice option under home->services->applicaiton and services->service management and then selected category as Common. Could you please let me know the steps to get the assembler service displayed in the list ASAP?
    Thanks in advance!!
    Bhargavi.

    No, Please look in <Installationfolder>\Adobe\Adobe LiveCycle ES3\deploy for jar adobe-assembler-dsc.jar. If its there, then connect to your server with work bench and install this jar through components tab in workbench. Workbench is the client for connecting to a livecycle server.
    You can get help for installing dsc via workbech under "Impot your component"  heading at the link http://www.adobe.com/devnet/livecycle/articles/dsc_development.html

  • Need help developing web services on Jdeveloper

    Hi,
    I'm having some problems developing a particular web service using jdeveloper 10.1.2.1.0 (build 1913).
    The web service is located on a remote computer (windows server 2003 SP1), deployed on a jboss3.2.5.
    I got the following error:
    java.lang.ClassCastException: oracle.xml.parser.v2.XMLText
    at oracle.jdeveloper.webservices.runtime.WrappedDocLiteralStub.fromElement(WrappedDocLiteralStub.java:614)
    at mypackage1.PdfGenStub.getConfigurationXML(PdfGenStub.java:189)
    at mypackage1.PdfGenStub.convertDocumentToPdf(PdfGenStub.java:241)
    at mypackage1.PdfGenStub.main(PdfGenStub.java:42)
    The web service is from a product that we have that converts documents to pdf.
    Any ideas ??
    However, I will try to intall the product on another machine that has connection outside the company network to put the WSDL link here for anyone who wants to test it .
    thanks

    Hi,
    Would really help if you could provide the wsdl and also steps to reproduce this exception, for us to try it out locally.
    You could also try to install the latest JDev 10.1.3.1 available on OTN, to see if it works on it.
    Regards,
    Sunil..

  • Need help restoring cancelled service

    During a recent financial hardship, my U-Verse Internet service was canceled. I just paid my balance and would like my service restored. Is their a way to contact customer service after hours?

    Hi ,
    I am so sorry about the issues you are having with your service. Tech support is open 24x7, and we can definitely help with this. Also, you can send us a message by clicking here. Be sure to include your name, account number, phone number, and the best time to reach you. 
    Keep an eye on the at the top right corner of your screen for a response.
    In the meantime, let me know if you have any other questions or concerns!
    -ATTU-verseCare

Maybe you are looking for