Setup Node manager as NT Service is easy, just run that cmd under WL_HOME\server\bin\installNodeMgrSvc.cmd.

Service created successfully, no errors, start/stop smoothly.

The problem popped up when doing Admin server and Managed server.

Error: the input line is too long.

This is typical JAVA CLASSPATH exceed DOS/WIN environment size limit issue.

The number of characters that can be entered into a single command is limited to 8191. (this is including spaces).

In detail, The error occurs when setting EXTRA_JAVA_PROPERTIES in call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

Try to ignore those lines:
set EXTRA_JAVA_PROPERTIES=-Doracle.apm.home=%APM_ORACLE_HOME% -DAPM_HELP_FILENAME=oesohwconfig.xml %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -DXL.HomeDir=%OIM_ORACLE_HOME%\server -Dscheduler.disabled=false -Djava.security.auth.login.config=%OIM_ORACLE_HOME%\server\config\authwl.conf -Dorg.owasp.esapi.resources=%OIM_ORACLE_HOME%\server\apps\oim.ear\APP-INF\classes -DeditionOverride=ee %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% -Djava.awt.headless=true %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doracle.oaam.home=%OAAM_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES= -Doam.oes.new=true -DOAM_POLICY_FILE=%DOMAIN_HOME%\config\fmwconfig\oam-policy.xml -DOAM_CONFIG_FILE=%DOMAIN_HOME%\config\fmwconfig\oam-config.xml -DOAM_ORACLE_HOME=%OAM_ORACLE_HOME% -Doracle.security.am.SERVER_INSTNCE_NAME=%SERVER_NAME% -Does.jars.home=%OAM_ORACLE_HOME%\server\lib\oes-d8 -Does.integration.path=%OAM_ORACLE_HOME%\server\lib\oeslib\oes-integration.jar -Does.enabled=true -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConnectionFactoryImpl -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djavax.xml.soap.SOAPFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=C:\app\oracle\Middleware_IAM\oracle_common -Djava.awt.headless=true
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dbpm.enabled=true
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dsoa.archives.dir=%SOA_ORACLE_HOME%\soa -Dsoa.oracle.home=%SOA_ORACLE_HOME% -Dsoa.instance.home=%DOMAIN_HOME% -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=%WL_HOME%\server\lib\DemoTrust.jks
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dums.oracle.home=%UMS_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dcommon.components.home=%COMMON_COMPONENTS_HOME% -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=%DOMAIN_HOME% -Djrockit.optfile=%COMMON_COMPONENTS_HOME%\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=%ORACLE_DOMAIN_CONFIG_DIR%\servers\%SERVER_NAME% -Doracle.domain.config.dir=%ORACLE_DOMAIN_CONFIG_DIR% -Digf.arisidbeans.carmlloc=%ORACLE_DOMAIN_CONFIG_DIR%\carml -Digf.arisidstack.home=%ORACLE_DOMAIN_CONFIG_DIR%\arisidprovider -Doracle.security.jps.config=%DOMAIN_HOME%\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=%DOMAIN_HOME%\servers\%SERVER_NAME%\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=%ALT_TYPES_DIR% -Djava.protocol.handler.pkgs=%PROTOCOL_HANDLERS% %WLS_JDBC_REMOTE_ENABLED% %EXTRA_JAVA_PROPERTIES%
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %EXTRA_JAVA_PROPERTIES%

When service created and start, got an error ‘ Unable to initialize the Java virtual machine!’

This EXTRA_JAVA_PROPERTIES seems is critical for JAVA process. Giving up.

I think for now I have to keep IAM desktop never always in login status.

A helpful trick, beasvc -remove command doesn’t work. Had to run sc delete instead.

There are many plugin around, the most of them require some medium level PHP skill to change template or theme.

Some cool plugins like Custom Post type UI, just custom post type and advanced custom type. But those plugin still have one problem to solve, how to make the input UI easier to use. One common problem is in the input screen, custom field displayed twice, and still give user flexibility to add other custom fields.

Custom field template suppose fix it, but it seems still need PHP code change somewhere.

Magic fields 2 solved this problem eventual, by introducing some style middle tables at backend, the admin UI looks much cleaner. And data storage is still in post_metadata.

rm .gitmodules, or edit it to remove the selected submodule.

