on 11-08-2012 5:36 PM
Hi,
When I MBO package developed for HWC application is deployed in a domain other than "default" in the SCC and run the application it is showing an error"Package is missing".
Why the package deployed in other than "default" domains not working?
Thanks
Midhun
Hi Midhun,
We ran into the same issue as well and had a hard time figuring it out. The workflow app has trouble finding the MBO when you don't specify which domain it's in. You have to deploy the workflow app in the domain where the package (MBO) is located. Here is the solution:
1) Deploy the MBO to your new domain (other than default) successfully.
2) Before you deploy the workflow to the SUP server, you need to specify which domain you would like to deploy to:
In the Unwired Workspace, open your workflow to the "Flow Design" screen and click on the "Properties" tab. Next, click the "Authentication" tab and scroll down to the bottom. Here you will see a field for "Unwired Server Domain". Enter the domain you would like to deploy to. Now re-deploy the workflow.
This should solve your "Package not found" error.
Jerad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there,
Quick question for you: in looking forward to revising documentation in a future version (to try avoid similar situations going forward), where would you expect to see this recommendation in the doc set.
Would you mind providing your opinion? Please let me know:
- The version you are using
- If you looked at the docs to find the answer.
- Would you isolate to development documentation or administration or both (and why)
- The document title(s) you would look in
- A title of a topic that you feel gives high visibility (and why)
Cheers,
Annette
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Annette,
We are using SUP 2.1.3. We tried looking in the docs to find the answer to this question but ended up contacting SAP (Sybase) directly for an answer. I'm not sure the solution is located anywhere in the Infobooks documentation. I think this issue is important to both administrators (to troubleshoot) and developers (to understand the concept and avoid the issue altogether).
I could definitely see this being incorporated into the Administrator Workbook for Multitenancy setup (even though this documentation is faulty as well, because the Domain Administrator role is essentially useless at this point). It's confusing because all workflows get deployed to the same folder on the SCC, but behind the scenes you have to specify the domain you want to deploy the worflow to. I think a troubleshooting document for the "Package not found" error would also be a good place to look for an answer.
If we had separate workflow directories for each domain, then we would avoid this problem altogether.
Hope that helps.
Jerad
Thanks Jerad. I'm seeing this as a pattern and think it absolutely needs to be addressed more prominently. I tend to agree that you would want to have a different domain other than default. From what I understand (in limited capacity) it is important for keeping admin authentication separate from your application users. In 2.2 we have introduced a Mobile Applications Life Cycle document and think that mentioning this in with the deployment docs there might increase the visibilty. Research shows that the Workbook is not referenced very often, so think between package deployment docs for developers, SCC online help and the new doc, we might get some traction.
Avoiding the issue altogether is what we're all after. Thanks for your feedback. Please feel free to add comments to the documentation on Infocenter via Doc Comment Exchange (link is at bottom of the topic). We respond to all feedback we get.
Cheers,
Annette.
Annette,
It is not available http://infocenter.sybase.com/help/index.jsp
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.