Take a look at the DM Server documentation. There are some settings regarding queues and one in particular, DMSERVER/SOAP/ CONNS_BACKLOG, that may help you manage an overloaded server. Also ensure you have all DM Server patches installed.   There are also ways to streamline the footprint of your services. Many nodes have memory settings for example and optimizing these settings may help you shrink services so that they are not so resource intensive. Ron ... View more

Hi Chetan -    This behavior may indicate that the resources available to the server processing the services is not adequately sized to handle the load when all 30 services are engaged. You could try turning off queuing on DM Server, but then the calling applications would have to deal with real-time services that were denied a slot for processing on DM Server (the calling app would have to retry failed service calls).   Take a look at your memory utilization when all 30 real-time services are engaged, this is usually a good indicator of whether DM Server is OK with resources.   Ron ... View more

For a quick demo of this functionality, check out this short video. It is true that the Clustering Update node is no longer in Data Management Studio. However, the Clustering node provides the same capabilities. In fact, the two nodes were nearly identical, which is why the Clustering Update node was deprecated. In both nodes you are required to run the same clustering rules in both the first and subsequent data processes. You are also required to append any new data you want to cluster to the end of the original data that had already been processed. Both need to reprocess the combined existing and added data at the same time. Using the Clustering node in newer versions of Data Management Studio will provide the same functionality as the deprecated node. You only need to make minor adjustments to the data job to accommodate the different node. You will still get repeatable cluster identifiers on subsequent runs of the job if the data input and the configuration parameters stay the same. Added data will receive new cluster identifiers or will be merged into existing clusters if the clustering criteria dictates. ... View more

Sometimes errors in the clustering steps are related to the process running out of memory. Does the job run to completion on a smaller test set of rows? If so, you can try to allocate more memory to the node in the node's advanced settings. This could also point to something in the data (like a control character) causing problems too.   If a smaller set of data doesn't remove the error, you might selectively remove clustering rules to see if one in particular is causing problems. This shouldn't be a problem so if you find this is the case, I suggest you initiate a technical support track.   Ron ... View more

It would be interesting to know, when you look at the repository database tables across each environment, if the "jobcode" associated with the task in the originating system remains the same after export then import to subsequent systems, or if it changes when imported to the business rules repository for the UAT system. I believe that's how the job node knows what business rule to reference.   Ron ... View more

Hi -    The XML Writer transformation does not have the ability to transform data as part of the transformation itself. You will need to read the XML file in through a DI Studio job (XML libname engine), write some transformation code to change the values, then use the XML Table Writer to output the XML file.    More information about the XML Writer transformation can be found here.   Ron ... View more

The Data Management Servers do not always start automatically. Sometimes there is a timing issue and they attempt to start but fail when the metadata server is not running. Double-check in SAS Metadata Console that your DM Server configuration is pointing to the right metadata server and then try to manually restart DM Server. Look in the DM Server directory structure to find the log that might give you more information.   Two common things that prevent DM Server from starting is that it can't connect to a metadata server or something is misconfigured, like pointing to a nonexistent log file location.   Ron ... View more

I'm going to assume that when you run the job interactively it works OK. Have you considered looking at what username is being used to run from the command line? It could be that one or more directories used or referenced by the job are available to the user running interactively but not to the user whose credentials are being used for the batch call.   Ron ... View more

If the "clear user saved credentials" option does not seem to be working in Data Management Studio, double-check that you have the correct permissions to update the files that stores the encoded credentials.I believe the location will be something like this for the files:    C:\Program Files\SASHome\DataFluxDataManagementStudio\2.7\etc\dsn   or   C:\Users\[your username]\AppData\Roaming\DataFlux\dac\savedconn ... View more

I can't say for sure if changing the value in the ES_ID column will crash anything but modifying values directly in the repository database is not something that is supported. Without getting too far into the details of the schema design, it could be that some table relationships needed by Data Management applications or functions will be broken if you make this change.   There is an option in Data Management Studio to delete items from the repository. You could try to use this first and the rerun your process with the intended values.   Ron ... View more