Remove the submodule’s entry in the .git/config

git rm –cached external/selected-submodule

git add external/selected-submodule

git commit -m

git push

Credit: http://chrisjean.com/2009/04/20/git-submodules-adding-using-removing-and-updating/

http://adcdownload.apple.com//wwdc_2012/wwdc_2012_session_pdfs/session_304__events_and_reminders_in_event_kit.pdf

Install SDK

Drag framework folder into XCode project.

Drag bundle into XCode project.

Drag deprecated header folder into XCode project. check copy in needed.

When picking dependency libraries, set them to optional, to allow app running on iOS5.

Set other link flag to -lsqlite3.0

Those steps are fully documented on facebook developer site: https://developers.facebook.com/docs/getting-started/facebook-sdk-for-ios/3.1/

Note: we are using old fashion Facebook sharing feature in app.  (FBDelegate vs. FBRequest) Because my client doesn’t like posting story on their wall without a preview. This way app will popup a separated window to display link to share, image, title, description, etc. User needs to type something in the textbox with placeholder ‘say something about this…’

Note: again, preset message feature has been disabled by Facebook as of 2012.

In app, we are adding #include “Facebook.h” to implement this.

Note: you can use sharekit library for this, but I want to figure out what’s happening behind the scene.

In the place you want to popup Facebook share options to user, do this to open a Facebook session.

// openSessionWithAllowLoginUI will be called by the actual sharing screen where users can click button to post message on their wall.
- (BOOL)openSessionWithAllowLoginUI:(BOOL)allowLoginUI
{
    NSArray *permission = [[NSArray alloc] initWithObjects:@"user_likes",@"publish_actions", nil];

    return [FBSession openActiveSessionWithPublishPermissions:permission
                                              defaultAudience:FBSessionDefaultAudienceFriends
 allowLoginUI:allowLoginUI
                                            completionHandler:^(FBSession *session, FBSessionState status, NSError *error) {
                                                [self sessionStateChanged:session state:status error:error];
                                            }];}

NSString *const FBSessionStateChangedNotification = @"com.bitrixsoft.Login:FBSessionStateChangedNotifiction";

- (void)sessionStateChanged:(FBSession *)session
                    state:(FBSessionState) state
                    error:(NSError *)error
{
    switch (state) {
        case FBSessionStateOpen:
            if (!error) {
                NSLog(@"User session found");
            }
            break;
        case FBSessionStateClosed:
        case FBSessionStateClosedLoginFailed:
            [FBSession.activeSession closeAndClearTokenInformation];
        default:
            break;
    }

    [[NSNotificationCenter defaultCenter]
     postNotificationName:FBSessionStateChangedNotification
     object:session];

    if (error) {
        [[[UIAlertView alloc]
         initWithTitle:@"Error"
         message:error.localizedDescription
         delegate:nil
         cancelButtonTitle:@"OK"
          otherButtonTitles:nil] show];
    }
}

- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url sourceApplication:(NSString *)sourceApplication annotation:(id)annotation
{
    return [FBSession.activeSession handleOpenURL:url];
}

I put this in appDelegate, so it can be shared. I don’t want to call this in appDelegate, otherwise the redirect to facebook to ask permission/login will annoy users.

Add those in appDelegate.h file

extern NSString *const FBSessionStateChangedNotification;

- (BOOL)openSessionWithAllowLoginUI:(BOOL)allowLoginUI;

Before calling opensession, sharing window should subscribe statechange notification.

[[NSNotificationCenter defaultCenter]
     addObserver:self
     selector:@selector(sessionStateChanged:)
     name:FBSessionStateChangedNotification
     object:nil];

