Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Aliases - Confussed...Creation...Shares

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Aliases - Confussed...Creation...Shares

    Hi Guys...

    I'm very confused by Aliases and I'm over thinking it...I think. I understand their use but the setup has me lost. BTW...I'm trying to create a web app but it only works locally.

    The examples I've read either point to a local file C:\mydata or UNC \\server\mydata

    If the data is local to the Application server I would think you would only specify the local path for the data folder. ex. D:\mydata or in my case D:\alpha data\arcapp

    When and why would I ever want to use a UNC? Why would I expose those data files to the users on the network? If it has to be a UNC then what is the minimum share and folder level permissions needed? Yes, I could encrypt the data files but why even let the users know what is out there.

    Joe
    Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

    #2
    Re: Aliases - Confussed...Creation...Shares

    Correct, you only need a UNC if your data is on the network, but not on the server that hosts your pages, like //otherserver/share/path

    Also, if you are INSIDE of your firewall and want to run the web app, your Alias can be a normal path or UNC, but the URL to get to your web app would take the form of the UNC. (That is, http://www.domain.com... would not work from inside the firewall).
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Aliases - Confussed...Creation...Shares

      Due to security concerns it may at times be advisable to store data on a machine separate from the application hosting machine. The data would only be "exposed" the network users if your network was configured to allowed it. You protect the data by segmenting the network, share permissions and NTFS permissions.

      For minimum share and folder level permissions this would depend on what you need to do with the data. In cases like these there are no good answers that can be given without knowing the full scope of the application.

      I do not run the AppServer I only work in the desktop side. My theory is that all data access across the UNC will be done with the credentials of the account running the App Server process. You can determine the account name by looking at the User Name column of Task Manager for the App Server process.

      To determine minimum access first remove all share level access and all of the NTFS level access to the data. Both lists will be empty at this point. Next using the built in Windows functions enable auditing for data access, both success and failure. http://support.microsoft.com/kb/310399. Then run your application, of course your app will generate errors on data access. Now is also a good time to code traps for the errors, in case your network goes offline during normal production times. Scan your security logs for the audit entries, then granularly give permissions to the accounts that are shown in the audit logs. Ideally the only account that needs access will be the account running the App server. Retest your app and rescan the logs until you no longer get access failures from the normal operation of the application.

      Once your done the only accounts listed in the share permissions and the NTFS permissions are the ones needing access, all other accounts listings are removed. To backup data, make sure the account that is running your backups is a member of the backup operators group.

      It is possible to use a URL like www.somedomain.com and have it point to an internal machine. This can be with an internal DNS server. You should not use not use an external DNS server to resolve an internal hostname.
      Andrew

      Comment


        #4
        Re: Aliases - Confussed...Creation...Shares

        Thanks for the thorough replies. If only the App Server is connecting to the data then this is pretty easy to lock down. I can easily move the data to my HP/Lefthand SAN which is on its own V-Lan. I wasn't sure if it needs to be a network share for it to work within the browser. I've never developed anything before so sometimes reading, doing, and what I know add up to a lot of questions.

        Thx.
        Joe
        Never take a ride to the edge of your mind unless you've got a ticket back - Jon Oliva - Savatage.

        Comment

        Working...
        X