Queries related to MAM configuration and MI synchronization
Hi,
I have queries as to the synchronization in MI & MAM
1. When I am synchronizing with MI Server, the requests are going in I-Waiting work lists in work list monitor.. What could be the reason for it.
2. I require clarification as to exact purpose of the variants used in Master data selections of the MAM configuration. Is it to reduce the replicator database or to reduce the handheld database.
I have created one variant for each FL, equipment and measurement points
A. The FL variant downloads all the necessary FL to the MI server. We havent assigned the variant to the user so as download the ony the FLs related to work orders.
B. The Equipment variant doesnt download any equipments because we are not using any equipments
C. The measurement point variant downloads the measurement points related to the FLs mentioned in the FL variant.
In the above scenario, we are able to download Work orders, Functional locations but not able download measurement points. In our scenario, we dont have equipments and measurement points are related to FL directly. The work list monitor displays "No data from R/3 downloaded".
Is it due to the MAM configuration ?
Can I debug the synchronization process in MI server so as to simulate the events happening when a synchronization is requested from MI client.
Thanks
Raj
Hi Raja,
Question 1: Two possible reasons for I-Waiting - breakpoint in backend BAPI and it waits for action. Or one of the SyncBOs is not activated (very common reason, check merep_pd).
Question 2: "Master data selection" is for replication. Technical objects on the device are coming from three sourses - when they are referenced on order and notif header level, when they are in order object list (and this is activated on the backend), standalone TOs configured in "user-dependent data".
Normally, if order references FL, FL should come to the device, if this FL references Meas. Point it should come to the deice as well. If you check logs for FL you will probably see "cascading error" for the meas. point. Few things to check - this meas. point is returned by the BAPI MAM041_getlist so it is suposed to be replicated. If it is in the list - check BAPI MAM041_getdetail to see that it does not return error. No error - check DB on the middleware to see that it is indeed replicated.
Regards,
Larissa Limarova
Similar Messages
-
Queries Related to B2B configuration
Hi,
We are working on EDI-B2B implementation
I have following Queries regarding the configuration in B2B.
1) While Creating the Business Actions we have the following fields
Translation Enabled –yes/no
Validation Enabled –yes/no.
In the Document it says the performance will be impacted if validation is enabled.Needs inputs on this.
2) When we create trading partner (remote or host) why do we set the
Application Sender code and Application receiver ID to the same value.
3) Can we use more than one Trading Partner Identification Type (Duns number AS2 identifier) for the same Trading Partner?
4) If we have more than one outgoing Document like 855,997,856 how we set the outbound Directories in the URI.
Regards
LalitHi Ramesh,
3-->Iin our case SFTP is not part of B2B.It is external to B2B.In B2B we are simply treating as the case of File protocol.
Actually what I asked was we have DUNS number both of the trading Partner(host and remote) so can we use that as the identifer(in the Identification section while creating the trading partner) or do we use names like ACME as we have used in ACME-GLOBALSCHIP sample.
For File protocol it always uses Name as the Identification.
I have few new Queries
1)For some reasons if I have to make changes in the Trading partner name or changing Business Protocol or changes at other places in B2B configuration.
Do we need to create the Agreement again.If yes then do we delete the prevoius agreement or update will work.
Moreover what will happen to the Configuration step.
Just quese and revalidate and redeploy the Agreement.
2) how to move the configuration settings from Development environment to Production Environment.
Export the configuration and import it into production box. Make sure to change the appropriate end point and revalidate and redeploy.
3) I have used the 850.ecs and 850.xsd(also 997 ) in my sample application as the one sent by you.
Though I have developed the 850.ecs and 997.ecs using the B2B document editor as per the Trading partner specification I thinking whether to use new ones or continue using the Old one sent by you because it seems to be the superset.
The only issue is that it has all the segments irrespective of whether they are used or not.
What do you suggest on this.
Depends on your requirement. You can use one shipped with the product. -
Question related to POF configuration and use-subclasses
Hi,
I noticed that the default POF configuration in coherence.jar (coherence-pof-config.xml) forces the use-subclasses flag to true (the ultimate use-subclasses value is true if whichever loaded POF configuration file specifies it to be true), and thus making it impossible to get error messages if a certain subclass of a registered type is not registered specifically in the POF-configuration, and users may silently lose data this way.
My question is:
Is the use-subclasses flag in the coherence-pof-config.xml set to true only because of Throwable-s, or are there other Coherence-provided classes which are serialized by subclass resolution and thus depend on the use-subclasses flag being true?
If only the Throwable-s depend on that, then instead of setting it to true, we can set it to false and use the following class instead of ConfigurablePofContext as the Serializer class for the POF-enabled services:
import com.tangosol.io.pof.ConfigurablePofContext;
import com.tangosol.run.xml.XmlElement;
* This class extends ConfigurablePofContext with the possibility to
* configurably disable the subclass-allowed setting forced true in the
* coherence-pof-config.xml, and still be able to use ThrowablePofSerializer for
* each not specifically configured Throwable subclass.
* @author Robert Varga
public class ThrowableAwareConfigurablePofContext extends
ConfigurablePofContext {
* By setting this flag to true, it is possible to disable subclass
* resolution. Interface resolution remains untouched.
private boolean m_fDisableSubclassAllowed;
* {@inheritDoc}
public ThrowableAwareConfigurablePofContext() {
* {@inheritDoc}
* @param sLocator
public ThrowableAwareConfigurablePofContext(String sLocator) {
super(sLocator);
* {@inheritDoc}
* @param xml
public ThrowableAwareConfigurablePofContext(XmlElement xml) {
super(xml);
* Sets the {@link #m_fDisableSubclassAllowed} flag. You can set this as an
* <init-param> in the Coherence cache configuration file.
* @param disableSubclassAllowed
public void setDisableSubclassAllowed(boolean disableSubclassAllowed) {
this.m_fDisableSubclassAllowed = disableSubclassAllowed;
* @return false if disableSubclassAllowed is true, or result from the super
* implementation otherwise.
@Override
protected boolean isSubclassAllowed() {
return (!m_fDisableSubclassAllowed) && super.isSubclassAllowed();
* If the super implementation could not resolve the type id for the class,
* and subclass-allowed is disabled and clz is a {@link java.lang.Throwable}
* subclass then it falls back to the configuration for
* {@link java.lang.Throwable}.
@Override
protected int getInheritedUserTypeIdentifier(Class clz) {
int result = super.getInheritedUserTypeIdentifier(clz);
if (result == -1 && !isSubclassAllowed()
&& Throwable.class.isAssignableFrom(clz)) {
result = getUserTypeIdentifier(Throwable.class);
return result;
}Thanks and best regards,
Robertdcarrano wrote:
Hi Robert,
If you are only interested in Java you are correct.
If you need more detail please let me know but I hope this answers your question.
Best regards,
-DaveHi Dave,
I am also interested in other environments, so I need more detail.
I am looking at the portability of my POF Serializer generator in which I assume that use-subclasses is false, because supporting use-subclasses being true would be quite hard to define, not to mention implement.
Thanks and best regards,
Robert -
Queries related to APP run and Configuration
Hi All,
i would like to know few in APP run..
Can we make partial payments through APP? if yes how can it be configured?
on what basis the APP proposal picks open items from vendor items?
some times system showing the items in Exceptions list, there we have to double click on each line item and need to reallocate to payment method and house bank id and account id....hence after selecting this record how can we exclude this record?
some times system is not picking all the due items of a vendor, then how can we add more items for the payment proposal, those items are not even in exceptions list?
any one please guide me in this, hence it was a urgent requirement for my client....
SRINUHi Srinu,
In APP run partial payment is possible
For that u can configure OBB8 and OBB9
There u configure terms of payment &installment
in OBB8 you have to select Installment payment check box ofter that OBB9 give intervals of partial payments
Now system will give the partial payment through APP
Exception
for that go through edit proposal there, select which one u dont want to pay and give the payment block next system doesnt pay that invoice
some times system doesnt pay the vendor due line item
for that you delete the uncompleted proposals through in run date click F4 button we can able to see those proposals
If u have any doubt feel free to ask
Regards
Surya -
Queries related to MAM enhancements
Hi,
We require more fields than what is offered by standard MAM application.
Please let me know the procedure to do so.
My understanding is
Step 1 : Add the fields in BADIs so that it can be pulled using standard BAPI wrappers.
Step 2 :Regenerate the syncbo after modifying the BAPI wrappers and edit the sync bos to download the fields to the mobile device. We would need license key for SAP to do this
Step 3 : Add set and get functions for the newly added fields in the java files.
I have few queries
1. Please let me know if the above understanding is correct.
2. After modifying the syncbos, can I add get and set functions in the impl java files without importing the xml file from syncbos?
I am using standard MAM 2.5 app, in which the app form belongs to that of non generic syncbo access code.
3. In the order management module, when I click on the order management link,it displays the list of orders..
Can I change this functionality to introduce another jsp to scan the equipment.Is such a customization possible
Regards
Raja SekharHi Raja,
Question 1: Two possible reasons for I-Waiting - breakpoint in backend BAPI and it waits for action. Or one of the SyncBOs is not activated (very common reason, check merep_pd).
Question 2: "Master data selection" is for replication. Technical objects on the device are coming from three sourses - when they are referenced on order and notif header level, when they are in order object list (and this is activated on the backend), standalone TOs configured in "user-dependent data".
Normally, if order references FL, FL should come to the device, if this FL references Meas. Point it should come to the deice as well. If you check logs for FL you will probably see "cascading error" for the meas. point. Few things to check - this meas. point is returned by the BAPI MAM041_getlist so it is suposed to be replicated. If it is in the list - check BAPI MAM041_getdetail to see that it does not return error. No error - check DB on the middleware to see that it is indeed replicated.
Regards,
Larissa Limarova -
Queries related to Toplink ClientSession and UnitOfWork
I'm facing with a memory leak issue and was trying to investigate it by looking at the log files. Here, are few things I saw which I thought are potential reason but could not really link with a memory leakage -
Code looks like -
Session session = DBManager.acquireSession();
UnitOfWork uow = session.acquireUnitOfWork();
...some processing/work with UnitOfWork but no release
The program navigates to a different path without releasing UnitOfWork or Session.
When I look at the log files I see that the Sessions are getting garbage collected (I see log entries that say Session has been released) even though after an hour or so. I guess I’m able to see that Sessions are being garbage collected as finalize() method of ClientSession internally makes a call to ClientSession.release() method. However, I never see UnitOfWork being garbage collected or I don’t know as there are no corresponding log entries.
Queries –
1) Would these un-released UnitOfWork hold onto some memory causing a Memory leak??
2) What happens to UOWs that are acquired from a Session that has been eventually garbage collected?? Will garbage collection of Session inturn cause garbage collection of UOWs??
I also have a code like –
Session session = DBManager.acquireSession();
.. Do some work with Session
session.release();
..after some time use the same Session reference to do more work like
session.readObject();
Over here I see that Session can still be used after it has been released with no problem. But I guess calling a release() next time on it won’t have any impact, is that true?? Also, now this would be a hanging Session as it was not released, right??
Eagerly waiting for some help!Simpler usage is to link UnitOfWork with the JTA transaction, then when JTA transaction commit or rollback the UnitOfWork remove will be called, and UOW will do the same on its parent ClientSession.
In Java, unlike Microsoft COM, instances will be garbage collected if reference each other like a cycle.
There is no side effect of not calling remove on UnitOfWork, but if not calling on ClientSession, and the ClientSession hold a DB connection from a pool, the pool is left with a missing connection, the act of adding back the connection to the pool is not something done by GC alone. -
Alert Configuration and Alert inbox showing error
I have activated all services in SICF which are related to alert configuration and changed the HTTP ABAP port according the note 750287
com.sap.aii.rwb.server.centralmonitoring.httpport to the HTTP port number mentioned in SMICM -> goto -> services -> HTTP port number.
This is error i am facing after chaning the port number in Exchange profile and activated and refreshed all cache using
you can also try to reset just ine case:
a) the RWB
http://<J2EE-Host>:<HTTP-Port>/rwb/rtc?op=init
b) exchange profile
http://<J2EE-Host>:<J2EE-Port>//rep/support/admin/index.html
Repository, Directory, Runtime
(All properties -> Refresh )
<i>Call of URL http://Hostname:8001/sap/bc/bsp/sap/alertinbox/index.htm terminated due to error in logon data.</i>
what are the changes expected to do..
Regards,
Govada.> I have activated all services in SICF which are
> related to alert configuration and changed the HTTP
> ABAP port according the note 750287
This is perfect.
>
> com.sap.aii.rwb.server.centralmonitoring.httpport to
> the HTTP port number mentioned in SMICM -> goto ->
> services -> HTTP port number.
This is again correct.
>
> This is error i am facing after chaning the port
> number in Exchange profile and activated and
> refreshed all cache using
>
> you can also try to reset just ine case:
> a) the RWB
> http://<J2EE-Host>:<HTTP-Port>/rwb/rtc?op=init
This is wrong. Try to reset using the J2EE port.
> b) exchange profile
> http://<J2EE-Host>:<J2EE-Port>//rep/support/admin/inde
> x.html
> Repository, Directory, Runtime
> (All properties -> Refresh )
This is correct as well.
Correct the wrong step, by giving the correct URL and then try again.
Regards
Bhavesh -
Queries related to web-ui configuration.
Hi Experts,
I have some queries related to web-ui configuration :
I have copied standard component of Lead with values Role Key = Zconfig key, Component Usage, Object Type, Object Subtype= Default and made some changes(renamed some fields) and assigned same Config key to business role further assigned that role to my user but when i open the lead transaction from webui the screen i see is standard and not which is configured by me, i have also confirmed screen by checking field property(F2) it shows my zconfig key, please clear my below queries:
1) I m missing any steps in screen configuration or assignment
2) I need to assign this new configured screen to diffrent users for diffrent project.
3) How to hide some field which is not required in transaction.
I have gone through the various threads in sdn but unfortunately i did not get clear idea.
Thanks and Regards,
DD'sHi harshit,
Thanx for u r quick reply i have done it by making changes in DO_CONFIG_DETERMINATION, can u please suggest how to hide unwanted fields in webui transaction.
Thanks and Regards,
DD's
Edited by: DD's on May 11, 2009 11:51 AM -
I have purchased my apple iPhone 5 from Germany, and now I am back to India. I need to contact the German apple support team for queries related my device. How to contact the apple support team in Germany from India ?
Warranty and support is only valid in the country of origin, or in the case of a device purchased in an EU country, only in an EU country.
Unless you will be visiting an Apple store in one of the EU countries before the warranty expires, you are pretty much out of luck.
FYI, the Contact Us link at the bottom of the page provides the appropriate contact information for Apple. -
Idoc Configuration and interfaces related to 810
Hi,
Can any one tell me the entire configuration of ALE and EDI810 supported tools?
Thanks
Shobi<b>Hi,
ALE
To develop a new custom ALE scenario, comprises 5 steps:
1. Design and develop the custom IDoc with its segments and a new message type
2. Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3. Develop the outbound process which does the following:
Populates the custom IDoc with control info and functional data
Sends the IDoc to the ALE layer for distribution
Updates status and handles errors
4. Configure the ALE inbound side (partner profiles with inbound process code)
5. Develop the inbound process which does the following:
Reads the IDoc into a BDC table; selects other data that is required
Runs transaction using call transaction or BDC session
Updates status and handles errors
Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
Figure 1: ALE Scenario model
1.1. ALE Example
For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service providers system.
Figure 2: Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
*--- Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*--- Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
*--- Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
*--- Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
*--- Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
*--- Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
*--- Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
* Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
*--- Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
*--- Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
*--- Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
*--- OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
*--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
*--- Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
*--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
*--- Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.</b>
Foe EDI 810 Mapping Refer <b>http://www.altova.com/videos.asp?type=0&video=edimapping</b>.
Online demo you can see,
Thanks
Manju -
Hi Experts,
I have few basic queries related with OIM 11.1.1.3
1) Can we use GTC connector to export data of users (Newly created users on daily basis) to CSV file?
I think No, But just wanted to confirm with you guys.
2) The LdapConfig utils in OIM11.1.1.3 provides facility to replicate the users in OID. Like whenever I am creating a user in OIM..Its creating it in OID as well.
My question here is:
a) Since we dont have any process form here so how can i add a new attribute in the data which is getting created in OID through OIM? Like I want to provision a custome attribute along with existing attributes..how will i achieve this?
b) In OIM11.1.1.3, In what scenario we can use OID connector and LdapConfig settings? Like..when to use connector..for provisoning data in OID.
Rajiv,Kevin,Sunny...waiting for ur valuable inputs :)
Regards,
J
Edited by: J_IDM on May 18, 2011 2:56 AMThanks Rajiv,
We have process form. We don't have Object Form but we have Request Dataset for that.
But since my OID is configured using LdapConfig and I am not using OID connector. So I dont see any process form associated with my OID.
How can i add new attribute here (Suppose carLicense I need to provision to OID)?
You'll use OID connector when you'll have OID as a target system.
Even I am not using any connector but my users are succesfully created in OID..using OIM 11g.
So I just wanted to know..under what circumstances we should go for LdapConfig(Auto OID user creation) and OID connector in OIM 11g
Thanks very much!!
J -
AAMEE 3.1 deployment get stuck at configuring and quits.
Hello,
I made a 32bit deployment of Adobe and when I test it out on my PC with msiexec with borwsers all off and no adobe applications running it makes it half way throgh configuring and then stops and the stats bar goes back to the start and it quits.
Bellow is the PDApp.log, any help would be grateful.
Mike
11/13/2013 15:26:20 [INFO] DeploymentManager - Build Version - 3.1.105.0
11/13/2013 15:26:20 [INFO] DeploymentManager - Logging Level verbosity Set to 4
11/13/2013 15:26:20 [INFO] DeploymentManager - Executing immediate custom action for install mode.
11/13/2013 15:26:20 [INFO] DeploymentManager - The CustomActionData string is : mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
11/13/2013 15:26:20 [INFO] DeploymentManager - Successfully executed the immediate custom action for install mode .
11/13/2013 15:26:25 [INFO] DeploymentManager - Build Version - 3.1.105.0
11/13/2013 15:26:25 [INFO] DeploymentManager - Logging Level verbosity Set to 4
11/13/2013 15:26:25 [INFO] DeploymentManager - Executing the deferred custom action.
11/13/2013 15:26:25 [INFO] DeploymentManager - Obtained the following as CustomActionData
11/13/2013 15:26:25 [INFO] DeploymentManager - mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
11/13/2013 15:26:25 [INFO] DeploymentManager - mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
11/13/2013 15:26:25 [INFO] DeploymentManager - Original database path is : d:\32bit Adobe2\Build\32bit Adobe2.msi
11/13/2013 15:26:25 [INFO] DeploymentManager - OptionXML saved at location :: C:\Users\mseddon\AppData\Local\Temp\{386867CE-0461-4FC3-83EA-466DEF7D5226}\\{0CB84CF3-741 B-4DDA-B3DF-B3066BA0B327}
11/13/2013 15:26:25 [INFO] DeploymentManager - Build Version - 3.1.105.0
11/13/2013 15:26:25 [INFO] DeploymentManager - Logging Level verbosity Set to 4
11/13/2013 15:26:25 [INFO] DeploymentManager - Initializing Custom Action Data from parameters
11/13/2013 15:26:25 [INFO] Utilities - Folder does not exist
11/13/2013 15:26:25 [INFO] DeploymentManager - Provisioning Tool path is (C:\Users\mseddon\AppData\Local\Temp\{386867CE-0461-4FC3-83EA-466DEF7D5226}\\{3E60E409-97 DF-4D53-A4EB-846FB440181F}).
11/13/2013 15:26:25 [INFO] DeploymentManager - Starting to run the custom action for install mode
11/13/2013 15:26:25 [INFO] DeploymentManager - STEP 1: Starting to parse Option XML.
11/13/2013 15:26:25 [INFO] DeploymentManager - Deployment XML created at path :: C:\Users\mseddon\AppData\Local\Temp\{1B76C0EA-C5CA-468A-AC2E-AF580CF03F2E}\\{65525300-78B 5-4102-95D3-6980332AB10A}
11/13/2013 15:26:25 [INFO] DeploymentManager - Deployment Manager is running in Install Mode.
11/13/2013 15:26:25 [INFO] DeploymentManager - Self-Update BootStrapper Relative Path doesn't exist.
11/13/2013 15:26:25 [INFO] DeploymentManager - Override XML created at path :: C:\Users\mseddon\AppData\Local\Temp\{1B76C0EA-C5CA-468A-AC2E-AF580CF03F2E}\\{27B51110-840 2-40F6-AD4D-7C85BC150CF0}
11/13/2013 15:26:25 [INFO] DeploymentManager - No of updates found (11).
11/13/2013 15:26:25 [INFO] DeploymentManager - STEP 2: Starting to launch media Bootstrapper.
11/13/2013 15:26:25 [INFO] DeploymentManager - Bootstrapper launch location is :: d:\32bit Adobe2\Build\Setup\Set-up.dat
11/13/2013 15:26:25 [INFO] Setup - Build Version - 6.0.335.0
11/13/2013 15:26:25 [INFO] Setup - Logging Level verbosity Set to 4
11/13/2013 15:26:25 [INFO] Setup - Start Adobe Setup
11/13/2013 15:26:25 [INFO] Setup - TimeLog: Bootstrapper Start
11/13/2013 15:26:25 [INFO] Setup - TimeLog: Start initial checks
11/13/2013 15:26:25 [INFO] Setup - Action specified - "install"
11/13/2013 15:26:25 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\resources\setup.xml
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] Setup - Found 6 packages in setup manifest
11/13/2013 15:26:25 [INFO] Utilities - Semaphore is not locked
11/13/2013 15:26:25 [INFO] PIM - Build Version - 6.0.335.0
11/13/2013 15:26:25 [INFO] PIM - Logging Level verbosity Set to 4
11/13/2013 15:26:25 [INFO] Utilities - File does not exist
11/13/2013 15:26:25 [INFO] Utilities - File does not exist
11/13/2013 15:26:25 [INFO] PIM - Build Version - 6.0.335.0
11/13/2013 15:26:25 [INFO] PIM - Logging Level verbosity Set to 4
11/13/2013 15:26:25 [INFO] PIM - CREATE PIM Instance ...
11/13/2013 15:26:25 [INFO] Utilities - File does not exist
11/13/2013 15:26:25 [INFO] Utilities - File does not exist
11/13/2013 15:26:25 [INFO] PIM - trying to createOrUpdatePIMDbSchema.
11/13/2013 15:26:25 [INFO] PIM - SUCCESS Created Tables.
11/13/2013 15:26:25 [INFO] PIM - PIM Database is Up To Date.
11/13/2013 15:26:25 [INFO] PIM - Updater Inventory location:d:\32bit Adobe2\Build\Setup\resources\updaterinventory.dll
11/13/2013 15:26:25 [INFO] PIM - Acquired System level ACF lock ...
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - pim_haveEnoughDiskSpaceToInstallPackages reqSize ... 104237697
11/13/2013 15:26:25 [INFO] Setup - TimeLog: End initial checks
11/13/2013 15:26:25 [INFO] Setup - TimeLog: Begin Installing
11/13/2013 15:26:25 [INFO] Setup - Start Installing core package - d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
11/13/2013 15:26:25 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
11/13/2013 15:26:25 [INFO] PIM - XML is valid
11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
11/13/2013 15:26:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx'
11/13/2013 15:26:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\core\PDApp.pima'
11/13/2013 15:26:26 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:26 [WARN] PIM - Failed to find Node
11/13/2013 15:26:26 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:29 [INFO] Utilities - File does not exist
11/13/2013 15:26:29 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx.
11/13/2013 15:26:29 [INFO] Setup - Finished Installing core package - d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx, Return status: 0
11/13/2013 15:26:29 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
11/13/2013 15:26:29 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
11/13/2013 15:26:29 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
11/13/2013 15:26:29 [INFO] PIM - XML is valid
11/13/2013 15:26:29 [WARN] PIM - Failed to find Node
11/13/2013 15:26:29 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx'
11/13/2013 15:26:29 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\D6\D6.pima'
11/13/2013 15:26:29 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:29 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:30 [INFO] Utilities - File does not exist
11/13/2013 15:26:31 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx.
11/13/2013 15:26:31 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
11/13/2013 15:26:31 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
11/13/2013 15:26:31 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
11/13/2013 15:26:31 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
11/13/2013 15:26:31 [INFO] PIM - XML is valid
11/13/2013 15:26:31 [WARN] PIM - Failed to find Node
11/13/2013 15:26:31 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx'
11/13/2013 15:26:31 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pima'
11/13/2013 15:26:31 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:31 [WARN] PIM - Failed to find Node
11/13/2013 15:26:31 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:33 [INFO] Utilities - File does not exist
11/13/2013 15:26:33 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx.
11/13/2013 15:26:33 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
11/13/2013 15:26:33 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
11/13/2013 15:26:33 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
11/13/2013 15:26:33 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
11/13/2013 15:26:33 [INFO] PIM - XML is valid
11/13/2013 15:26:33 [WARN] PIM - Failed to find Node
11/13/2013 15:26:33 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx'
11/13/2013 15:26:33 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pima'
11/13/2013 15:26:33 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:33 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:34 [INFO] Utilities - File does not exist
11/13/2013 15:26:34 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx.
11/13/2013 15:26:34 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
11/13/2013 15:26:34 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
11/13/2013 15:26:34 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
11/13/2013 15:26:34 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
11/13/2013 15:26:34 [INFO] PIM - XML is valid
11/13/2013 15:26:34 [WARN] PIM - Failed to find Node
11/13/2013 15:26:34 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx'
11/13/2013 15:26:34 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\P6\P6.pima'
11/13/2013 15:26:34 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:34 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:37 [INFO] Utilities - File does not exist
11/13/2013 15:26:37 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx.
11/13/2013 15:26:37 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
11/13/2013 15:26:37 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
11/13/2013 15:26:37 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
11/13/2013 15:26:37 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
11/13/2013 15:26:37 [INFO] PIM - XML is valid
11/13/2013 15:26:37 [WARN] PIM - Failed to find Node
11/13/2013 15:26:37 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx'
11/13/2013 15:26:37 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pima'
11/13/2013 15:26:37 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:37 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:39 [INFO] Utilities - File does not exist
11/13/2013 15:26:39 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx.
11/13/2013 15:26:39 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
11/13/2013 15:26:39 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
11/13/2013 15:26:39 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
11/13/2013 15:26:39 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
11/13/2013 15:26:40 [INFO] PIM - XML is valid
11/13/2013 15:26:40 [WARN] PIM - Failed to find Node
11/13/2013 15:26:40 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx'
11/13/2013 15:26:40 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pima'
11/13/2013 15:26:40 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:26:40 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:26:41 [INFO] Utilities - File does not exist
11/13/2013 15:26:42 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx.
11/13/2013 15:26:42 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
11/13/2013 15:26:42 [INFO] PIM - Processing ... _pimCreateOrUpdateAAMInventory
11/13/2013 15:26:42 [INFO] PIM - Return ... SUCCESS _pimCreateOrUpdateAAMInventory
11/13/2013 15:26:42 [INFO] Setup - TimeLog: End Installing. Now launching PDApp
11/13/2013 15:26:42 [INFO] Setup - Deployment File Path not specified in command line arguments. Skipping payload deployment part
11/13/2013 15:26:42 [INFO] Setup - ================= End Adobe Setup. Exit code: 0 =================
11/13/2013 15:26:42 [INFO] PIM - PIMSqlite closeDB status 0
11/13/2013 15:26:42 [INFO] PIM - FREE PIM Instance ...
11/13/2013 15:26:42 [INFO] DeploymentManager - Build Version - 3.1.105.0
11/13/2013 15:26:42 [INFO] DeploymentManager - Logging Level verbosity Set to 4
11/13/2013 15:26:42 [INFO] DeploymentManager - The return code from the Bootstrapper Process is (0).
11/13/2013 15:26:42 [INFO] DeploymentManager - STEP 3: Starting to launch ASU AAM.
11/13/2013 15:26:42 [INFO] DeploymentManager - Bootstrapper launch location is :: d:\32bit Adobe2\Build\ASU\Set-up.dat
11/13/2013 15:26:43 [INFO] Setup - Build Version - 6.2.136.0
11/13/2013 15:26:43 [INFO] Setup - Logging Level verbosity Set to 4
11/13/2013 15:26:43 [INFO] Setup - Start Adobe Setup
11/13/2013 15:26:43 [INFO] Setup - TimeLog: Bootstrapper Start
11/13/2013 15:26:43 [INFO] Setup - TimeLog: Start initial checks
11/13/2013 15:26:43 [INFO] Setup - Action specified - "install"
11/13/2013 15:26:43 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
11/13/2013 15:26:43 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\ASU\resources\setup.xml
11/13/2013 15:26:43 [INFO] PIM - XML is valid
11/13/2013 15:26:43 [WARN] PIM - Failed to find Node
11/13/2013 15:26:43 [INFO] Setup - Found 7 packages in setup manifest11/13/2013 15:27:08 [INFO] Utilities - Semaphore is not locked
11/13/2013 15:27:08 [INFO] PIM - Build Version - 6.2.136.0
11/13/2013 15:27:08 [INFO] PIM - Logging Level verbosity Set to 4
11/13/2013 15:27:08 [INFO] Utilities - File does not exist
11/13/2013 15:27:08 [INFO] Utilities - File does not exist
11/13/2013 15:27:08 [INFO] PIM - Build Version - 6.2.136.0
11/13/2013 15:27:08 [INFO] PIM - Logging Level verbosity Set to 4
11/13/2013 15:27:08 [INFO] PIM - CREATE PIM Instance ...
11/13/2013 15:27:08 [INFO] Utilities - File does not exist
11/13/2013 15:27:08 [INFO] PIM - trying to createOrUpdatePIMDbSchema.
11/13/2013 15:27:08 [INFO] PIM - Current db schema version on machine 1.
11/13/2013 15:27:08 [INFO] PIM - Current db schema version to install 1.
11/13/2013 15:27:08 [INFO] PIM - PIM DB Schema is up to date. Current schema version is 1.
11/13/2013 15:27:08 [INFO] PIM - PIM Database is Up To Date.
11/13/2013 15:27:08 [INFO] PIM - Updater Inventory location:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\resources\updaterinventory.dll
11/13/2013 15:27:08 [INFO] PIM - Acquired System level ACF lock ...
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id 5AA1D762-31AF-4FC3-A0C0-66BF663B2117 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id 54FD72DC-72EC-4CDC-8828-F07C4E9E6FA2 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id 6D2A548B-C50D-46BA-B83E-C8199C6A9406 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id 99477136-88AD-496B-9551-BAE72699A32C is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id FAFC744B-DDFB-4097-A41D-7E9539FEBAF9 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id B322281B-C04F-438E-82D7-7DA34A359526 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id B1313DE3-08DF-4834-91D9-CBD1A91488E5 is already installed
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\CCM\CCM.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Package id F0158AAB-0779-4B40-A07D-3F2A21D47E74 is already installed
11/13/2013 15:27:08 [INFO] PIM - pim_haveEnoughDiskSpaceToInstallPackages reqSize ... 29928536
11/13/2013 15:27:08 [INFO] Setup - TimeLog: End initial checks
11/13/2013 15:27:08 [INFO] Setup - TimeLog: Begin Installing
11/13/2013 15:27:08 [INFO] Setup - Start Installing core package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
11/13/2013 15:27:08 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
11/13/2013 15:27:08 [INFO] PIM - XML is valid
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx'
11/13/2013 15:27:08 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pima'
11/13/2013 15:27:08 [INFO] PIM - Package id 5AA1D762-31AF-4FC3-A0C0-66BF663B2117 is already installed
11/13/2013 15:27:08 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:08 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:08 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:08 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
11/13/2013 15:27:08 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:08 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:12 [INFO] Utilities - File does not exist
11/13/2013 15:27:12 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx.
11/13/2013 15:27:13 [INFO] Setup - Finished Installing core package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx, Return status: 0
11/13/2013 15:27:13 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
11/13/2013 15:27:13 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
11/13/2013 15:27:13 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
11/13/2013 15:27:13 [INFO] PIM - XML is valid
11/13/2013 15:27:13 [WARN] PIM - Failed to find Node
11/13/2013 15:27:13 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx'
11/13/2013 15:27:13 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pima'
11/13/2013 15:27:13 [INFO] PIM - Package id 54FD72DC-72EC-4CDC-8828-F07C4E9E6FA2 is already installed
11/13/2013 15:27:13 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:13 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:13 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:13 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:13 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:13 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:13 [INFO] Utilities - File does not exist
11/13/2013 15:27:14 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx.
11/13/2013 15:27:14 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
11/13/2013 15:27:14 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
11/13/2013 15:27:14 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
11/13/2013 15:27:14 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
11/13/2013 15:27:14 [INFO] PIM - XML is valid
11/13/2013 15:27:14 [WARN] PIM - Failed to find Node
11/13/2013 15:27:14 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx'
11/13/2013 15:27:14 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pima'
11/13/2013 15:27:14 [INFO] PIM - Package id 6D2A548B-C50D-46BA-B83E-C8199C6A9406 is already installed
11/13/2013 15:27:14 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:14 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:14 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:14 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:14 [WARN] PIM - Failed to find Node
11/13/2013 15:27:14 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:14 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:16 [INFO] Utilities - File does not exist
11/13/2013 15:27:17 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx.
11/13/2013 15:27:17 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
11/13/2013 15:27:17 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
11/13/2013 15:27:17 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
11/13/2013 15:27:17 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
11/13/2013 15:27:17 [INFO] PIM - XML is valid
11/13/2013 15:27:17 [WARN] PIM - Failed to find Node
11/13/2013 15:27:17 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx'
11/13/2013 15:27:17 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pima'
11/13/2013 15:27:17 [INFO] PIM - Package id 99477136-88AD-496B-9551-BAE72699A32C is already installed
11/13/2013 15:27:17 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:17 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:17 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:17 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:17 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:17 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:18 [INFO] Utilities - File does not exist
11/13/2013 15:27:19 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx.
11/13/2013 15:27:19 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
11/13/2013 15:27:19 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
11/13/2013 15:27:19 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
11/13/2013 15:27:19 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
11/13/2013 15:27:19 [INFO] PIM - XML is valid
11/13/2013 15:27:19 [WARN] PIM - Failed to find Node
11/13/2013 15:27:19 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx'
11/13/2013 15:27:19 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pima'
11/13/2013 15:27:19 [INFO] PIM - Package id FAFC744B-DDFB-4097-A41D-7E9539FEBAF9 is already installed
11/13/2013 15:27:19 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:19 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:19 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:19 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:19 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:19 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:21 [INFO] Utilities - File does not exist
11/13/2013 15:27:22 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx.
11/13/2013 15:27:22 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
11/13/2013 15:27:22 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
11/13/2013 15:27:22 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
11/13/2013 15:27:22 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
11/13/2013 15:27:22 [INFO] PIM - XML is valid
11/13/2013 15:27:22 [WARN] PIM - Failed to find Node
11/13/2013 15:27:22 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx'
11/13/2013 15:27:22 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pima'
11/13/2013 15:27:22 [INFO] PIM - Package id B322281B-C04F-438E-82D7-7DA34A359526 is already installed
11/13/2013 15:27:22 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:22 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:22 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:22 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:22 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:22 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:24 [INFO] Utilities - File does not exist
11/13/2013 15:27:25 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx.
11/13/2013 15:27:25 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
11/13/2013 15:27:25 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
11/13/2013 15:27:25 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
11/13/2013 15:27:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
11/13/2013 15:27:25 [INFO] PIM - XML is valid
11/13/2013 15:27:25 [WARN] PIM - Failed to find Node
11/13/2013 15:27:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx'
11/13/2013 15:27:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pima'
11/13/2013 15:27:25 [INFO] PIM - Package id B1313DE3-08DF-4834-91D9-CBD1A91488E5 is already installed
11/13/2013 15:27:25 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
11/13/2013 15:27:25 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
11/13/2013 15:27:25 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
11/13/2013 15:27:25 [INFO] PIM - SUCCESS insertPackageUpdateList.
11/13/2013 15:27:25 [INFO] PIM - SUCCESS insertAppletRegInfoList.
11/13/2013 15:27:25 [INFO] PIM - Backup Folder Created
11/13/2013 15:27:27 [INFO] Utilities - File does not exist
11/13/2013 15:27:27 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7 -
Error configuring and starting Managed Server in WebLogic 10.3
Hi,
I am able to configure and start the Managed Server on windows environment. I am trying to configure Managed Server on linux environment. I am configuring the Managed Server with custom keystore. When I configured the Managed Server I specified the keystore/trustsote information in the Keystores tab of the Admin Console for Managed Server settings. Specified Private Key Alias, Password in SSL tab.But when I am starting the Managed Server from command line, I see the process looking for demo trust files and failing.
Here is the command I run to start the Managed Server:
./startManagedWebLogic.sh MyManagedServer1 https://localhost.localdomain:8443
Below is the console output:
<Mar 11, 2015 12:37:44 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
<Mar 11, 2015 12:37:45 PM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:beaadmin
Enter password to boot WebLogic server:
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks.>
<Mar 11, 2015 12:37:53 PM PDT> <Error> <Security> <BEA-090132> <Could not open the keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks for read access. Exception: java.io.FileNotFoundException: /opt/wlserver_10.3/server/lib/DemoTrust.jks (No such file or directory)>
<Mar 11, 2015 12:37:53 PM PDT> <Warning> <Security> <BEA-090164> <Failed to load trusted certificates from keystore /opt/wlserver_10.3/server/lib/DemoTrust.jks of type jks>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jre1.6.0_45/lib/security/cacerts.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at https://localhost.localdomain:8443.>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320400> <The log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log00015. Log messages will continue to be logged in /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log is opened. All server side log events will be written to this file.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090837]The configured keystore location for the PKI Credential Mapper is either null or empty.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090815]The password provided for the keystore configured for the PKICredential Mapper was null.>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <Security> <BEA-090403> <Authentication for user beaadmin denied>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User beaadmin weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 11, 2015 12:37:57 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Why is it looking for demotrust.jks file to start the Managed Server. We don't use the demo trust and cannot copy to the location it is referring to. I followed the solution provided at the below link:
http://serverfault.com/questions/106499/custom-trust-and-custom-identity-keystore-in-weblogic-10-3
There are 2 options given in the link. To update the boot.properties of the Admin Server and appending JAVA_OPTIONS to DomainEnv file. Both of these caused the failure of Admin Server. I couldn't bring up the server after these changes.I also came across posts talking about boot.properties for Managed Server. I don't see the security folder that has boot.properties for my Managed Server (verified it on both windows and linux boxes).
Thanks in advance.
-nn.Hi Faisal,
Here is the config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd"
xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security"
xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<name>JCRMDomain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml">
<name>JCRMDomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType">
<sec:control-flag>SUFFICIENT</sec:control-flag>
</sec:authentication-provider>
<sec:authentication-provider xmlns:ext="http://xmlns.oracle.com/weblogic/security/extension" xsi:type="ext:jcrm-authenticatorType">
<sec:name>JcrmAuthenticator</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:credential-mapper xsi:type="wls:pki-credential-mapperType">
<sec:name>PKICredentialMapper</sec:name>
</sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:user-lockout-manager>
<sec:lockout-threshold>3</sec:lockout-threshold>
<sec:lockout-duration>15</sec:lockout-duration>
<sec:lockout-reset-duration>99999</sec:lockout-reset-duration>
</sec:user-lockout-manager>
<sec:deploy-role-ignored>false</sec:deploy-role-ignored>
<sec:deploy-policy-ignored>false</sec:deploy-policy-ignored>
<sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
<sec:security-dd-model>DDOnly</sec:security-dd-model>
<sec:combined-role-mapping-enabled>true</sec:combined-role-mapping-enabled>
<sec:name>myrealm</sec:name>
<sec:delegate-m-bean-authorization>false</sec:delegate-m-bean-authorization>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator"
xsi:type="pas:system-password-validatorType">
<sec:name>JCRMPasswordValidator</sec:name>
<pas:max-password-length>31</pas:max-password-length>
<pas:min-password-length>15</pas:min-password-length>
<pas:min-numeric-characters>2</pas:min-numeric-characters>
<pas:min-lowercase-characters>2</pas:min-lowercase-characters>
<pas:min-uppercase-characters>2</pas:min-uppercase-characters>
<pas:min-non-alphanumeric-characters>2</pas:min-non-alphanumeric-characters>
</sec:password-validator>
<sec:deployable-provider-synchronization-enabled>false</sec:deployable-provider-synchronization-enabled>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}cpwhv2peqwl0Z8Ma1Jk7KlmC6d1gtCAqxnzrmR5ssybHpM9AUzbBRJ7rE7m4/7U16IHgsTMkcOr/5/abZJ4NeuHR45jdDK1EjFmnUuPssISmGkan3EIpCKHmPPIynVxh</credential-encrypted>
<node-manager-username>wdUXiuwL5A</node-manager-username>
<node-manager-password-encrypted>{AES}UDiZjaLOrm0y+/I9noQVURudpzmRKMBOQR2B8ofNIt8=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<max-http-message-size>10000000</max-http-message-size>
<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<client-certificate-enforced>false</client-certificate-enforced>
<listen-port>8443</listen-port>
<two-way-ssl-enabled>true</two-way-ssl-enabled>
<server-private-key-alias>localhost.localdomain</server-private-key-alias>
<server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>true</use-server-certs>
<jsse-enabled>true</jsse-enabled>
</ssl>
<listen-port-enabled>false</listen-port-enabled>
<web-server>
<keep-alive-secs>60</keep-alive-secs>
<https-keep-alive-secs>60</https-keep-alive-secs>
</web-server>
<listen-address/>
<java-compiler>javac</java-compiler>
<tunneling-enabled>true</tunneling-enabled>
<tunneling-client-ping-secs>45</tunneling-client-ping-secs>
<tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
<key-stores>CustomIdentityAndCustomTrust</key-stores>
<custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
<custom-identity-key-store-type>JKS</custom-identity-key-store-type>
<custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
<custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
<custom-trust-key-store-type>JKS</custom-trust-key-store-type>
<custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
<overload-protection>
<panic-action>system-exit</panic-action>
<failure-action>force-shutdown</failure-action>
<server-failure-trigger>
<max-stuck-thread-time>600</max-stuck-thread-time>
<stuck-thread-count>3</stuck-thread-count>
</server-failure-trigger>
</overload-protection>
</server>
<server>
<name>MyManagedServer1</name>
<ssl>
<enabled>true</enabled>
<listen-port>8445</listen-port>
<server-private-key-alias>localhost.localdomain</server-private-key-alias>
<server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
</ssl>
<machine xsi:nil="true"></machine>
<listen-port>8444</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<key-stores>CustomIdentityAndCustomTrust</key-stores>
<custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
<custom-identity-key-store-type>JKS</custom-identity-key-store-type>
<custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
<custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
<custom-trust-key-store-type>JKS</custom-trust-key-store-type>
<custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
<data-source>
<rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
</data-source>
</server>
<production-mode-enabled>false</production-mode-enabled>
<embedded-ldap>
<name>JCRMDomain</name>
<credential-encrypted>{AES}LNAnq4qCQQmy9rCOMN+uIZVPq1bVvPrwQqqtOScZrnYmwESt9aruHNVy4IjqMWz7</credential-encrypted>
</embedded-ldap>
<administration-port-enabled>true</administration-port-enabled>
<configuration-version>10.3.4.0</configuration-version>
<admin-server-name>AdminServer</admin-server-name>
</domain>
It has 'CustomIdentityAndCustomTrust' for both Admin Server as well as managed Server in it.
Thanks,
nn -
Queries related to calibration inspection process
I have some queries related to calibration business process.They are as follows:-
1.Which equipment category do we choose, Q or P?
2.While creating a maintenance plan,which category do we choose, maintenance order or quality maintenance order?
3.Is it that we can't do a time confirmation before results recording?If I try to do so,I get this message"No open operation recieving confirmation entries for order".
4.While I create my maintenance plan,I get this message, a counter could not be defined for the reference object.Why so?
5.After usage decision,if I lock my equipment for further use,the equipment has the status both AVLB and NPRT.Why?
6.Can I create my calibration order manually and assign equipment task list.If so,how?
7.While creating my test equipment,for the PRT tab,the task list usage becomes a mandatory field.What setting is done for this task list usage to become a mandatory field?
Edited by: Pallavi Kakoti on Feb 2, 2012 8:19 AMHi
1.Which equipment category do we choose, Q or P?
Ans:
Q is normaly used for Instruments,Lab equipments
P also used for Production/process related equipments needs calibrations often
2.While creating a maintenance plan,which category do we choose, maintenance order or quality maintenance order?
Ans:
Its all depends on config you have did. if Quality maintenance order should be linked to inspection type.can be used.
we can not used maintenance order if it is not linked to inspection type 14.
3.Is it that we can't do a time confirmation before results recording?If I try to do so,I get this message"No open operation recieving confirmation entries for order".
Ans:
You can do time confirmation after result recording, then UD.after UD ,order will be TECOed automaticlay.
4.While I create my maintenance plan,I get this message, a counter could not be defined for the reference object.Why so?
Ans:
Check any measuring counters created for the equipments,
5.After usage decision,if I lock my equipment for further use,the equipment has the status both AVLB and NPRT.Why?
Ans:
After UD, system changes the status NPRT for the equipments have PRT view only.
if PRT view maintained in the equipment, system status remains AVLB.
If you dont to use the equipment after UD-Reject,have to go development using user status.
6.Can I create my calibration order manually and assign equipment task list.If so,how?
Ans:
Yes. you can
Create task list with 300 inspection point, assign when u create order
also you can have manual call in the maintenance plans. -
Objective setting appraisal (OSA) queries related to ESS/MSS
Hello All,
I am currently working in OSA. I have few queries related to this.
My client wants to implement OSA without linking it to the SAP ESS/MSS. They have their own intranet portal which is not a part of SAP. But they are using it for applying leave etc which has been linked to SAP R/3. So they also want to use the the same portal for appraisal also.
Hence my query is whether is it possible to link OSA with their own inhouse intranet portal ? And if it is possible then how and will I be able to get all those functionalites which are available in standard ESS/MSS for OSA?
Please guide.
Regards,
DanielHi Daniel
If you can call SAP Portal in your local intrenet.
In one of my clients they were using MOSS as thier frame work (SAP portal is called inside moss)
Thanks
Rajdeep
Maybe you are looking for
-
Hi Gurus, I want to know about SAP Insurance Certification course
Hi Gurus, I want to know about SAP Insurance Certification course. Can anyone guide me how to proceed. Regards Raghu
-
Managing more than one UPS with Lion
I have one APC UPS on my iMac, but I really need a second, will the Lion Power utility work with two both connected by USB?
-
Illustrator CC | Swatches -- Other Library
Hi there, I have problem with my Adobe Illustrator CC. I want to import swatches from InDesign. I have exported .ase file but when I click on Swatches --> Other Library ... nothing's happened. No reaction from Illustrator. I tried to uninstall Illust
-
User Groups and non Developers users
Hi, two questions. 1) How do I create users groups. I want to divide specific users to specific groups. 2) I created users not as developer and not as a administrator. When I logged on with that users I didnt see any of the applications, why? Thanx.
-
Does Anyone anywhere publish an operators manual for Premier Elements?
Yes, I can make a movie, it will play on my computer, on my DVD players, X - BOX, etc. The problem is that results are not consistent. I do not understand why the program does whatever it does. The program is totally undocumented. Tutorials seem