- (void)sessionStateChanged:(NSNotification *)notification
{
    if ((FBSession.activeSession.isOpen)) {

        if (nil == self.facebook) {
            self.facebook = [[Facebook alloc]
                             initWithAppId:FBSession.activeSession.appID
                             andDelegate:nil];

            self.facebook.accessToken = FBSession.activeSession.accessToken;
            self.facebook.expirationDate = FBSession.activeSession.expirationDate;

            // resume sharing routine here, because first time attempt without login will stop after app back from background, 
            // but this method will get statechange notifcation, so perfect to resume/restart here.
            [self shareViaFacebook];
        }
    }else{

        self.facebook = nil;
    }

Finally, the actual post action:

- (IBAction)shareOptions:(id)sender
{

    BNAppDelegate * appDelegate = (BNAppDelegate*)[[UIApplication sharedApplication] delegate];
    [appDelegate openSessionWithAllowLoginUI:YES];

    UIActionSheet * options = [[UIActionSheet alloc]
                               initWithTitle:@"Share"
                               delegate:self
                               cancelButtonTitle:@"Cancel"
                               destructiveButtonTitle:nil
                               otherButtonTitles:@"Twitter", @"Facebook", @"email", nil];

    [options showInView:self.view];
}
- (void)shareViaFacebook
{
    NSString * message = @"test msg from my test ios app";

    // no nil allow in any parameter
    NSMutableDictionary *params = [NSMutableDictionary dictionaryWithObjectsAndKeys:
                                   @"Bitrix News iPhone app", @"name",
                                   _post.title, @"caption",
                                   _post.exerpt, @"description",
                                   @"http://www.frankmao.com", @"link",
                                   @"http://ww1.prweb.com/prfiles/2011/02/01/8151699/gI_60506_bxlogo.jpg", @"picture",
                                   message, @"message", //already obsolete, don't bother, facebook will ignore it anyway
                                   nil];

    [self.facebook dialog:@"feed" andParams:params andDelegate:self];

}

Someother gotcha, app identifier must match between app and setting in developers.facebook.com/app, otherwise facebook will complain app is misconfigured when starting the session.

REF: https://developers.facebook.com/docs/reference/dialogs/feed/

https://developers.facebook.com/docs/howtos/feed-dialog-using-ios-sdk/

Copied his script into my build file, error said: Regex does not exist.

Added system.dll reference in NAnt according to this post, no help.

I stopped, why bother using Regex for such a small task.

I turn back to native NAnt tasks. Strategy is,

1. Find the hardcoded version number in vdproj file, e.g., 1.1.0, notify team member don’t touch it, this will be my constant, or token to be replaced later.
2. Replace this 1.1.0 on the fly during the build, build msi. Create backup vdproj file before replacing.
3. When build finished, restore original vdproj.

Simple and clean solution, job accomplished.

Only goofy part is, if I run this build script when Visual Studio opened, VS kept saving memory cached content to disk, causing file conflict.

Not a big deal, this build target only runs on our CI server anyway.

  <property name="orig.version.number.in.vdproj" value="1.1.0" /> <!--ensure this matches vdproj-->
  <property name="path.vdproj.file" value="src\EmailProcessorNTServiceSetup\EmailProcessorNTServiceSetup.vdproj" />
  <property name="path.vdproj.file.orig" value="${path.vdproj.file}.orig" />

  <target name="update.vdproj.version" depends="">
    <loadfile file="${path.vdproj.file}" property="file.contents" />
	<!-- build.number in format of xx.xx.xx.xx, need to shorten to xx.xx.xx to satisfy vdproj -->
    <property name="version.number" value="${string::substring(build.number, 0, string::last-index-of(build.number, '.'))}"/>
	<echo message="shorteded version.number: ${version.number}" />
    <echo file="${path.vdproj.file}" message="${string::replace(file.contents, orig.version.number.in.vdproj, version.number)}" />
  </target>  
 
  </target>

  <target name="restore.vdproj.file" depends="">
    <delete file="${path.vdproj.file}" />
	<echo message="${path.vdproj.file} could not be deleted" if="${file::exists(path.vdproj.file)}" />

	<if test="${not file::exists(path.vdproj.file)}">
		<copy file="${path.vdproj.file.orig}"
          tofile="${path.vdproj.file}"

          />
		<delete file="${path.vdproj.file.orig}" />
	</if>
<!-- can also replace it back, same result, but this potentially still mess up svn flag.    <echo file="${path.vdproj.file}" message="${string::replace(file.contents, version.number, orig.version.number.in.vdproj)}" />-->
  </target>

Use git behind firewall

git config –global -l
check http.proxy=?

git config -global http.proxy=http://proxy-server:port-number
If reset is necessary,
git config –global  unset http.proxy
or  git config –global unset-all http.proxy

Configure TeamCity connect to external git repository

So far there is no place to set http proxy in teamcity yet. (we are on teamcity 7.03）

One easiest solution is:

1. git clone to local repo folder, e.g. c:/git_repo>git clone https://remote-git myrepo
2. share this folder on local network
3. in TeamCity, VCS settings, set remote fetch url to \\repo-host\myrepo
4. tahdah…it works!

Remaining problem is we still need to manually run git pull on git_repo folder to get latest from remote, maybe a cron job can make this easier.

Compare to on-demand instance which costs about $0.02/h, spot instance price starts from $0.006, almost a third of the other one. Running a micro instance for a month will be only $4.5.

Why so cheap? One possible reason would be, on-demand instances are charged by hour, which means even if you only used it for one minute then stop your instance immediately, you will still be charged for the full hour.

The only drawback for spot instance is that there is no guarantee for server instance to continue running. When market price goes up, spot instance will be terminated. Try to pick a quiet region if you can, e.g., us-east-1b price history seems very stable  0.006/h for a month, even for past 3 months ( only 2 spikes on Apr. 23)

When instance terminated, all data will be lost. Root ebs will be deleted automatically. If state data is needed, an extra ebs can be attached as user-data storage.There are many different posts showing how to attach another ebs during start-up, like coding in rc.d

http://ec2dream.blogspot.ca/search/label/EBS

http://www.ioncannon.net/system-administration/199/automounting-amazon-ebs-volumes-on-ec2-instances/

but the easiest way is to set it in request, ec2 tool kit only.

• https://forums.aws.amazon.com/thread.jspa?messageID=200921&#200921
• http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/concepts-spot-instances-applications-ebs.html
• http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RequestSpotInstances.html

ec2-request-spot-instances -p 0.006 -t t1.micro -n 1 -b ‘/dev/sdf=snap-a023dfdf::false’ ami-746fc91d -z us-east-1b -k mykeypaire -g my-group -r persistent

1. Can not use sda1 （root), otherwise error: snapshotId cannot be modified on root device
2. /dev/sdx start from a letter >f, in the example it uses b, I encountered an error saying snap id can only be changed on ebs device.
3. Don’t forget the key-value pair and security group. They are key to access.
4. -r persistent means repeat request.

Setup OS (environment, tools, your app, etc)

Spot instance should start working for your order immediately after request fulfilled, the perfect solution would be start from your private AMI.

Create AMI

To create an AMI is to request a on-demand instance, setup everything you need, then

• Option A: created from an existing instance, better to stop the instance before
• Option B: create an ebs snapshot, from which create a new image.

Write down your image id. then request spot instance. Request can be done through AWS console or ec2 tool kit.

Setup ec2 tool kit

Download zip file from http://developer.amazonwebservices.com/connect/entry.jspa?externalID=368&categoryID=88

Simply following http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/setting-up-your-tools.html

export EC2_HOME=~/tools/ec2…
export JAVA_HOME=/usr

Generate X509 cert following  http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/using-credentials.html#using-credentials-certificate
upload those 2 files to your work machine under  ~/.ec2 folder

$ export EC2_PRIVATE_KEY=~/.ec2/pk-blahblah.pem
$ export EC2_CERT=~/.ec2/cert-blahblah.pem

Test setup using a command like ec2-describe-regions

It should work.

Those export and path setup can be put into ~/.bash_profile or ~/.bashrc

Manually attach ebs

Created a new ebs 1G

Attach to new instance manually in AWS console
device name will change to /dev/xvdf from /dev/sdf in ubuntu

ebs needs format before mount

sudo mkfs -t ext3 /dev/xvdf
sudo mount -t ext4 /dev/xvdf /home/ubuntu/folder_to_mount

ref: http://yoodey.com/how-attach-and-mount-ebs-volume-ec2-instance-ubuntu-1010

Set trust scp/ssh for rc2 instance on your own VPS

local: ssh-keygen -t dsa -f $HOME/.ssh/id_dsa -P ”
remote:(~/.ssh) cat id_dsa >> authorized_keys

ref: http://www.csua.berkeley.edu/~ranga/notes/ssh_nopass.html

Bad news, spot instance is not included in free tier.

All the saving cost export I spent so far seems useless, and I will revisit this post when my 12 month free tier expired.