- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I have 100's of SAS Flows which I have done a manual metadata export and import including Jobs and Deployed jobs. Everything has been migrated successfully BUT only few flows came over to the new environment with the previously scheduled(in old environment) options, I mean no clock symbol on the flows in the new environment.
while others are migrated with out a schedule [No clock symbol on them]
1. Is there any options I need to consider to get all flows as-is (including schedule)
2. How to migrate LSF schedule files from /lsf/pm/work/storage/flow_storage? - I know when I manually schedule the flow these files will be created, but I have 100's of users and all the flows has been scheduled by them and we dont want to ask everyone to do this for every flow in new envi.
3. If I move lsf flow files to new environment and Metadata flows (with or without schedule, clock symbol) will these flows start as per the schedule?.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
And you are saying a few flows migrated successfully with a correct time event, but the rest is missing that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi there,
the process you are looking for should be similar to:
- copy migrate all lsf/ps calendars, then the schedules & flows (they may require some modifications, regarding uids and such, give it a look) - this can be automated or semi-automated
- ensure the groups and authentication domains are in place, with all the metadata permissions as expected
- migrate SAS metadata - this is automated
- Then re-deploy & re-schedule the flows - it is possible to automate this via scripts using the platform framework (and you will need the passwords of the users, so careful), but probably it will take you less overall time to do this manually, each user, and more in control. When you re-schedule the flows, the flows should have picked up the right calendar/schedule, or at least they will be in the list in SMC.
I hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
@JuanS_OCS : Do you mean I have to manually redeploy and reschedule the flows in SMC after metadata migration?. If so , does it have to be done by individual users for their flows OR is it ok if I do using sasadm/lsfadmin user?. Idea is to minimize tasks/impact to users.
After migrating calendars , flows in LSF storage location (Linux) and SAS metadata I can see all flows in Platform Process Manager BUT I dont see the time event on the flow ICON , does this mean the migrated flows will start automatically as per the previously scheduled event?.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
@Key123 : yes, I mean that you can redeploy and reschedule manually (that would be my approach) in SMC after the metadata migration (which you can automate with the SAS Platform Object Framework).
While it is possible to reschedule with any metadata account for as long as the Outbound login has the right permissions in LSF, the OS folders and the metadata user has the right permissions over the metadata you could potentially use any account to redeploy the jobs, and to schedule them.
However, you are going to need to look into the implications of using an elevated account, and to ensure that the scheduled jobs will use the right credentials for the execution, file ownership, connection to databases, etc. That is for you to evaluate and decide.
This being said, I do not know how your users schedule and deploy jobs and flows (it depends on the design), which what user, if there is a common user for them, etc etc.
I say this because Batch Jobs are supposed to be controlled workflows. All what is controlled, there should be just one or a limit amount of privileged accounts to deploy and schedule, in the end. However, if your users are using Batch as self service, that is a different story, and, indeed, the implications on security vs investment of work are much different.
Let me add: in the communities there is a limit as to how much we can help you without knowing details on design and security of your environment. When they get complicated, I would encourage you then to reach out to SAS Professional Services or a trusted SAS Partner, specialised on this area.